As a repository admin, I want to be flexible in defining OAI-PMH Sets from the list of DOIs

[RightInTwo]

Using Selective Harvesting and Sets, I would like to define OAI Sets for different purposes:

• A set for each unit of our institute (that has data publications)
• A set for each researcher of our institute (that has data publications)
• A set for the (whole) institute

Alternatively it could be just the set for the institute, but then the information about the unit/researcher assignment would need to happen on the server side, making this project much more complicated. The first solution (with multiple sets) would allow to make these assignments when defining (through the API) which DOIs belong to a set.

[tcoupin]

First, we can do with a file hierarchy ?
Example:

set sub1.1 = DOI1+DOI2
set sub1.2 = DOI3
set folder1 = DOI[1-4]
set folder2 = DOI5
set root (=all) = DOI[1-6]

[RightInTwo]

I thought that this would be handled by the database. But maybe I don't understand the folder concept - can you elaborate?

To illustrate my understanding of it, I extended my existing doi list with two more tables. One to define a list of sets and one to map dois to sets:

[tcoupin]

I understand that the dois table is used to cache metadata (fields oai_dc and oai_datacite)? For a first milstone, I suggest to request doi metadata on oai-pmh request. it will save us from having to manage periodic harvesting.

Folder is only a graphical concept

et getDois return dois of current folder and call getDois on his children

[RightInTwo]

I understand that the dois table is used to cache metadata (fields oai_dc and oai_datacite)? For a first milstone, I suggest to request doi metadata on oai-pmh request. it will save us from having to manage periodic harvesting.

Ok, it's a good idea to KISS it for a first milestone.