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 service can be used (versioning, statistics, aa etc.)
- 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.)
Open Questions:
eSciDoc only as archive[edit]
The item (image) itself will be stored in eSciDoc
Open Questions:
MD in Triple Store[edit]
eSciDoc Core Performance Tuning[edit]
Update eSciDoc core, so that retrieval of items are faster.
All solution 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
Open Questions:
No eSciDoc[edit]
We do not use eSciDoc at all. Open question, what to use as storage? Fedore, DB?
- High development effort
Open Questions: