Sirenia docker image testing - errors when adding/viewing additional Collection metadata fields
Descriptive summary
As part of the Collection Index test sequence using the Sirenia docker image, tests related to populating Additional Fields in the Collection form result in errors or unexpected behavior. Additionally, it appears that some of the Collection form fields do not seem to display in the Public View of Collection page: is there documentation about which fields should and should not display in the Public View of Collection page, or is this still work in progress?
Steps to reproduce the behavior in User Interface (UI)
- Ensure a Collection exists that you can edit
- Edit the Collection and populate new fields, including expanding the Additional Fields section
- Save the changes
- View the Collection page (Public View) and note that few if any of the entries display (Title and Description only)
- Go back to the Collection and edit it
- Add a year-only date in the Date Created field (e.g. 2023)
- Save the change
- See RSOLR error
In my example, I first added a Target Audience, Department, and Description. In a second edit, I added Contributors and a Date Created.
Actual behavior (include screenshots if available)
Sirenia docker image, Hyrax 5 rc2
Extra fields populated (including those in the Additional Fields section)
Fields populated, but not displaying
RSOLR error when adding a year as a date. This error also recurred later when trying to remove a work from the collection containing the Date Created value of 2023.
Acceptance Criteria/Expected Behavior
- [ ] Ensure that common date formats such as YYYY can be entered and saved.
- [ ] If there is a specific date format required, we should document this or provide guidance in the form
- [ ] Ensure that form fields offered in the Collection form are actually configured for display
Rationale (for feature request only)
Provide the rationale or user story that describes "why" this issue should be addressed. Especially if this is a new feature or significant change to the existing implementation.
If a user enters common metadata into the Collection form, the form should both save the entries and display them.
Related work
Link to related issues or prior related work here.