Imeji Performance eSciDoc
|
This is a protected page.
eSciDoc ItemHandler[edit]
All metadata are stored in an eSciDoc item. The item is updated etc. via the eSciDoc item handler.
Fast development, as already implemented in other solutions
- All eSciDoc services can be used (versioning, statistics, aa etc.)
Very slow (approx. 2,2 sec for one item (update, submit, pid, release))
- Extra release, pid assignment etc. is necessary
Open Questions:
eSciDoc ContentRelation[edit]
All metadata are stored in a content relation object, which is related to the item (image).
For a metadata change, the content relation only needs to be updated (no extra release, pid assignment etc.)
To be checked if fast enough
Open Questions:
- Is a content relation under version control?
- No, it is not under version control
- How is the aa for content relations?
- same principle as for items, excluding versions
eSciDoc only as archive[edit]
The item (image) itself will be stored in eSciDoc, together with the technical metadata.
Open Questions:
- Is there a set of 'core' metadata we have to/ should store with the item for LTA reasons?
- any metadata are subject to LTA, in addition, PREMIS event history is tracked for items/containers
MD in Triple Store[edit]
All metadata are stored in a triple store, all operations (search, update etc.) can take place here.
The triple store would know the eSciDoc id of the image item, but the image item would not know its metadata in the triple store.
Very fast (30,000 items in 2 seconds)
- items or triples?
synchronization issues
- redundant data
- aa has to be implemented
Open Questions:
- How can we synchronize the two systems? (Do we have to synchronize them at all, or is sufficient to store the md only in the triple store?)
- How do we perform status updates? (escidoc has to know the status, not only the triple store)
eSciDoc Core Performance Tuning[edit]
Update eSciDoc core, so that retrieval of items are faster.
All solutions could profit from this
Development has to be together with FIZ, so that we do not develop our own eSciDoc which we have to adopt with every FW release.
- Development process can be very long
- Code seems to be complex to understand
Open Questions:
- Would FIZ be willing to provide development resources to perform this task?
No eSciDoc[edit]
We do not use eSciDoc at all.
Can be much faster
Services can not be reused
- High development effort
Open Questions:
- What to use as storage? Fedora, DB?