...
- hydra.chemheritage.org is production server - encryption for passwords
- staging server still at staging.hydra.chemheritage.org - no encryption for passwords, so use a fake one!
- Digital Collections team will continue to use both the staging and production server.
- Collection template has been stripped down - need larger discussion on what metadata fields needed for collection rather than item
- Items have been ingested from digital collections team first. Cat processed Hillary's Norda collection. Beckman digital archive team (Sarah and Megan) are now beginning to ingest for Beckman Legacy Project archival project.
Discussion of cloud server back-up strategies
...
- Demo pulling Sierra record info via bib number.
- Sierra data appears in a box that can be cut and pasted into fields
- Box will later disappear and fields will populate, but future mapping work required: probably different per department, and may be differences between items in a single department (i.e. plates versus entire works for rare books)
- Could be something to mention to Innovative that we're using their API - fits use cases identified in their brochure: https://www.iii.com/sites/default/files/APIs_Case_Study.pdf
- API pulls one way, one time, from the opac into Hydra. Not syncing. In the future,if changes are made to a record in the opac, they will have to be manually changed in Hydra
Plans and Priorities for the Year
...