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

🚧 Knapsack EPIC #9

Closed
wants to merge 22 commits into from
Closed

🚧 Knapsack EPIC #9

wants to merge 22 commits into from

Conversation

ShanaLMoore
Copy link
Contributor

@ShanaLMoore ShanaLMoore commented Feb 23, 2024

Story

Related

Refs #issuenumber

Expected Behavior Before Changes

Expected Behavior After Changes

Screenshots / Video

Notes

Shana Moore added 8 commits February 23, 2024 04:33
i2-knapsack-pals is i35-valkyrize-hyku + contributions from the pals knapsacking process
trying to get the app to spin up after knapsacking
@ShanaLMoore ShanaLMoore changed the title 🚧 WIP 🚧 Knapsack EPIC Feb 28, 2024
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Contribute back to hyku?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

contribute back to hyku?

LaRita Robinson and others added 10 commits March 21, 2024 11:03
The structure of the stored collection type gid changed in Hyrax 3.0

A rake task is needed to update the collection_type_gid that is stored
on the collection as part of the upgrade from Hyrax 2.x process. This
references the logic from the rake task that Hyrax has in versons 3 & 4,
and updates it to work within Hyku tenants.

The definition of collection_type_gid= changed in Hyrax 5.0. This
rake task is known to work for updates to versions prior to Hyrax 5.
Functionality for later versions is unknown.
Prior to this commit we were blanket checking CSV recores for the
presence of title and resource_type.  The problem with this approach was
that all models were being checked for these fields while not all models
required these fields, such as the Collection and FileSet models.

In this commit we leverage the exisiting `Bulkrax::CsvParserDecorator`
to check each model's actual required fields according to their
respective forms (minus the FileSet which do not have required fields)
and add logic to check any custom parser mappings according to the
bulkrax initializer and also any numbered fields.  The error message was
also changed to indicate which model was missing what required field(s).

Ref:
  - notch8/palni-palci#436
This commit makes it so we can use Bulkrax to import locations into the
based_near property.  It also will work for invalid locations.
This commit will fix a bug where if the csv has a `location` header but
no value.
This commit will adjust the Bulkrax csv parser fields to allow spaces in
the csv headers.  Previously, if you had `rights statement`, this header
was not accepted.  With this commit it will be.
@ShanaLMoore ShanaLMoore requested a review from jeremyf March 21, 2024 18:38
@ShanaLMoore
Copy link
Contributor Author

ShanaLMoore commented Mar 21, 2024

Acknowledging that I've noticed and will look into the recent build issue

@ShanaLMoore
Copy link
Contributor Author

ShanaLMoore commented Mar 21, 2024

I don't understand the failing build's error:

image

This branch exists in hyku_knapsack.

i can build and bundle successfully, locally

@ShanaLMoore ShanaLMoore closed this Apr 4, 2024
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.

2 participants