Difference between revisions of "PubMan Func Spec Export/OAI Data Provider"
Jump to navigation
Jump to search
Kleinfercher (talk | contribs) m |
m (→Scheduled) |
||
Line 3: | Line 3: | ||
==Scheduled== | ==Scheduled== | ||
for PubMan R5 | for PubMan R5 | ||
==Definition== | ==Definition== |
Revision as of 08:48, 16 December 2008
Description[edit]
A set is an optional construct for grouping items for the purpose of selective harvesting.
Scheduled[edit]
for PubMan R5
Definition[edit]
TODO:
- what would be good criteria to define sets?
- what kind of sets we would like to provide to outside?
- to be able to check if the set definition can be fulfilled by filters
- FIZ will check if it is able to expose filters as sets
- MPDL will check better requirements and put on Colab
OAI-PMH Set Definition[edit]
eSciDoc
eSciDoc:Solution
eSciDoc:Solution:Context
eSciDoc:Solution:OrgUnit
Examples:
Requirement | Set |
---|---|
Get me all PubMan items of my institute | eSciDoc:PubMan:MPDL |
Get me all YearBook PubMan items | eSciDoc:PubMan:Yearbook |
Get me all items from Collections MPI/PL Grey Material | eSciDoc:PubMan:MPI/PL_Grey_Material |
Get me all Pictures from FACES | eSciDoc:FACES |
Get me all PubMan items from Sengbusch Collection | eSciDoc:PubMan:Sengbusch |
General Ideas[edit]
- The sets can be retrieved via filter function (Filter needed for Solution, orgUnits, Contextes)
- The search&export interface can be enhanced with export format 'oai-pmh'. Where the user can define his own oai-pmh set via the search function.
- The Dataacquisition service provides fetching of the standard oai-pmh sets.
- The set description is generated dynamically because it will contain all orgUnits and Contextes
- Only the metadata of relesaed items can be exported
Comments[edit]
- Does it make sense to export all eSciDoc items?
- Does it make sense to export all items of a solution?