-
Notifications
You must be signed in to change notification settings - Fork 1
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
Valkyrie: Blank metadata properties should not display on the show page #771
Comments
Today I created one of every work type through the UI. I uploaded PDFs to every type. One one work, I uploaded a folder (compound work). I only entered the required metadata of title and rights. Here is what I'm seeing that I don't expect:
|
This commit is a temporary solution to prevent blank metadata fields from rendering. There is a bigger issue of why some fields are being assigned values of `[""]` but this commit solves the current issue. Ref: - #771
We created a solution for this problem but there is more to be done in the future: #807 |
# Story This commit is a temporary solution to prevent blank metadata fields from rendering. There is a bigger issue of why some fields are being assigned values of `[""]` but this commit solves the current issue. Ref: - #771 # Expected Behavior Before Changes Some metadata fields that did not have content were rending on the works. # Expected Behavior After Changes Only metadata fields that have content will render. # Screenshots / Video Before:  After: <img width="1220" alt="Screenshot 2024-09-12 at 3 55 31 PM" src="https://github.com/user-attachments/assets/703b9082-fe6a-44e9-85c8-b4db8f96c74e"> # Notes This is a temporary solution to solve the current needs of the client.
QA RESULTS: ❌ NEEDS REWORKtested on STAGING I created a conference item and filled in only the required fields.
I created a collection and filled in only the required fields.
|
This commit modifies the metadata yaml files for collections and all work types removing the 'm' from solr index keys for values that contain `multiple: false`. This fixes the issue of rendering blank metadata fields for all items except author (creator). It does not fix the underlying issue of fields being assigned `[""]` when they should be `[]`. Ref: - #771
This commit updates the version of the order-already gem to 0.3.2. This version of the gem handles blank values preventing blank fields from being assigned `[""]` instead of `[]`. Ref: - notch8/adventist_knapsack#771
This commit updates the version of the order-already gem to 0.3.2. This version of the gem handles blank values preventing blank fields from being assigned `[""]` instead of `[]`. Ref: - notch8/adventist_knapsack#771
This commit reverts the temporary fix of managing blank fields that persist as an emptry string in an array `[""]` due to a better solution being found. Ref: - #771
Updates Hyku main to include the most recent version of the order_already gem. Ref: - samvera/hyku#2334 - #771
# Story Blank metadata properties should not display on the show page for collections or works. Refs - #771 # Expected Behavior Before Changes Some metadata fields that did not have content were rending on the catalog page, the works show page, and the collection show page. # Expected Behavior After Changes Only metadata fields that have content will render. # Screenshots / Video - Catalog page <img width="1557" alt="Screenshot 2024-09-19 at 3 48 12 PM" src="https://github.com/user-attachments/assets/9311be82-a08b-4b95-9b4e-0ae5674e317d"> - Works show page  - Collection show page 
QA Results: ✅ PASSPLEASE NOTE, if you still see blank fields on pre-existing works, it needs to be reindexed. Until we perform a full reindex on the entire system, you can trigger it manually. Edit and save the work or collection without making changes. WORK ✅ PASSTest on STAGING I filled in only the required fields (title and rights statement):
COLLECTION ✅ PASSTested on STAGING I filled in only the required field (title): public view
|
|
Tested a new work on staging, and only added metadata to three fields. No blank fields are showing. https://adl.s2.adventistdigitallibrary.org/concern/generic_works/600641e8-8cc7-453c-a12d-c0ad34a027cf Tested a new collection as well, and it also works as expected. Two fields have metadata, and two fields show. https://adl.s2.adventistdigitallibrary.org/collections/ed64bf09-7142-4251-9abe-698cc6568a10?locale=en |
Summary
I imported 3 books from OAI set adl:book, and when I opened the edit page on one and resaved it, the work page now shows a bunch of blank metadata fields that I didn't modify. These fields were and remain blank. Yet after edit/save, they now display on the public facing work page.
https://adl.s2.adventistdigitallibrary.org/concern/published_works/20121738_the_vatican_and_the_war_a_retrospect_and_forecast_being_a_review?locale=en
The fields are:
The author field displays on work pages even when it is blank in the metadata. See and compare example work: On Staging https://adl.s2.adventistdigitallibrary.org/concern/published_works/20000076_mizpah?locale=en and On Production https://adl.b2.adventistdigitallibrary.org/concern/published_works/20000076_mizpah (note this was an existing work, not a new work)
Acceptance Criteria
Testing Instructions
Testing note: the staging site was partially reindexed resulting in most existing records being updated but not all. Our assumption is that the cut over will handle the update of all works in production. Creating new works (or collections) should pass QA.
PLEASE NOTE, if you still see blank fields the work needs to be reindexed. Until we perform a full reindex on the entire system, you can trigger it manually. Edit and save the work or collection without making changes.
Notes
["0~"]
due to an older version of the order_already gem.["0~"]
will not register the author (creator) field as blank and therefore do not display or sort properly.["0~"]
in the creator field need to be updated. This can be done with the following script:The text was updated successfully, but these errors were encountered: