...
- 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? Talk to Glen about data for overrides currently. NLG: Really this is a history so should it be repeating (copyright holder, dates, notes).
- 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
...