Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 12
Next »
Attendees (please add your name):
Magda Zacharska leeda.adkins@duke.edu Monica Arnold Donald Depoorter Amanda Ros Jennifer Eustis Lisa Smith Christine Tobias@Kimberly Wiljanen Scott Perry Kimie Kester
Note Taker:
Robert Scheier
Meeting Recording:
Discussion:
| Topic | Details |
|---|
| Housekeeping | - Attendees - please add your name to the list of attendees
- Meeting host - please turn on Transcript option for the meeting
- No meeting December 27th
- Should we have a convener?
- Any other topics to cover?
|
Development updates | - Recordings of implemented Nolana functionality can be found here
|
| Morning Glory HF1 |
| key |
summary |
due |
priority |
status |
|
| Current list of Nolana bugs |
| key |
summary |
due |
priority |
status |
|
Nolana UAT updates and feedback | UAT Scenarios We got more responses this time. Did this form (Excel file with scenarios) worked better than the survey used in prior releases? Review of suggested feedback: | Area | Comment | Notes |
|---|
| General | It would be nice if you remember another edit you need to make you could use the same set of records to do another bulk edit under action rather than needing to go back to New bulk edit. |
| | General | Is the extra error "no change in value needed" necessary? If something is an error I would expect it not to be changed so it makes the errors look twice as long. |
| | Users- download matching records | two records did not fetch create or update data Brooks Richard Hernandez Edna But at least for Richard Brooks, it looks like that is an error in the underlying user record. Not sure how these accounts were created. | I was not able to recreate the issue but I run the tests after MODEXPW-319 and MODEXPW-320 were resolved | | User records - expiration date | The cursor goes in the year box which makes it seem like you should be able to edit the date by typing |
| | Items - status | It would be helpful to know which statuses can be changed. |
| | Holdings - uploading files | I selected the wrong identifier from the drop down. The error message wasn't that clear. There was still a preview of the holdings records and then errors for each one. It would be nice at some future date to have the error read that the identifier weren't uuids. |
| | Holdings - Are you sure? form | I added a 3rd action, then deleted it. When I clicked 'Confirm changes' I got a 'Something went wrong' error. I had to start over. Without the added action added and deleted, the step was passed. | UIBULKED-170 |
|
| Uploading progress bar | When uploading large file the progress bar stays in the same place for a while:  
|
| Bulk Edit Use cases | Reviewed use cases and associated existing JIRA tickets or marked which ticket still needs a JIRA to be created. Follow up questions on: | Number | Use case | Notes |
|---|
| 29 | Add a similar feature to Sierra Global Update that allows you to see the data from the fields of the same type (author, subject, title, etc.) present in a set (review file) of records. Use case – Identify bib records from the daily headings reports that have not been sent for authorities processing. Example: Backstage inserts a code indicating that a bib record has been processed in the 040 field. I can view all the 040 fields from a set of records using the “toggle” function in Global Update and select records for future authorities processing. Use case – Find patterns of problems in a set of records. Example: During record loading, some MARC fields may end up being duplicated. Sierra Create List searching cannot find duplicate fields, but the “toggle” function in Global Update helps identify affected records. |
| | 30 | Ability to temporarily add or remove a MARC field in SRS. Use case – To temporarily exclude some bib records from authorities processing, we add a 9XX note and re-write the monthly search query to exclude records using that note. Example: The recent EEBO record load was huge, so we had to temporarily exclude them from the month’s authorities processing query. |
| | 36 | When the 3-part Item State is available/developed, there will be the need to identify item records based on a 1-part item state, location, etc. in order to update them with one or more of the 3-part states. This could be done based on a list of item records (HRIDs or Barcodes), or by location alone, depending on how the 1-part item state is used with location, or other data, at individual institutions. |
| | 49 | Ability to identify records with certain characteristics (a particular 650, for example) and permanently add a MARC field in SRS and Instance to those records. Use case: In-house record enhancements (adding new controlled vocabularies such as LCGFT or LCMPT) |
| | 57 | We want to be able to find and delete duplicate fields. We want to be able to specify the field or fields where we want to remove duplicate data. |
|
|
| Bulk Edit Working Group's Meetings Feedback | https://forms.gle/iwRM1zq7id34Jgzt8 |