publish harriman project resources

[briesenberg07]

PUBLISH HARRIMAN PROJECT SUMMARY AND DATA

• directory critcat/harriman
  • README.md, including:
    • Project scope
    • Link to collection landing page
    • Link to harriman metadata application profile
    • Guide to data included in project directory (.csv file below, possibly other files...)
    • ...?
  • harriman_target_records.csv (export from og_library_mig Excel file) -- change history for CONTENTdm metadata
  • ...?

📜 NOTES

• No one outside repo contributors will be able to view this information ^^^ as long as uwlib-mig/critcat is a private repository
• We also changed EAD data and MARC data—not included in the proposal above--will we publish these changes as well?

Requesting feedback from @CECSpecialistI @ElaineSpeer @smfitch @weirdbananakat , will share as email for feedback from pilot project group members without GitHub accounts

[weirdbananakat]

My thoughts are to --yes to the directory and yes, publish EAD and MARC data as well. Does that mean we will need to specify what is public and private when we work in the MIG repository in the future?

[smfitch]

Benjamin, This looks great to me. Very helpful. Susan

[[ Benjamin deleted email-forwarding clutter below ]]

[briesenberg07]

Thanks everyone so far for the feedback. I mentioned...

We also changed EAD data and MARC data—not included in the proposal above--will we publish these changes as well?

...but we edited collection landing pages and the copy-negative database too! So, here and going forward, will need to decide which changes to publish

[CECSpecialistI]

I am in favor of publishing changes to MARC and EAD data here as well. I'm also hoping that we might make this repository fully public once we've worked out the details of how we want it to look. As far as the copy-negative database and landing pages, I don't have strong opinions but would lean towards publishing some kind of summary of project deliverables in the .README file that included links to changed landing pages and a narrative description of how we accomplished the repair we set out to do.

[weirdbananakat]

I am in favor of publishing changes to MARC and EAD data here as well. I'm also hoping that we might make this repository fully public once we've worked out the details of how we want it to look. As far as the copy-negative database and landing pages, I don't have strong opinions but would lean towards publishing some kind of summary of project deliverables in the .README file that included links to changed landing pages and a narrative description of how we accomplished the repair we set out to do.

Agree!

[briesenberg07]

📢 Bare-minimum added to Past_Projects/Harriman/README.md

DETAILS/NOTES:

• Includes working spreadsheet
• The 'before' and 'after' CONTENT commits were created by me from a single export --
  • I didn't get a 'before' export!
  • So, I created a this from data in working spreadsheet (❗ TO DO for future projects - get 'before' exports for all metadata formats where changes will be made and we wish to record change history!)
• No EAD exports at this time - tagging @ElaineSpeer
  • I imagine that a current/'after' EAD export can be made, but not sure whether previous versions are available for export, and if not, whether it's feasible or desirable to create this file as I did for the CONTENTdm XML

[ElaineSpeer]

Benjamin- versioning EAD may be a longer conversation, let me know if you want to schedule something. The short version is that I'm still in the process of figuring out how Mark set up our XML stuff so I don't think we have access to prior versions, but sometimes we find stuff so it's not impossible. The other thing is I don't remember how much the Alliance keeps as backups so I can reach out to them and see.

[briesenberg07]

Thanks @ElaineSpeer -- you mention:

I don't remember how much the Alliance keeps as backups so I can reach out to them and see

Would you be willing to reach out to the Alliance and see if a previous version ('before') XML/EAD is available? If yes, we can store that, and, once your ability to export the current ('after') version of XML/EAD is sorted, we can store this as well (RELATED: questions about CritCat data management)?

If no, maybe we don't have access to before/after EAD data for the pilot project. If that's the case, well, lessons will have been learned and we'll be sure to get a 'before' export next time!

It should be noted ✏️ how little I understand the Encoded Archival Description standard. I believe it is XML-encoded data, so my general idea is to store versions of an EAD file in much the same way that I'm proposing we store CONTENTdm XML exports to create a record/view of updates made during remediation. Let's discuss more on the 23rd?

[ElaineSpeer]

@briesenberg07 Yes, I think adding this to the agenda for the 23rd makes a lot of sense. I'll see what info I can gather before then.