Changeset 8865
- Timestamp:
- 2004-12-20T17:33:42+13:00 (19 years ago)
- File:
-
- 1 edited
-
trunk/gli/metadata/rfc1807.mds (modified) (12 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/gli/metadata/rfc1807.mds
r8747 r8865 84 84 <Attribute name="identifier">Id</Attribute> 85 85 <Attribute name="definition">The identifier for the RFC-1807 record.</Attribute> 86 <Attribute name="identifier">This is the second field of any record. It is also a mandatory field. The ID field identifies the bibliographic record and is used in management of these records. Its format is "ID:: XXX//YYY", where XXX is the publisher-ID (the controlled symbol of the publisher) and YYY is the ID (e.g., report number) of the publication as assigned by the publisher. This ID is typically printed on the cover, and may contain slashes. The organization symbols "DUMMY" and "TEST" (case independent) are reserved for test records that should NOT be incorporated in the permanent database of the recipients. Format: ID:: <publisher-ID>//<free-text> Example: ID:: OUKS//CS-TR-91-123 </Attribute>87 86 <Attribute name="comment">This is the second field of any record. It is also a mandatory field. The ID field identifies the bibliographic record and is used in management of these records. Its format is "ID:: XXX//YYY", where XXX is the publisher-ID (the controlled symbol of the publisher) and YYY is the ID (e.g., report number) of the publication as assigned by the publisher. This ID is typically printed on the cover, and may contain slashes. The organization symbols "DUMMY" and "TEST" (case independent) are reserved for test records that should NOT be incorporated in the permanent database of the recipients. Format: ID:: <publisher-ID>//<free-text> Example: ID:: OUKS//CS-TR-91-123 </Attribute> 88 87 </Language> … … 100 99 <Attribute name="identifier">Entry</Attribute> 101 100 <Attribute name="definition">The date RFC-1807 record was created.</Attribute> 102 <Attribute name="identifier">This is a mandatory field. It is the date of creating this bibliographic record. The format for ENTRY date is "Month Day, Year". The month must be alphabetic (spelled out). The "Day" is a 1- or 2-digit number. The "Year" is a 4-digit number. Format: ENTRY:: <date%gt; Example: ENTRY:: January 15, 1992 </Attribute>103 101 <Attribute name="comment">This is a mandatory field. It is the date of creating this bibliographic record. The format for ENTRY date is "Month Day, Year". The month must be alphabetic (spelled out). The "Day" is a 1- or 2-digit number. The "Year" is a 4-digit number. Format: ENTRY:: <date> Example: ENTRY:: January 15, 1992 </Attribute> 104 102 </Language> … … 243 241 <Attribute name="definition">Total number of pages</Attribute> 244 242 <Attribute name="comment">Total number of pages, without being too picky about it. Final numbered page is actually preferred, if it is a reasonable approximation to the total number of pages. Format: PAGES:: <number> Example: PAGES:: 48 </Attribute> 245 <Attribute name="comment">Total number of pages, without being too picky about it. Final numbered page is actually preferred, if it is a reasonable approximation to the total number of pages. Format: PAGES:: <number> Example: PAGES:: 48 </Attribute>246 243 </Language> 247 244 <!-- Non-language specific --> … … 272 269 <Attribute name="definition">Handles are unique identifiers that are used to rerieve location data.</Attribute> 273 270 <Attribute name="comment">Handles are unique permanent identifiers that are used in the Handle Management System to retrieve location data. A handle is a printable string which when given to a handle server returns the location of the data. Handles are used to identify digital objects stored within a digital library. If the technical report is available in electronic form, the Handle MUST be supplied in the bibliographic record. Format is "HANDLE:: hdl:<naming authority>/string of characters". The string of characters can be the report number of the technical report as assigned by the publisher. For more information on handles and handle servers see the CNRI WEB page at http://www.cnri.reston.va.us. NOTE: White space in HANDLE due to line wrap is ignored. Format: HANDLE:: hdl:<naming authority>/string of characters Example: HANDLE:: hdl:oceanview.electr/CS-TR-91-123</Attribute> 274 <Attribute name="comment">Handles are unique permanent identifiers that are used in the Handle Management System to retrieve location data. A handle is a printable string which when given to a handle server returns the location of the data. Handles are used to identify digital objects stored within a digital library. If the technical report is available in electronic form, the Handle MUST be supplied in the bibliographic record. Format is "HANDLE:: hdl:<naming authority>/string of characters". The string of characters can be the report number of the technical report as assigned by the publisher. For more information on handles and handle servers see the CNRI WEB page at http://www.cnri.reston.va.us. NOTE: White space in HANDLE due to line wrap is ignored. Format: HANDLE:: hdl:<naming authority>/string of characters Example: HANDLE:: hdl:oceanview.electr/CS-TR-91-123 </Attribute>275 271 </Language> 276 272 <!-- Non-language specific --> … … 300 296 <Attribute name="identifier">Retrieval</Attribute> 301 297 <Attribute name="definition">Describes how to get a copy of the full text</Attribute> 302 <Attribute name="comment">Open-ended format describing how to get a copy of the full text. This is an optional, repeatable field. No limitations are placed on the dissemination of the bibliographic records. If there are limitations on the dissemination of the publication, it should be protected by some means such as passwords. This format does not address this protection. Format: RETRIEVAL:: <free-text> RETRIEVAL:: for full text with color pictures send a self-addressed stamped envelope to Prof. J.A. Finnegan, CS Dept, Oceanview University, Oceanview, KS 54321 </Attribute>303 298 <Attribute name="comment">Open-ended format describing how to get a copy of the full text. This is an optional, repeatable field. No limitations are placed on the dissemination of the bibliographic records. If there are limitations on the dissemination of the publication, it should be protected by some means such as passwords. This format does not address this protection. Format: RETRIEVAL:: <free-text> RETRIEVAL:: for full text with color pictures send a self-addressed stamped envelope to Prof. J.A. Finnegan, CS Dept, Oceanview University, Oceanview, KS 54321 </Attribute> 304 299 </Language> … … 316 311 <Attribute name="definition">Keywords</Attribute> 317 312 <Attribute name="comment">Specify any keywords, controlled or uncontrolled. This is an optional, repeatable field. Multiple keywords are entered using multiple lines in the form of "KEYWORD:: <free-text>. Format: KEYWORD:: <free-text> Example: KEYWORD:: Scientific Communication KEYWORD:: Communication Theory </Attribute> 318 <Attribute name="comment">Specify any keywords, controlled or uncontrolled. This is an optional, repeatable field. Multiple keywords are entered using multiple lines in the form of "KEYWORD:: <free-text>. Format: KEYWORD:: <free-text> Example: KEYWORD:: Scientific Communication KEYWORD:: Communication Theory </Attribute>319 313 </Language> 320 314 <!-- Non-language specific --> … … 331 325 <Attribute name="definition">The Computer Reviews Category index</Attribute> 332 326 <Attribute name="comment">Specify the CR-category. The CR-category (the Computer Reviews Category) index (e.g., "B.3") should always be included, optionally followed by the name of that category. If the name is specified it should be fully specified with parent levels as needed to clarify it, as in the second example below. Use multiple lines for multiple categories. Every year, the January issue of CR has the full list of these categories, with a detailed discussion of the CR Classification System, and a full index. Typically the full index appears in every January issue, and the top two levels in every issue. Format: CR-CATEGORY:: <free-text> Example: CR-CATEGORY:: D.1 Example: CR-CATEGORY:: B.3 Hardware, Memory Structures </Attribute> 333 <Attribute name="comment">Specify the CR-category. The CR-category (the Computer Reviews Category) index (e.g., "B.3") should always be included, optionally followed by the name of that category. If the name is specified it should be fully specified with parent levels as needed to clarify it, as in the second example below. Use multiple lines for multiple categories. Every year, the January issue of CR has the full list of these categories, with a detailed discussion of the CR Classification System, and a full index. Typically the full index appears in every January issue, and the top two levels in every issue. Format: CR-CATEGORY:: <free-text> Example: CR-CATEGORY:: D.1 Example: CR-CATEGORY:: B.3 Hardware, Memory Structures</Attribute>334 327 </Language> 335 328 <!-- Non-language specific --> … … 360 353 <Attribute name="definition">Series title</Attribute> 361 354 <Attribute name="comment">Series title, including volume number within series. Open-ended format, with producing institution strongly encouraged to be internally consistent. Format: SERIES:: <free-text> Example: SERIES:: Communication </Attribute> 362 <Attribute name="comment">Series title, including volume number within series. Open-ended format, with producing institution strongly encouraged to be internally consistent. Format: SERIES:: <free-text> Example: SERIES:: Communication</Attribute>363 355 </Language> 364 356 <!-- Non-language specific --> … … 374 366 <Attribute name="identifier">Monitoring</Attribute> 375 367 <Attribute name="definition">The monitoring organization(s)</Attribute> 376 <Attribute name="comment">The name(s) of the monitoring organization(s). Format: MONITORING:: <free-text>Example: MONITORING:: ONR </Attribute>377 368 <Attribute name="comment">The name(s) of the monitoring organization(s). Format: MONITORING:: <free-text> Example: MONITORING:: ONR </Attribute> 378 369 </Language> … … 405 396 <Attribute name="definition">The contract number(s)</Attribute> 406 397 <Attribute name="comment">The contract number(s). Format: CONTRACT:: < free-text> Example: CONTRACT:: MMA-90-23-456 </Attribute> 407 <Attribute name="comment">The contract number(s). Format: CONTRACT:: <free-text> Example: CONTRACT:: MMA-90-23-456</Attribute>408 398 </Language> 409 399 <!-- Non-language specific --> … … 420 410 <Attribute name="definition">The grant number(s)</Attribute> 421 411 <Attribute name="comment">The grant number(s). Format: GRANT:: <free-text> Example: GRANT:: NASA-91-2345</Attribute> 422 <Attribute name="comment">The grant number(s). Format: GRANT:: <free-text> Example: GRANT:: NASA-91-2345</Attribute>423 412 </Language> 424 413 <!-- Non-language specific --> … … 434 423 <Attribute name="identifier">Language</Attribute> 435 424 <Attribute name="definition">The language in which the report is written</Attribute> 436 <Attribute name="comment">The language in which the report is written. Please use the full English name of that language. Please include the Abstract in English, if possible. If the language is not specified, English is assumed. Format: LANGUAGE:: <free-text> Example: LANGUAGE:: English Example: LANGUAGE:: French </Attribute>437 425 <Attribute name="comment">The language in which the report is written. Please use the full English name of that language. Please include the Abstract in English, if possible. If the language is not specified, English is assumed. Format: LANGUAGE:: <free-text> Example: LANGUAGE:: English Example: LANGUAGE:: French</Attribute> 438 426 </Language>
Note:
See TracChangeset
for help on using the changeset viewer.
