Skip to content

Instantly share code, notes, and snippets.

@jpstroop

jpstroop/beach_image_workflow_proposal.md

Last active January 9, 2017 16:57
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jpstroop/ac59742d1e0664b50d90cef35a14add9 to your computer and use it in GitHub Desktop.
Save jpstroop/ac59742d1e0664b50d90cef35a14add9 to your computer and use it in GitHub Desktop.
Download ZIP
Beach Image Workflow Idea
Raw
beach_image_workflow_proposal.md

Deprecated. Moved here: https://docs.google.com/document/d/1GY9_CfvFb5WCFOoSQ54DwzoMKPXmh5UrBgBuN5QXjUg/edit#

Proposed Flow

  1. Talk to RBSC cat.
  2. Enhace EAD w/ item level data from TEI. Including pudl0123 IDs temporarily
  3. Use TEI to EAD mapping to reorg. images to match new EAD (item level) components
  4. Remove temporary pudl0123 IDs from new EAD components
  5. Generate new PULFA METS and load EAD
  6. Migration New PULFA METS to Plum - Make sure EAD component ID is in dc:replaces
  7. Map Plum manifest URIs back to TEI

Requires

  • Permission / Help from RBSC
  • Plum to PULFA migration routine

Questions

  • Does this cover all of pudl0123 / C0108 digitzation?

  • Does Roel have the back story as to why two copies?

    Answer is because the studios originally made the more granular organization, and then the curator (?) asked if it could be flattened out so that it could go online with the findin aid.

@rlskoeser
Copy link

Additional note (new information): images are not currently in chronological order; should be possible to re-order based on dates in the transcribed TEI. May require some manual cleanup (?)

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