Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate and map Primary Set values to OAI Collection #257

Open
wickr opened this issue Jan 21, 2021 · 3 comments
Open

Migrate and map Primary Set values to OAI Collection #257

wickr opened this issue Jan 21, 2021 · 3 comments

Comments

@wickr
Copy link
Member

wickr commented Jan 21, 2021

Primary Set values will also need to be mapped to OAI Collections in OD2. These aren't yet made, but will function in a similar way, with membership limited to one.

Will likely need a mapping file to handle pid differences.

Related to #30

@lsat12357
Copy link
Contributor

can the new collections be the coll ids + "-oai"
like ken-gray-oai
then just a little bit of extra code can be added to admin_set_membership_service to add the oai coll to the member_of_collections_attributes hash

@lsat12357
Copy link
Contributor

lsat12357 commented Jun 9, 2021

collection type is oai_set
check to make sure this type exists before generating all the oai_sets

@lsat12357
Copy link
Contributor

lsat12357 commented Jun 9, 2021

anything with a primarySet gets an oai_set, but are there any assets with primarySet that are restricted?
if so, may need logic to prevent an oai_set being assigned.
ok there are definitely assets with primarySet but are restricted. could remediate, but primarySet is useful for setting adminSet.
Solution: reverse order in stack, so that visibility runs first.
check if visibility==open before adding oai_set to the work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants