Differences

This shows you the differences between two versions of the page.

--- new_collections [2016/04/18 19:53]
arubinst OAI-PMH
+++ new_collections [2026/02/06 22:45] (current)
kaileyh
@@ Line 1: / Line 1: @@
-====== Adding New Collections to Credo ======
+====== Adding new collections to Credo ======
@@ Line 6: / Line 6: @@
 ===== 1. Add <relatedItem> to MODS records =====
-For an individual item in Credo to be part of a collection, it needs to have a MODS <relatedItem> element pointing to that collection. You can find more information about <relatedItem> use in SCUA's [[http://credo.library.umass.edu/SCUAMODSGuidelines2012.pdf|Best Practices for MODS]]. Here's an example:
+For an individual item in Credo to be part of a collection, it needs to have a MODS <relatedItem> element pointing to that collection. You can find more information about <relatedItem> use in SCUA's [[http://credo.library.umass.edu/SCUAMODSGuidelines.pdf|Best Practices for MODS]]. Here's an example:
 <code xml>
@@ Line 32: / Line 32: @@
 If you want to add a collection page for a collection that does not yet have a full finding aid, it's easy enough to create a stub EAD record using the information in UMarmot. For a good example of a stub collection-level record, look at collection_mums700.xml on oubliette.
+There is a template for a collection-level record in spec_collections/credo/metadata/templates
@@ Line 45: / Line 47: @@
 ===== 4. Add collection information to the OAI-PMH endpoint =====
-This last step is critical for successful harvest by Digital Commonwealth and DPLA, that depend on the collections appearing in the OAI-PMH endpoint in a specific way in order to properly display the collection hierarchies in those systems.
+This last step is critical for successful harvest by Digital Commonwealth and DPLA, which depend on the collections appearing in the OAI-PMH endpoint in a specific way in order to properly display the collection hierarchies in those systems.
 In OAI-PMH, we represent collections as "Sets" and a complete listing of the collections each of our digital objects belong to can be viewed in the response to the OAI-PMH verb [[http://credo-oai.library.umass.edu/oai?verb=ListSets|ListSets]].
@@ Line 70: / Line 72: @@
 credo-oai.library.umass.edu
 user: localadminuser
 Please ask Aaron R. for a password.
-The file can be found at ~/solr/solr-5.2.1/server/solr/oai and is called ListSets.xml. Download this file and edit to add the new <set>. Once added, re-upload the edited file. In order for these changed to take effect, the OAI-PMH web server will need to be restarted. Please ask Aaron R. to restart the server. In Aaron R.'s absence, create a syshelp ticket in LibWire and Aaron A. will restart.
+The file can be found at ~/solr/solr-5.2.1/server/solr/oai and is called ListSets.xml. Download this file and edit to add the new <set>. Once added, re-upload the edited file. In order for these changes to take effect, the OAI-PMH web server will need to be restarted. Please ask Aaron R. to restart the server. In Aaron R.'s absence, create a syshelp ticket in LibWire and Aaron A. will restart.
+====== Adding series-level records to collection-level records in Credo ======
+Series-level landing pages can be created for collections in Credo. These pages allow the user to search within a specific series and includes Title, Collection #, Extent, Series Overview, Language and Location of that series/collection.
+===== 1. Creating the series page(s) =====
+Before a series page can be created you must add the following elements to the EAD/XML //collection page//:
+<code xml>
+<dsc type="combined" id="contlist">
+  <c01 level="series">
+    <did>
+      <unittitle><extref href="mums312-s01">Series 1. Correspondence</extref></unittitle>
+      <unitdate>1877-1965</unitdate>
+      <physdesc>195.50 boxes</physdesc>
+      <physdesc>
+        <extent>(81.52 linear feet)</extent>
+      </physdesc>
+    </did>
+  </c01>
+</code>
+In the series-level record, the following elements must be included to link out to items in the series on Credo:
+<code xml>
+<dsc type="combined" id="contlist">
+  <c01 level="series" id="mums312-s01">
+    <did>
+      <unittitle>Series 1. Correspondence</unittitle>
+      <unitdate>1877-1965</unitdate>
+      <physdesc>
+        <extent>195.50 Boxes (81.52 linear feet)</extent>
+      </physdesc>
+    </did>
+   </c01>
+</code>
+Information about the arrangement of the series and a scope note for the series can be added to the series-level record as well.
+When making a series page, the MODS record for every individual item in the series must include a <relatedItem> element pointing to the series as follows. The identifier must be the same as in the series ID in the //collection page//.
+<code xml>
+<mods:relatedItem type="series">
+  <mods:titleInfo>
+    <mods:title>Series 1. Correspondence</mods:title>
+  </mods:titleInfo>
+<mods:typeOfResource>mixed material</mods:typeOfResource>
+<mods:identifier type="uri">mums312-s01</mods:identifier>
+</mods:relatedItem>
+</code>
+This goes after the <relatedItem> element that points to the collection page (the @type="host"). Like the collection page, the @type="series" in <mods:relatedItem>, the unique ID for the collection in <mods:identifier type="uri">, and the title of the series in <mods:title> must be consistent across all records.
+In Fedora, the //series-level// record should be added to the folder where the items in that series live. Like the collection-level record, **do not** add the series-level record to the ingest folder, just add the file to the correct series folder.
+**TIP:**
+  * Make sure to create the file in the spec_collections/EAD folder so the DTD will not throw an error. You can then move the file to a collection folder.
+  * Watch out for extra elements and XML errors.
+  * There is a template for a series-level record in spec_collections/credo/metadata/templates
+===== 2. Link to items in a subseries from the series-level record in Credo =====
+//Note: this is only necessary if items from specific subseries in a collection are in Credo.//
+If a series has subseries, all items in that subseries can be linked to from the series page. To do so, add the following to the series-level record, //after// the closing </controlaccess> element and //before// the closing </c01> tag:
+<code xml>
+<c02 level="subseries">
+ <did>
+  <unittitle><extref href="mums312-s01A">A. General Correspondence</extref></unittitle><unitdate>1877-1965</unitdate><physdesc/></did>
+    </c02>
+  <c02 level="subseries">
+   <did><unittitle>
+    <extref href="mums312-s01B">B. Crisis Correspondence</extref>
+   </unittitle>
+    <unitdate normal="1911/1934">1911-1934</unitdate></did>
+    </c02>
+</code>
+The MODS record for each item in the subseries must include another <relatedItem> element pointing to the subseries:
+<code xml>
+<mods:relatedItem type="series">
+  <mods:titleInfo>
+    <mods:title>Series 1A. General Correspondence</mods:title>
+  </mods:titleInfo>
+<mods:typeOfResource>mixed material</mods:typeOfResource>
+<mods:identifier type="uri">mums312-s01A</mods:identifier>
+</mods:relatedItem>
+</code>
+Again, the @type="series" in <mods:relatedItem>, the unique ID for the collection in <mods:identifier type="uri">, and the title of the collection in <mods:title> must be consistent across all records.
+The subseries <relatedItem> element should be placed //after// the series <relatedItem> element, and this order **does matter** for the hierarchy of the links at the top of the item record page in Credo. For example, when the series <relatedItem> element comes before the subseries <relatedItem> element in an item record, the top of the page for the item looks like this:
+{{::series.png?600|}}
+If the subseries is placed before the series in the item record, it looks like this instead:
+{{:subseries.png?600|}}

scua

User Tools

Site Tools

Differences

Page Tools