Version 12 (modified by, 9 years ago) (diff)


T9) Digital Object Archive Service

User Workspace and Archive Services

1) Goals

2) Tasks

Start with CNRI prototype digital object archive service
Plan transition to use of iRODS service
How to move data to service: move file; move SQL DB; or?
How is persistent object identifier (i.e., handle) generated? also registered? and later resolved? Include necessary Object Identifier (OI) service. How are partitions for different users managed?
How is data in MDOD used to set archive sharing policy? what is required in MDOD?
Operations plan for Digital Object Archive Service.

3) Team

Co-LEAD Giridhar Manepalli (CNRI)
Co-LEAD Shu Huang (RENCI)
Larry Lannom (CNRI)
Wesley Wu (U Kentucky)
Hussam Nasir (U Kentucky)
Chris Small (NetKarma, IU)
Jeannie Ohren (GPO)

4) Meetings

(organized calls or meetings before GEC13?)

Review conclusions in pre-meeting at GEC13

Review with working team at GEC13

5) Open Issues

6) Definition of DOA Service

The CNRI prototype Digital Object Archive (DOA) service was based on this original configuration:

The current view of the User Services in the User Workspace is shown in the following figure.

Here, several services in the original configuration are gathered together into the "Directory Archive" service in the User Workspace; among other functions, they define an object, and then push it to the DOA Service.

Also included in the User Workspace is an "MDOD Creator/Editor" service, that interacts with an "Object Identifier (OI)" service to get a unique persistent identifier (e.g., a handle). Several functions of this service were included in the CNRI prototype Digital Object Archive (DOA) service.

A DOA service, and an associated OI service, must be built to match this configuration. At first, the DOA service should be based on the CNRI prototype DOA service, and then it should be based on the iRODS service.

Attachments (2)

Download all attachments as: .zip