...
- To discuss ? 1.5 Themes: Not used in CineFiles-XDB, but might be a good feature if done right in CSpace. Would it be possible to combine with subject headings or genres? Needs more thought, but could help automate something done by hand now.
- Add Themes concept vocabulary (would be hierarchical in order to support sub-themes).
- 9/26/2013: Might be worth having the vocabulary and field, but do data work later or BAMPFA can do by hand.
- To discuss ? Maybe no work in CSpace needed, but need to doublecheck what happens with docs that have the same name. Document "display name" derivation for disambiguation. This might only be needed in denorm tables and reports (i.e., no work in CSpace) When looking at a Film (works authority) record, related documents will appear in the right frame under "Used By". We can display the Document title and one additional field in the list, maybe the author, source, or year?
- Author and Title would probably be sufficient, but it's possible we would need to create a derived column that holds more information, like XDB does now.
- Author and Title should be OK.
- To discuss with Glen ? 2 Collect more image metadata on ingest (color model, pixel depth, compression): Glen has this information now, but it's not clear it's needed. Is this relevant to future asset management? Can it be added later?
- To discuss with Nancy and Glen: 2 Copyright holder: A set of screens built in XDB that are not currently used. Functions currently used in a FileMaker db; would love to integrate with CSpace when possible.
- Glen and Nancy would like to revisit this because the Access Code model is complex. We could have a field on Document that was "Copyright Holder" and the access code for that person or organization record could determine sharing directly. How would we populate this data on migration?
- Mapping in FileMaker data and functionality might be too big for this exercise.
- 9/26 idea: Add a copyright holder field to identify documents where the copyright holder is not the source (publisher). Would we migrate data for that? Going forward, would users enter both source and copyright holder?
- To discuss but maybe a 2. On person do we need checkboxes for: Is Director? Is fully indexed? Needs indexing? This is to support http://www.mip.berkeley.edu/cinefiles/Directors.jsp and http://www.mip.berkeley.edu/cinefiles/BrowseBayAreaFilms.jsp and http://www.mip.berkeley.edu/cinefiles/BrowseDirs.jsp Need workflow for maintaining this information. Currently this is maintained by hand. Most important is tracking the info with checkboxes and allowing info to be extracted to web site. Nice to have: Reports and workflows for identifying updates.
- Future probably
- To discuss? 2 Asset Management procedure and data.
- Need to have a design discussion about access rights. Needed for DAM requirements that CSpace advisory group is interested in.
- NLG has a FileMaker database for rights clearance (sounds like a new procedure)
- Glen: Could have a field for Copyright Holder (on Document), but (NLG), this changes over time, so it needs to be repeatable. How would we migrate data into this?
- Future probably
- 2 or 3 Need a "Download image with original filename" button or batch process. Original TIFF or derived JPEG? (Done from web site so probably not important)
- Might work from CSpace already
- 3 Object-persistent templates (document, poster)
...