2022-03-17 Metadata Management Meeting notes

MM SIG Release Note & Other Highlights.

For the MODSOURCE-300 - Scripts for identifying and fixing invalid instanceIDs in SRS, what problem is this supposed to solve? This came up with some of the libraries who were migrated where some of the data wasn't entered into the source record properly in the metadata around the source record so that the instance and srs link up properly. Do you see this error also in quickMARC? Ann-Marie will double check Charlotte's question and revise the description in the documentation. More context would help on this page and how to run these scripts.

For 567, this is a Spike and not a feature. This is blocked because something unexpected was encountered in quickMARC. Things need to be finalized before this is ready to go.

For 719, for the 1st time a record comes in the 001 and 003 are used to create the 035. Here the problem was that the 001 which had the HRID was being used again on update to create the 035 with the 003 which it shouldn't do. The expected result on overlay is not to copy the 001. This is only for overlay (an update).

Felix Hemme Charlotte Whitt 

UXPROD-3080 - Edit. Analytical records; bound with - part 2: link multiple bibs to the same item OPEN

Present UX work for Create and edit of bound-with: UX work for Create and edit of bound-with

The back end work was done and then another team did the UI work. What we are missing is the ability to create and edit these bound-with records. We need to make sure that this solution in the slideshow fits institutions.

It would be great to show the bound-with on both the main and linked record.

Is "link to" the accurate phrase for this? This is in regards to the button. Link to sounds good and is different from Move to. There is also a Boolean for bound-with that uses this terminology. These are not only for bound-withs. You can also use this for analyzed serials. Link to is more of a description and can be used for different scenarios that rely on this action.

There's a property on the instance record called Bound-with which is a True/False. You can count using the API and use the UUIDs for further actions. Is this only the record using the item or for the parent record? This is done over the holdings record where the item has been associated to. There is a ticket for this. This is a requirement change if we think this is important to know what is the starting point or primary one. To unlink it, it might matter where you started.

Can we add a requirement to tell which is the parent record that the item is living on? Can I edit the item from any instance/holdings that I find the item related to?

You can edit the linked item from anywhere. In this sense, it doesn't matter where it started. In this regards, it doesn't matter where we started. We could use the label "Linked Title".

After linking, when you do a barcode search then all records will be returned. Is this correct? A barcode search only returns the main one. We aren't able identify the main one. Is there a requirement coming for barcodes? This can't be done with the multicolumn list. We can add this when we have the hierarchical display. Right now the titles appear at the bottom. Can you make the row a hotlink? Can we identify here the primary instance title in the UI? This has some interest. 

Do we know if we have the information in here for discovery systems? This will be implemented for VuFind.

This gives enough information to give discovery systems something to work with.

When a patron has borrowed the book and you have to recall it, you include the primary information on the notice which can be confusing for the user who has the specific title rather than the serials title. If the barcode could bring back all titles associated with that linked record would be really great and could be included in the notice for patrons. We display the title from instance record and add other titles in red. The system also knows the other instance titles and fetch any kind of information from those records. What is missing is how RA will handle this for the slips and notices? RA could consider our implementation. That work hasn't been picked up by RA. Charlotte will reach out to RA about this. This model has been implemented and RA can play with it now.

Linking will work with or without barcodes. It works using the UUIDs. To check out an item, you do need a barcode.

For the edit screen, is this a good path using the split screen? Yes this is great. This is consistent with the Move To which makes it easier to learn.

To undo a Linked To will work similarly. To unlink everything would be manually. Here you would want to need to know the primary record. We need further discussion on removing linked records. The concept of parent item is good because of the display limitations.

This is planned for Morning Glory.

Felix and Charlotte will move forward on the UI and think about how to unbound or unlink, and the parent instance.