A.5 Define the interface for the Fedora/BitFinder repository
State: In progress
Time used: 0 md.; iteration 11: 2 md
Depends Upon
Description
For systems to interact with the DOMS repository, it needs an interface. The goal of the task is to define this interface. It is clear that for different systems, the interface will be different.
This list encompass the as yet needed interfaces:
- DOMS must support OAI-PMH harvest
There must be a standard for Batch ingest (see TaskA.4)
- There must be an interface for the Summa system (Probably based around a Lucene index made with Gsearch)
- There must be a Java interface for the GUI, which might just be native calls for the Fedora API and direct manipulation of the Bitstorage, or something more elaborate
- There must be an interface for the Validation service
Sub tasks
Documentation
Parent task
Progress history
Iteration | Time used | Status | Notes | |
ActionBitStorageWebservice | 15 | 0md | In progress (semi-done) | |
ActionBitStorageWebservicePartTwo | 16 | ½md (BAM) | Finished. | Need fix todos action later |
ActionFedoraApiEvaluation | 10 | 0md | Finished | Evaluate the Fedora 3 API. Decide whether or not it will be suited as the interface to the DOMS system. |
ActionFedoraXACML Evaluation | 10 | 3md | Finished | Evaluate if the Fedora XACML authorization system is sufficient for DOMS |
ActionHowToDeleteObjects | 14 | 0.5md | Finished | |
ActionRISearchWrapper | 14 | 2.5md | Finished | |
ActionTestbedBitStorage | 12 | 0.5md (ABR) | In progress | |
ActionTestbedPIDGenerator | 11 | 5md | Finished | |
ActionTestbedSearch | 12 | 3md | In progress | Code style and review needed |