Skip to content

Instantly share code, notes, and snippets.

@mark-dce

mark-dce/Hierarchy Sample.CSV

Last active March 18, 2019 16:00
Show Gist options
  • Save mark-dce/550cfe5b2f63afe4ca06cd2f4adca04c to your computer and use it in GitHub Desktop.
Save mark-dce/550cfe5b2f63afe4ca06cd2f4adca04c to your computer and use it in GitHub Desktop.
Download ZIP
Potential CSV model for collections and child pages
Raw
Hierarchy Sample.CSV
Object Type Title Item ARK Collection ARK Parent ARK Sequence Number
Collection Miscellaneous Manuscripts ark:9999/1df68c5
Work Home Book on Sanitation ark:9999/2fa8801 ark:9999/1df68c5
Child Work Front Cover ark:9999/8c500dc ark:9999/2fa8801 1
Child Work Inside Front ark:9999/6899e32 ark:9999/2fa8801 2
@mark-dce
Copy link
Author

Agreed about row order - requiring an explicit sequence number makes sense.

All of the examples we have seen (e.g. http://digital2.library.ucla.edu/viewItem.do?ark=21198/zz000sq41q) have page-level ARKs. UCLA has indicated this will also be the case going forward, so we'll use this as our working assumption until proven wrong.

Based on discussion, we're dividing out the child-level parent vs. the work's collection parent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment