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.)

Very slow

Extra Release, pid assignment etc. is necessary

Open Questions:

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:

The item (image) itself will be stored in eSciDoc

Open Questions:

All metadata are stored in a triple store, all operations (search, update etc.) can take place here.

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)

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:

We do not use eSciDoc at all. Open question, what to use as storage? Fedore, DB?

Would be much faster

Services can not be reused

High development effort

Open Questions: