• Sample Personal Page
• Sample Research Page
• Sample Generic Page

1. Download the approriate template
2. Rename the folder to something approripate (the name of the project, for example)
3. Edit the index.html file located in the folder to use your content. All links, images, etc will be assumed to be relative to the site main page, so there is NO need to hardcode any links to ... Any links will be translated to a relative path before uploading by the Webmaster (or user of DreamWeaver). The links are only there now so that remote users will be able to see the page they are editing!
4. Submit your directory (preferrably as a zip file) to the webmaster for uploading.

1. Please be sure to remove all instances of the string http://umiacs.umd.edu before uploading the pages or loading them into DreamWeaver.
2. Be sure not to remove the final /.
3. This can be accomplished most easily by a search and replace inside DreamWeaver

Publications

Earlier we decided that the best way to manage this information is for each author to create a .bib file or set of files for their
publications. You MUST provide these bib entries for Denise to link in the publications.

For now, the publications will be one of three types:

Conference Publication (inproceedings)
Journal Article (article)
Technical Report (techreport)

GENERATION OF BIB ENTRIES
-------------------------

You should provide all of the information in the templates below for each publication. For the CITIATION_NAME you should follow the these convensions if possible:

TR: LAMP_XXX
Conference and Journal: NameYear_Description
(e.g. ICPR99_TextTracking)

If you want the abstract included, you must fill in the abstract.

If you want the paper linked to a copy on the server, please provide a copy of it and fill in the appropriate line (PDF, HTML or PS). At this time we will NOT provide external links as it is too difficult to keep them up to date. You must provide a copy of the file (with the names described) with the bib entry. Any of the fields can be optional fields can be omitted.

NOTES:

1) Authors should be listed with First and Middle initials only and
the word "and" in between all authors names

2) Whenever you use tex commands sensitive characters in the abstract, they must be proceeded by a \, as in \%, \{ or \}.

3) The path to the files should be the absolute path to
location of the .ps, .html or .pdf file

4) the commas, and braces are very important. These are simply bibtex style entries.

5) In the keys, you should not use a colon (:)

% Conference Publication (inproceedings)
%
@InProceedings{CITATION_NAME,
author = {},
title = {},
booktitle = {},
month = {},
year = {},
pages = {},

OPTIONAL FIELDS

abstract = {},
status = {SUBMITTED, TOAPPEAR, PUBLISHED},
psfile = {NAME OF PS FILE},
htmlfile = {NAME OF HTML FILE},
pdffile = {NAME OF PDF FILE},
}

% NOTE: If the name of the files above is "-" then the name is assumed to be the same as the key (ie CITATION_NAME).

%
% Journal Article (article)
%

@Article{CITATION_NAME,
author = {},
title = {},
journal = {},
year = {},
volume = {},
number = {},
pages = {},
abstract = {}
status = {SUBMITTED, TOAPPEAR, PUBLISHED},
psfile = {},
htmlfile = {},
pdffile = {},

}

@TechReport{CITATION_NAME,
author = {},
title = {},
institution = {University of Maryland, College Park},
number = {LAMP-TR-XXX,CFAR-TR-YYY,CS-TR-ZZZ},
month = {},
year = {},
abstract = {}
status = {SUBMITTED, TOAPPEAR, PUBLISHED}
psfile = {},
htmlfile = {},
pdffile = {},
}

Authors should submit these entries directly to Denise. If you want to use the generated entries on your own WWW pages, please simply copy the HTML source from the WWW pages when the references are posted.

EXAMPLE:

@TechReport{LAMP_022,
author = {Bonnie J. Dorr and Nizar Habash and David Traum},
title = {A Thematic Hierarchy for Efficient Generation from Lexical-Conceptual Structure},
institution = {University of Maryland, College Park},
number = {LAMP-TR-022,UMIACS-TR-98-50,CS-TR-3934},
month = {October},
year = {1998},

PSFILE = {-},
PDFFILE = {BonniesTR22.pdf},
abstract = {
This paper describes an implemented algorithm for syntactic realization
of a target-language sentence from an interlingual representation called
Lexical Conceptual Structure (LCS). We provide a mapping between LCS
thematic roles and Abstract Meaning Representation (AMR) relations; these
relations serve as input to an off-the-shelf generator (Nitrogen). There
are two contributions of this work: (1) the development of a thematic
hierarchy that provides ordering information for realization of arguments
in their surface positions; (2) the provision of a diagnostic tool for
detecting inconsistencies in an existing online LCS-based lexicon that
allows us to enhance principles for thematic-role assignment.}

}

WEBMASTER INSTRUCTIONS:

GENERATION OF BIB ENTRIES

This is a program availble to process these abstracts located in the pubs/bin directory of the LAMP WWW tree (currently /fs/www-cfar/Documents/LAMP-ExtraSpace/ on system 7 or /fs/www/Documents/LAMP-ExtraSpace/ on system 6)

GenBibAbstract <bibfile> [optional <bibkey>] -html -tex -entry

- generates an HTML version of the abstract for each record in the input bib file that has an abstract optional key is -html (case insensitive)
- generates a LaTex compilable form of the abstract for each record in the bib file that has an abstract. optional key is -tex
- generates a line that can be included as pointer to your abstract, psfiles, etc on any WWW page optional key is -entry
- generates all three files above if you don't enter any

When you run GenBibAbstract above, it will produce

<bibentry>-Entry.html
<bibentry>-Abstract.html if there is an abstract
<bibentry>-Abstract.tex if there is an abstract all in a subdirectory named <bibentry>.

Now the question is how to we create an HTML files with the
<bibentry>-Entry.html text embedded. We have produced a script
RealizeBib, which takes a .base file and produces .html file.

If you want to include the text from <bibentry>/<bibentry>-Entry.html, just put "<ENTRY <bibentry>>" in the base file. Running RealizeBib will substitute the next and create the new .html file.

---------------------------------------------------------------------
Specifics:

We want three files for LAMP publications, one called LampTRs.base, one calle LampLang.base and one called LampMedia.base. These should be kept in the pubs directory of the LAMP www page, currently in the same place as above

The highest priority will be to get the existing bib entries into
the correct structure.

Example DIRECTIONS: FOR LampTRs

1. Update LampTRs.bib located in /fs/www/lamp/pubs
2. Run "bin/GenBibAbstract LampTRs.bib"
3. Update LampTRs.base by putting the new entry <ENTRY LAMP_036> in the content section
4. Run "bin/RealizeBib LampTRs"

*******************
Generating Lists of Publications

- Goto the Papers or TechReports directory
- Run
" bin/GenBibList.csh [dirs]"
where [dirs] is a list of the papers you want to generate a list for

For example
GetBibList.csh LAMP*

This will produce a list of "items" that can be included into a
latex file in an "itemize" command.