Difference between revisions of "Imeji Performance eSciDoc"

From MPDLMediaWiki
Jump to navigation Jump to search
(new page)
 
Line 2: Line 2:


== eSciDoc ItemHandler ==
== eSciDoc ItemHandler ==
All metadata are stored in an eSciDoc item. The item is updated etc. via the eSciDoc item handler.
[[Image:Happy.gif | 20px]] Fast development, as already implemented in other solutions
: All eSciDoc service can be used (versioning, statistics, aa etc.)
[[Image:Sad.gif | 20px]] Very slow
: Extra Release, pid assignment etc. is necessary


== eSciDoc ContentRelation ==
== eSciDoc ContentRelation ==
All metadata are stored in a content relation object, which is related to the item (image).
[[Image:Happy.gif | 20px]] For a metadata change, the content relation only needs to be updated (no extra release, pid assignment etc.)
[[Image:Sad.gif | 20px]] To be checked if fast enough


== eSciDoc only as archive ==
== eSciDoc only as archive ==

Revision as of 08:49, 31 May 2010

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.

Happy.gif Fast development, as already implemented in other solutions

All eSciDoc service can be used (versioning, statistics, aa etc.)

Sad.gif Very slow

Extra Release, pid assignment etc. is necessary

eSciDoc ContentRelation[edit]

All metadata are stored in a content relation object, which is related to the item (image).

Happy.gif For a metadata change, the content relation only needs to be updated (no extra release, pid assignment etc.)

Sad.gif To be checked if fast enough

eSciDoc only as archive[edit]

MD in Triple Store[edit]

eSciDoc Core Performance Tuning[edit]

No eSciDoc[edit]