2020-10-15 Metadata Management Meeting notes

No PC meeting this week

• The Vision/Strategy Working Group had their 4th and final meeting. Results will be shared later this week.
• Bound-withs/in-analytics working group met with developers. Questions from developers is leading the group to meet with the RA SIG next week to get some questions answered.

• From Magda, via chat, "Data export will also add the checkbox column to the inventory search screen as described in UXPROD-2332 - Getting issue details... STATUS "

Charlotte said that since last week's meeting, Filip will write a UX design with the possibility of selecting the order of columns at an tenant level. UX-403 (story). This would be a FOLIO wide improvement. It may be available at an individual user level as well. 

Resource Type and Format Columns

Format type or Resource Type. Format type is more granular than resource type. Resource type is required, but format type is not in FOLIO.  Since 337 is not required, Jacquie suggested it won't be as useful, but others feel that since the 337 is more useful, libraries may apply them. We can have both columns, however, the more elements, the more info the user has to wad through. Resource Type  is not repeatable in the instance and is mandatory, it will be easier to develop that. 

Jessica via chat - "Are we going to have options for hiding or collapsing columns? Can we resize columns? - Answer: Charlotte will add these ideas into UX-403. 

Conclusion - Group will request Resource Type and Format Type.

Edition

Laura check Cornell's db - 15% of their records have an edition statement. Chalmers would like this edition statement showing. Charlotte observed that this could be more important for public libraries. Shanghai Libraries: 

Marmot Library Network: Lloyd - would like this to be an option. 

Jennifer Eustis (via chat) - "Would it be helpful for a/v materials? For things like Director's cut, theatrical edition. For music there are various editions of music scores"

The group advocated for having this column as well. 

Relations

Since very few and instance to instance relations is used not often, so group decided to eliminate this column. Rita advocated for keeping this column. She would like to think it over. Rita brought up relations concerning periodicals and the usefulness of this in this display. Types of relations? Preceding/succeeding titles, or analytics? Felix said he took this back to a group who decided that the information is important, but not needed in that initial display.

UXPROD-2703

Split publication date (numeric only) out from publisher column. This would allow a publisher date sort in the result list. Value of getting date mapped from the 008 as opposed to the 264$c was discussed. Laura suggested this may be a discussion that we need to have more fully at another meeting. Action: Naming this element? Where would we want it to appear? Suggestions: "Sort Date" , placed with the "Administrative data", or "Identifiers"  ??? Later discussion. Charlotte advocated for the administrative data.   

Add ideas here

https://docs.google.com/document/d/1u1tvfVxn6i3fTImrWWCYHlh7RT5cf3_G7YgDuxKob4M/edit

x

VZG

Stanford

Index Data