PubMan Func Spec Export/OAI Data Provider
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
- As contexts are only administrative objects, we will not offer them for OAI-PMH, they even have no PID. In previous discussions we agreed that if we want to have sets equal to contexts, we will all objects to a Container. --Natasa 08:50, 16 December 2008 (UTC)
eSciDoc:Solution:OrgUnit
eSciDoc:PubMan:Yearbook --Natasa 08:50, 16 December 2008 (UTC)
- --Natasa 09:16, 16 December 2008 (UTC)Sets can also be defined by subject category or other controlled vocabulary, such as:
- eSciDoc:Faces:Young
- eSciDoc:PubMan:physics
- eSciDoc:PubMan:OpenAccess
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 |
- As stated above, both Sengbusch and PL_Grey_Material shall have extra Containers if we would like to offer them as sets --Natasa 08:52, 16 December 2008 (UTC)
General Ideas[edit]
- The sets can be retrieved via filter function (Filter needed for Solution, orgUnits, Contextes)
- Sets can be defined as "saved filters" with description and defined criteria
- 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.
- what is the idea behind having export format oai-pmh? The oai-pmh is separate interface. Via this interface we can offer repository content in several metadata formats. --Natasa 09:37, 16 December 2008 (UTC)
- The Data acquisition service provides fetching of the standard oai-pmh sets.
- why would data acquisition service provide fetching of the oai-pmh sets? My understanding was that the data acquisition service provides fetching a single record from external/internal source and offering this very same record into another format. Actually, the question is why would data acquisition service had knowledge on oai-pmh sets? --Natasa 09:37, 16 December 2008 (UTC)
- The set description is generated dynamically because it will contain all orgUnits and Contextes
Comments[edit]
- Does it make sense to export all eSciDoc items?
- according OAI-PMH specification, yes
- Does it make sense to export all items of a solution?
- yes
- Do we provide only released item metadata over oai interface?
- released and withdrawn items. Withdrawn items should be with status "deleted" in the header response. --Natasa 09:13, 16 December 2008 (UTC)
- OAI-Data provider interface is implemented for the eSciDoc repository
- OAI-Data provider shall allow defining sets and providing set description
- Usage of ListRecords/List Identifiers verb of OAI-PMH interface could be invoked for a particular set, or without set parameter
- if invoked without set parameter it shall provide information on sets in which this record/identifier is "grouped"