-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feature/fdo update #116
Feature/fdo update #116
Conversation
southeo
commented
Dec 9, 2024
- align with fdo 1.0
- introduces "unrecognized" fdo property as a small workaround in the mongodb layer so the handle api won't crash if a pid record has a property from a previous version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment about license
"mediaHost", | ||
"mediaHostName", | ||
"linkedDigitalObjectPid", | ||
"linkedDigitalObjectType", | ||
"primaryMediaId" | ||
"primaryMediaId", | ||
"license", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
license
is a required field but in the Service I don't think we actually set license
. Couldn't that create a potential issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok this should be removed, also made a pr on opends. If we don't have a license in the FDO record I think we'll somehow survive
Quality Gate failedFailed conditions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗂️