metadata_resources
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
metadata_resources [2026/05/14 16:58] jeremy |
metadata_resources [2026/05/14 17:06] (current) jeremy |
||
|---|---|---|---|
| Line 27: | Line 27: | ||
| * [[https://www.getty.edu/conservation/publications_resources/pdf_publications/atlas.html | other print types]] | * [[https://www.getty.edu/conservation/publications_resources/pdf_publications/atlas.html | other print types]] | ||
| - | ===Standard Photo Sizes (If it isn't one of these, describe in cm.)=== | + | ====Standard Photo Sizes (If it isn't one of these, describe in cm.)==== |
| *3 x 5 in. | *3 x 5 in. | ||
| *4 x 6 in. | *4 x 6 in. | ||
| Line 33: | Line 33: | ||
| *8 x 10 in. | *8 x 10 in. | ||
| - | === More metadata rules and creation tips=== | + | ==== More metadata rules and creation tips==== |
| **Organization** | **Organization** | ||
| * You can save a set of tabs in your browser and open them with one click. Bookmark websites to a folder. Open the bookmark manager or library. Right-click on a folder and select "Open all in tabs". | * You can save a set of tabs in your browser and open them with one click. Bookmark websites to a folder. Open the bookmark manager or library. Right-click on a folder and select "Open all in tabs". | ||
| Line 39: | Line 39: | ||
| * Save every time you edit any local authority file you create -- save after every little change so that it updates when others are working at the same time. | * Save every time you edit any local authority file you create -- save after every little change so that it updates when others are working at the same time. | ||
| **Creation** | **Creation** | ||
| - | * If an incoming letter mentions an enclosure but it is not present in the folder, make at note in the abstract: **Enclosure not with letter**. | + | * If an incoming letter mentions an enclosure but it is not present in the folder, make a note in the abstract: **Enclosure not with letter**. |
| * Mention any handwritten notes or corrections on documents in the abstract, except for filing instructions at the tops of documents (General, Personal, name of client). | * Mention any handwritten notes or corrections on documents in the abstract, except for filing instructions at the tops of documents (General, Personal, name of client). | ||
| * Include spaces after the period for initials in names (e.g. W. E. B. Du Bois - **correct**, W.E.B. Du Bois - **wrong**). | * Include spaces after the period for initials in names (e.g. W. E. B. Du Bois - **correct**, W.E.B. Du Bois - **wrong**). | ||
| * If you come across a stack of form letters (same content) addressed to many people, catalog those as one record with title "Letter from XXX to multiple recipients". Based on interest of content and amount of names, make a decision on whether to include recipients' names in the abstract. Add genre term "form letters". | * If you come across a stack of form letters (same content) addressed to many people, catalog those as one record with title "Letter from XXX to multiple recipients". Based on interest of content and amount of names, make a decision on whether to include recipients' names in the abstract. Add genre term "form letters". | ||
| * Names or words with diacritics need to be encoded. Use the Oxygen character map (under the Edit menu) to look up the code that properly inserts the accented character. **Use the "decimal" (not hexidecimal) code**. To make sure it is searchable in Credo, use the plain text version in the abstract. Example: **Pelé** in title and name elements and **Pele** in abstract. | * Names or words with diacritics need to be encoded. Use the Oxygen character map (under the Edit menu) to look up the code that properly inserts the accented character. **Use the "decimal" (not hexidecimal) code**. To make sure it is searchable in Credo, use the plain text version in the abstract. Example: **Pelé** in title and name elements and **Pele** in abstract. | ||
| - | * for royal/titled names that are in LOC Name Authority, it's a good idea to check the MARC format to see how LOC has parsed the name elements. Example: "Wellington, Charles Wellsely, Duke of, 1945-" (LOC). Title: "Letter from XXX to Charles Wellsely, Duke of Wellington" | + | * For royal/titled names that are in LOC Name Authority, it's a good idea to check the MARC format to see how LOC has parsed the name elements. Example: "Wellington, Charles Wellsely, Duke of, 1945-" (LOC). Title: "Letter from XXX to Charles Wellsely, Duke of Wellington" |
| - | * MODS Name as: \\ <name type="personal">\\ <namePart type="family">Wellington</namePart>\\ <namePart type="given">Charles Wellsely</namePart>\\ <namePart type="termsOfAddress">Duke of</namePart>\\ <namePart type="date">1945-</namePart>\\ </name> | + | * MODS Name as: \\ **<name type="personal">**\\ **<namePart type="family">**Wellington**</namePart>**\\ **<namePart type="given">**Charles Wellsely**</namePart>**\\ **<namePart type="termsOfAddress">**Duke of**</namePart>**\\ **<namePart type="date">**1945-**</namePart>**\\ **</name>** |
| **Mods/Credo rules** | **Mods/Credo rules** | ||
| * **<mods:name>** | * **<mods:name>** | ||
| Line 51: | Line 51: | ||
| * **<mods:dateCreated>** | * **<mods:dateCreated>** | ||
| * For items with a date range, create two **<mods:dateCreated>** entries, one for each part of the date range. Add **point="start"** to the first entry and **point="end"** in the second entry. | * For items with a date range, create two **<mods:dateCreated>** entries, one for each part of the date range. Add **point="start"** to the first entry and **point="end"** in the second entry. | ||
| - | * There can only be one **keyDate="yes"** attribute for dates. So for entries with a date range the keyDate attribute should appear on the earliest entry (e.g. **<mods:dateCreated keyDate="yes" encoding="w3cdtf" point="start">**//1967-07//**</mods:dateCreated><mods:dateCreated encoding="w3cdtf" point="end">**//1967-08//**</mods:dateCreated>**. This rule also applies if you have a **<mods:dateIssued>** element as well. | + | * There can only be one **keyDate="yes"** attribute for dates. So for entries with a date range, the keyDate attribute should appear on the earliest entry (e.g. **<mods:dateCreated keyDate="yes" encoding="w3cdtf" point="start">**//1967-07//**</mods:dateCreated><mods:dateCreated encoding="w3cdtf" point="end">**//1967-08//**</mods:dateCreated>**. This rule also applies if you have a **<mods:dateIssued>** element as well. |
| - | + | ||
| * **<mods:title>** | * **<mods:title>** | ||
| * Do not use double quotes (") in titles -- the system will screw them up. Use single quotes (') instead. | * Do not use double quotes (") in titles -- the system will screw them up. Use single quotes (') instead. | ||
| - | * [[willy_pad|More FAQs on cataloging]] | + | **[[willy_pad|More FAQs on cataloging]]** |
metadata_resources.1778777917.txt.gz · Last modified: 2026/05/14 16:58 by jeremy
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
