Difference between revisions of "Imeji Performance eSciDoc"
Kleinfercher (talk | contribs) |
Kleinfercher (talk | contribs) |
||
| Line 9: | Line 9: | ||
[[Image:Sad.gif | 20px]] Very slow | [[Image:Sad.gif | 20px]] Very slow | ||
: Extra Release, pid assignment etc. is necessary | : Extra Release, pid assignment etc. is necessary | ||
'''Open Questions:''' | |||
== eSciDoc ContentRelation == | == eSciDoc ContentRelation == | ||
| Line 16: | Line 18: | ||
[[Image:Sad.gif | 20px]] To be checked if fast enough | [[Image:Sad.gif | 20px]] To be checked if fast enough | ||
'''Open Questions:''' | |||
== eSciDoc only as archive == | == eSciDoc only as archive == | ||
The item (image) itself will be stored in eSciDoc | |||
'''Open Questions:''' | |||
=== MD in Triple Store === | === MD in Triple Store === | ||
== eSciDoc Core Performance Tuning == | == eSciDoc Core Performance Tuning == | ||
Update eSciDoc core, so that retrieval of items are faster. | |||
[[Image:Happy.gif | 20px]] All solution could profit from this | |||
[[Image:Sad.gif | 20px]] 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 == | == No eSciDoc == | ||
We do not use eSciDoc at all. Open question, what to use as storage? Fedore, DB? | |||
[[Image:Happy.gif | 20px]] Would be much faster | |||
[[Image:Sad.gif | 20px]] Services can not be reused | |||
: High development effort | |||
'''Open Questions:''' | |||
[[Category:Faces 4.0| Metadata Update]] | [[Category:Faces 4.0| Metadata Update]] | ||
Revision as of 09:08, 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.
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:
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:
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?
Would be much faster
Services can not be reused
- High development effort
Open Questions: