-
Notifications
You must be signed in to change notification settings - Fork 0
Repository Development Roadmap
Jim Coble edited this page May 20, 2015
·
9 revisions
- Target: June 30, 2015
- Issues
- Support for Simple Ingest Format
- Released: May 19, 2015
- Issues
- Behind the scenes change to handling of descriptive metadata in batch processing
- Groundwork for role-based authorization
- Permanent ID added to staff views
- February 4th, 2015
- Issues
- ARK Persistent Identifier integration
- February 11th, 2015
- Initial public access interface
- [Issues] (https://github.com/duke-libraries/ddr-public/milestones/v1.0)
- Released: September 24, 2014
- Composite object creation (item + component(s) in one step) DONE
- Migration of descriptive metadata from XML to RDF implementation DONE
- Change default storage type for content to external DONE
- Migration of content to external files (i.e., not "managed" by Fedora)
- Ruby 2.1, Rails 4.1, hydra-head 7.2, active-fedora 7.1, Blacklight 5.5 DONE
- Merge AdminPolicy functionality into Collections DONE
- Issues
- Released: June 26, 2014
- Upgrade to hydra-head 7.0 DONE
- Accommodate Duke Core in descriptive metadata DONE
- Issues
- Released: March 31, 2014
- Web interface for single object submission [postponed from 1.3]
- Ability to upload content [postponed from 1.3]
- Web interface to ingest a spreadsheet of Qualified Dublin Core descriptive metadata [postponed from 1.3]
- Issues
- Released: December 19, 2013
-
Web interface for single object submission[postponed to 1.4] - Ability to edit descriptive metadata [DONE]
-
Ability to upload content[postponed to 1.4] - Web interface to ingest a batch of content files [DONE]
-
Web interface to ingest a spreadsheet of Qualified Dublin Core descriptive metadata[postponed to 1.4] - Integration of Grouper groups for access controls. [DONE]
- Issues
- Released: October 29, 2013
- Integrate with Shibboleth for user authentication
- Improved user experience for batch ingest
- Persist batch fixity check records in database [postponed from 1.1]
- Issues
- Released: August 19, 2013
- Refactored batch ingest process
-
Persist batch fixity check records in database[postponed to 1.2] - Enhanced search options (e.g., by PID)
- Issues
- Criteria for initial production release
- Implemented on production server [DONE]
- Vica and Kwilecki collections ingested [DONE]
- Following user stories supported:
- ITS staff, using data supplied by DPC and other library staff, can ingest batches of existing DPC digital collections [DONE]
- Designated stakeholders receive copies of the validation logs produced by the batch ingest process [DONE - can be emailed following ingest]
- Fixity checks are run against ingested digital content periodically
- A small group of library staff can log into the repository and perform the following actions:
- Browse the objects in the repository [DONE]
- Search for objects in the repository by identifier and title [DONE]
- View all the datastreams associated with an object and all other objects related to that object (e.g., parent object, child objects, preservation events, image targets, and stored derivatives) [Recommend removing "stored derivatives" from this list -- not needed for Vica or Kwilecki]
- Retrieve one or more images for delivery to a third party [DONE]
- Issues remaining to be resolved
- Descriptive metadata mapping to Qualified Dublin Core, at least for Vica and Kwilecki collections [DONE ... will use TripodMETS descriptive metadata as basis]
- Uses made of file characterization data for digital content files and whether such data is stored in the repository [DONE ... won't store JHOVE data in object]
- Preservation event metadata practices [DONE]
- Reporting needs [Find out if anything in particular is needed for v1.0.0]
- Admin policy naming convention [DONE]
- Default permissions policies [Don't think we need to worry about this for v1.0.0]
- Remaining software development tasks
- View object audit trails [DONE]
- View object preservation events [DONE]
- Fixity check regime implemented
- Implement Target model [DONE]
- Define and implement Derivative model [Recommend removing from this milestone -- not needed for Vica or Kwilecki]
- Implement image delivery service for use by staff [DONE]
- Complete administrative interface [DONE]
- Preservation events get assigned an admin policy [DONE]
- Implemented catalog-based views for listing Collections, Items, and Components; index controller actions and view templates removed for those models.
- Customized catalog show view; Collection, Item, and Component show actions and view template removed.
- Datastream views added.
- #new, #create, #edit, #update, #destroy actions removed from model controllers.
hydra-head 5.4.0
- hydra-head 5.2.0
- blacklight 4.0.1
- rails 3.2.11
Initial numbered version