Questions and practicalities
- Troubleshooting production DB connection problem?
- Environment var management? envyable? blacklight secret.
- How does hydra/fedora handle preservation? E.g. checksums.
- What are the encoding defaults of metadata and databases in Hydra?
- what data modeling needs to be done in addition to what fedora / hydra already provide (or will provide)?
- is XML completely deprecated in fedora 4?
- Doesn't sound like it. Get more info. Mark recommends examining your use cases – legacy XML from fedora 3? maybe model it that way for fed4.
- how / when is bagit used with fedora? hydra?
- default URIs? Should these be changed? If so, to what?
- DEFER (may not be relevant): what are the graph manipulation tools in fedora? how are these accessed from hydra? Or is it just taken care of when API requests are made?
- Re: audit service: what is a premise?
- Re: Ordering, what is a proxy? Also has a meaning outside the context of ordering.
- What db are most people using? postgres? How to move from sqlite to postgres?
- What does it look like to upgrade?
- How to curate, manage, maintain a set of test files / data?
General notes
Reindex everything into Solr from Fedora!
- ActiveFedora::Base.reindex_everything
opaquenamespaces: a community registry / namespace for RDF properties. Probably best practice to try to put locally-required properties there or somewhere similar. This was started by Karen and Tom at U Oregon.
Page numbers: can use this as literal sequence and put marked pagenumbers in page label property.
Book.where(title:"hat") # note this returns an array, not a single book object
re: IDs. consider using the default id as an internal identifier and another field as a local id for human use.
http://demo.curationexperts.com/
one challenge of hosting on amazon is moving large files around. sufia uses ffmpeg and converts them to playable proxies. anything that can be handled by imagemagick, openoffice / libreoffice (creates a thumbnail from the first page of the doc)