You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why are we doing this? What user stories does it support? What is the expected outcome?
Currently, there is no support for different record data models (f.e. LOM, Marc21). Modules that bring support for other record data models should also have their own elasticsearch index (f.e. lom-records, marc21-records), database tables, services, etc., as the metadata format differs from rdm-records.
This change would allow other modules to hook into the invenio-oaiserver module and provide the respective records via the OAI protocol, without having to implement this themselves.
Outcome is to have one endpoint for a combined harvesting possibility of all records - no matter the model. Further filtering can be achieved via sets.
Summary
What are you proposing to change (high-level overview only)?
Introduce data model configuration variable(s) which other modules can extend
Motivation
Currently, there is no support for different record data models (f.e.
LOM
,Marc21
). Modules that bring support for other record data models should also have their own elasticsearch index (f.e.lom-records
,marc21-records
), database tables, services, etc., as the metadata format differs fromrdm-records
.This change would allow other modules to hook into the
invenio-oaiserver
module and provide the respective records via theOAI
protocol, without having to implement this themselves.Outcome is to have one endpoint for a combined harvesting possibility of all records - no matter the model. Further filtering can be achieved via sets.
Summary
OAI-PMH
verbs to take data model configuration into accountResources
2 days per week from my side (as of right now)
The text was updated successfully, but these errors were encountered: