Component | Tasks | Responsible | Dependencies? |
|---|---|---|---|
| DAMS | Nail down what we want users to see when they log in, e.g. view and directory structure | Adrian | |
| Implement any changes to Nuxeo UI to reflect above | Brian | ||
| Sketch out a load schedule/profile clusters for Nuxeo with UCB staff | Brian | ||
| Test load content on stage through ETL process (platform importer) | Brian | ||
| Add representative content from as many campuses as possible | Adrian | ||
| Send hard drive to UCSC | Sherri | ||
| Collection Registry | Refine the Read-Only UI so it is "prime time" ready - Done | Mark/Amy/Sherri | |
| Verify data model and what data is actually there/where it's coming from - Done | Mark/Sherri/Adrian | ||
| Hookup the "login" functionality - Done | Mark/Amy | ||
| Make selected fields editable - Done, but more to come | Mark/Amy | ||
| Follow up with Heather and Matt on digitization workflow fields for Aggie | Sherri | ||
| Decide on how we need to indicate "status" for our own purposes (e.g. content in hand, etc.) and implement in UI | Sherri | ||
| Take another pass at data currently in there and clean it up, as needed, for viewing | Adrian | ||
| Take a pass at an accessibility test for CR - Done for read only, need to figure out how to test the editing interface – maybe open up the dev machine with standard django auth | Mark | ||
| Central Index/API | Harvest some content from eScholarship and/or WAS and have it appear in demo interface - Have harvested escholarship entries from the following collections:
| Mark | |
| Put the API on a production URL - Currently it is just the Solr std API on registry.cdlib.org:8080 | Mark | ||
| Develop a policy/disclaimer for the API and determine how to release this | Sherri | ||
Start to scope out the harvest API in consultation with UCLA, UCSB, and UCSD - Had a good discussion with UCSD  , more to come... | Mark | ||
| Public Interface | Determine graphic design needs and resource requirements | Sherri | |
| Conduct a "literature review" of previous work related UX; unpack what can be applied to UCLDC and where there are still holes | Sherri | ||
| General (cuts across components) | Define who will have access to what at release / how broadly to circulate URLs / general communications strategy | Sherri | |
| Create documentation for the login workflow for both Nuxeo and Collection Registry | Sherri/Adrian | ||
| Create documentation on what we are asking key campus staff to do at this point (ie Collection Registry data) | Sherri/Adrian | ||
| Tackle any remaining/additional Shibboleth questions (as needed) | Brian | ||
| Schedule Nuxeo training | Adrian | ||
| Receive initial input from PSG on metadata scheme | Adrian/Sherri | ||
| Create UCLDC email and Salesforce cases view for feedback | Sherri | ||
| Set up production environments | Brian | Delivery of prod. from unix group |
This is a public wiki space. All contents are publicly accessible unless page restrictions are in place.
Overview
Content Tools
