...
- 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!
- only metadata Collection template has been stripped down - need larger discussion on what metadata fields needed for collection rather than item
Discussion of cloud server back-up strategies
...
- Demo pulling Sierra record info via Bib Number. 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
Plans and Priorities for the Year
- P/T Collections Photographer hire - will have one-on-one meetings with different curators to test workflow
- Anna's maternity leave: no Hydra development March - June 2016
- Priorities for Summer and Fall include: implementing works (not just files); adding user roles; finish Sierra API based on feedback for mapping
- IMLS grant application submitted: focus on adding linked data capabilities to Hydra and improving authority control for metadata (Ask Michelle if you want a copy of the abstract or narrative)
- Critical mass for show? Could potentially show the Board at the October meeting. Waiting for website revisions and rebranding before we put any work into public-facing user interface