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

Update Hyku submodule 2024-11 #274

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from
Draft

Conversation

bkiahstroud
Copy link
Contributor

We're primarily upgrading to bring in the per-tenant Bulkrax field mappings feature. However, many other changes and bug fixes are included

We're primarily upgrading to bring in the per-tenant Bulkrax field
mappings feature. However, many other changes and bug fixes are included
Brings in fixes for views and branding
Thanks to a new feature in Hyku, Bulkrax field mappings will be
configurable on a per-tenant basis via an Account setting. This method
should be favored over configuring field mappings in the knapsack
initializer; new Accounts will be initialized with the default field
mappings configured in Bulkrax, so adding customizations to them at this
level is unnecessary and may cause confusion
Comment on lines +9 to +17
based_near:
type: string
multiple: true
form:
primary: false
index_keys:
- "based_near_sim"
- "based_near_tesim"
predicate: http://xmlns.com/foaf/0.1/based_near
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might break things if we don't override the other work type's schemas... (GenericWork, Image, etc)

Brings in Bulkrax mappings-related bug fix as well as UI fixes
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

Successfully merging this pull request may close these issues.

1 participant