Complete manual data entry in production ASpace
marlo-longley opened this issue · comments
Let's wait until we've resolved #326 to make sure we are set on the formatting.
It's important that the HTML is copied directly from the staging ASpace interface because I made some fixes to the HTML there, which won't be reflected in the original source or file.
Backup copy of the HTML from Scope and Content note(s) in Collection record (copy/pasted direct from ASpace staging interface after Marlo's work referenced above): https://drive.google.com/file/d/1-sKjGjQ6gvTsiULch5BeuzDTL-192eNG/view?usp=share_link
Out of date as of 12/8
This backup could easily become out of date if we continue to edit in ASpace. I think it's great to have a backup, but we should rely on pasting from the ASpace instance when we do the migration, as it may change in the course of QA.
We created a barebones collection resource in production so we could upload data.
All the the manual data entry remains to be done.
Blocked on #338
When doing manual data entry, Column M in "USHMM collection name" should be added to Scope and content for film items (AKA this is a note to self): https://docs.google.com/spreadsheets/d/1QGcCtrGgASdvU6cHG7t09UVXMAk_DIN110zuWv42914/edit#gid=1206926021
@laurensorensen re this note to self on Column M, if you only make this change in the production ASpace while you are migrating the content from staging, it will not get airtime on staging during QA / now, and it will be a difference between the data we are QA'ing and the production data. If you want, we can create a separate ticket for this task and complete it now on staging. That way the change will be migrated to production along with all the other scope and contents data.
Thanks @marlo-longley I'll create a separate ticket. Commented on another related ticket which I will now delete, just seeing this!
@laurensorensen current data has been added to production ASpace, so everything there is ready for you to edit. going forward we're going to index EAD generated from production ASpace in both environments of the app, so #368 may not be necessary (or at least low-priority). lmk if that doesn't make sense
@thatbudakguy when I try and access http://spec-as-prod.stanford.edu:8080/ I am only able to select Spec as the repository. Am I looking in the wrong place?
I can access the VT repository there using the nta_app_prod account — maybe it's a permissions issue? @marlo-longley do you know?
Update: credentials all good.
This is all entered!