-
If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.
-
You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!
|
CRS Metadata Entry Standards
Page history
last edited
by PBworks 17 years, 9 months ago
CRS Report Metadata Entry Standards
Starr Hoffman
6.29.06
DC Date
- list format/style
- specify what the date is (creation, etc.)
- rule for including dates metadata is created/edited
- not all will have a specific publication date
- some are marked only "May 2006" -- we enter "May 1, 2006" for these
- 6.30.06 update, am discussing current date practices & future possibilities with Mark
DC Creator
reconcile the name to whatever is the most used form
- Bea, Keith (80 records) vs. Bea, Keith A (1 record); __use Bea, Keith__
- Viña, Stephen R (10 records) vs. Viña, Stephen (3 records) vs. Viña, Steve (1 record); __use Viña, Stephen R__
in cases of the same number of records for each form, use the most complete form of the name
- i.e. Smith, Jonathan E (when both Smith, Jonathan E and Smith, Jon were used)
- if later reports reveal that more use the shorter form, the records can be changed then
- it's easier to delete material than to add it
sources for determining if a particular name is equivalent to a different name for the same person
- check the CRS reports to see if each name/person works in the same division
- Google each version of the name (in quotes) and several CRS titles
- Google each version of the name and the word "contact" to determine if this information is the same for each
in the case of a "junior" or "senior" suffix: last name, first name, suffix
- Use __Best, Richard A, Jr__
do not include the period after the middle initial or a suffix
- it will be dropped upon upload
- still need to decide what to do about first initials...
cases in which both a maiden name and a married name are used
agencies/divisions which have subsequently changed names
- use the agency title as it is written in the report
- when the Authority Control file is completed, we may (?) be able to use it to link different agencies/divisions (much like it would in an OPAC)
check the Creator & Title authority file
- note in Creator authority file any agencies/divisions which have subsequently changed names
DC Title
enter only one space after a colon
- use "Energy Efficiency__: Key__ to Sustainable Energy Use"
when a dash appears in the title (as a separator, not as a modifier), enter: space, dash, space
- use "U.S.-Korean Relations - Issues for Congress"
- instead of "U.S.-Korean Relations--Issues for Congress"
- a modifying dash would be the dash in "U.S.-Korean"
include punctuation as presented in the report title
- preserve the question mark in "Long-Term Care: What Direction for Public __Policy?__"
- instead of "Long-Term Care: What Direction for Public __Policy__"
do not include any italics formatting
- this appears to cut off any part of the title following the italics
- I assume this occurs during the upload process...
in instances of "and" or "&" use the version that is used in the report title
- if the original title reads "Nuclear Weapon Initiatives: Low-Yield __R&D__, Advanced Concepts, Earth Penetrators, Test Readiness" then preserve "R&D" as written
- check this: using "&" in the spreadsheet may cause the rest of the title to be cut off, like some of the R&D titles
do not abbreviate any words not already abbreviated in the title
- do not create a record with the title "__U.S.__ Foreign Policy" if the CRS title reads "__United States__ Foreign Policy"
the reverse is also true: do not write out any words that are abbreviated in the title |
check the Creator & Title authority file
DC Title Issues to Solve...
problemmatic titles (possibility of an alternate title field?)
- 6.30.06 update, Mark has informed me that we do have an option for presenting alternate/related titles by using DC qualifiers; I'll explore this more
- plurals
- "Overview of the Authorization-__Appropriation__ Process" vs "Overview of the Authorization-__Appropriations__ Process"
- "Taiwan: Recent Development and U.S. Policy Choices" vs "Taiwan: Recent Developments and U.S. Policy Choices"
- variant spellings or typos
- "Nuclear Power Plants__: Vulnerability to Terrorist Attack" vs "Nuclear __Powerplants__: Vulnerability to Terrorist Attack"
- variant word forms
- "The Capitol __Visitor Center: An Overview" vs "The Capitol Visitors' Center: An Overview"
- ""Bunker Busters": Robust Nuclear Earth Penetrator Issues, FY2005__ and FY2006" vs ""Bunker Busters": Robust Nuclear Earth Penetrator Issues, __FY2005-FY2007__"
- later version of same document, years adjusted accordingly
- ""Bunker Busters": Robust Nuclear Earth Penetrator Issues, FY2005 and __FY2006__" vs ""Bunker Busters": Robust Nuclear Earth Penetrator Issues, FY2005-__FY2007__"
- variant punctuation
- "Sport Utility Vehicles, __Mini-Vans __and Light Trucks: An Overview of Fuel Economy and Emissions Standards" vs "Sport Utility Vehicles, __Mini-Vans, and Light Trucks: An Overview of Fuel Economy and Emissions Standards"
- "The European Union's 'Constitution'__" vs "The European Union's __Constitution__"
- missing or extra words
- "Afghanistan: Current Issues and U.S. __Policy__" vs "Afghanistan: Current Issues and U.S. __Policy Concerns__"
- "A Brief Summary of the __HIPAA Medical Privacy Rule" vs "A Brief Summary of the Medical Privacy Rule"
- (additional cases are listed in the individual CRS Metadata spreadsheets)
Back to CRS Process
Back to GovDocs Notes & Training
Back to Front Page
CRS Metadata Entry Standards
|
Tip: To turn text into a link, highlight the text, then click on a page or file from the list above.
|
|
|
|
|
Comments (0)
You don't have permission to comment on this page.