/
2020-10-08 Metadata Management Meeting notes

2020-10-08 Metadata Management Meeting notes

Oct 08, 2020

Date

Oct 8, 2020

Attendees

please put an 'x' next to your name in the list below the "Discussion items" if you are attending. Thanks!

Recordings

Recordings of meetings can be found in the Metadata_Management_SIG > Recordings folder on Google Drive: https://drive.google.com/drive/folders/0B7G8S7WF6N20YUM4My1oRTIxSHM

Discussion items (notes are mixed in the columns)

Notetaker needed for today

 

@Jesse Lambertson

 

No meeting next week?

 

  • yes, next week's meeting is a go!

 

Product Council Update

 

PC Agenda and Minutes

  • Entity Management WG has finished its effort and has received support from MM

  • Privacy SIG is hoping for rejuvenation

 

Other updates/announcements

 

  • no other updates or announcements

 

 

Results display improvements – continued from last week

@Charlotte Whitt

@Laura E Daniels

WIP: Inventory. Refine result list (UXPROD-1634 and more) - https://docs.google.com/presentation/d/1kDumWwhNfP7Mq9hZ5q4O1cnbg_BY4ILgKbjBWOO4Xso/edit#slide=id.g9c99639b81_0_0

Spreadsheet to illustrate the enhanced Inventory Result list - see:https://docs.google.com/spreadsheets/d/1XLtdhnaHJz4Vb3G8FcHjso_LAUFdEzETo_50f8SYDrY/edit#gid=0

The listed examples in the spreadsheet is from Bugfest-Goldenrod - search:https://bugfest-goldenrod.folio.ebsco.com/inventory/view/50d09dd3-8586-4279-9883-24fbe6b6a407?qindex=title&query=vanity%20fair&sort=title

List of features:

UXPROD-1634 (index title/title)

UXPROD-2667 (sort on contributor, when more than one contributor is listed)

UXPROD-2668 (Adding instance HRID)

UXPROD-2669 (Adding resource type)

  • summary of the past:

    • displaying the title including initial articles sorting on index title

    • limiting contributors to 3 at most (for those titles that include a lot of contributors)

    • there were lots of good examples to support the adding instance HRID)

  • based on 336 field (required in instances)

    • related to content - not media or carrier

    • does not distinguish print from electronic

    • CW says it is not hard for the developers to add that column

    • how to deal with the mapping?

    • Christie suggests testing 

    • Folio takes the first 336?

    • Do other 336s display?

    • Ann K in chat ("I think it’s just the first one, but it needs to be tested
      Sometimes they are out of order
      It is supposed to be the “primary” one first, but that’s not always the case
      Particularly in older records")

    • CW out of scope for the result list right now

    • Affects filtering

    • LW suggests commenting on the slides above

UXPROD-2670 (Adding format)

  • not required

  • useful - but would be useful

  • LW concern is: 

    • might be blank

    • will take up real estate

    • the GMDs were formerly useful - but that is old standard

    • CT: format type is highly ranked for UChicago

    • harmonizing e and print inventory (CW) / new data element to be stored in the records

    • mode issuance also relevant

    • long term effort

    • should not add columns if they are not really needed

    • ref to Philip's solution using icons (deprecated according to CW)

      • UX390 or 391?

      • about granular data if it is NOT necessary to have that granularity

      • Format type OR resource Type (is one preferred)

      • Action item for this week: think about that above question: Format type OR resource Type (is one preferred)

      • what should be used as a separator (space ; space as it is in 'contributor') +1 from LW

UXPROD-2671(Adding edition)

UXPROD-2703(Adding publication date)

 

 

 

 

Display of empty & unmapped fields (continued)

@Charlotte Whitt

@Laura E Daniels

@Khalilah Gambrell

https://folio-org.atlassian.net/browse/UXPROD-2652

  • In the inventory app, many elements should be flexible

    • there needs to be local flexibility for local modeling

    • typical view: many empty data elements (no data has a dash '-')

    • Might the edit view and the detail view be aligned to have a more condensed view of data with content?

    • Maybe suppressing publication frequency and range?

    • want to display only data with real content

    • CW wonders if this change if this is a folio-wide change and not an app specific only change.

    • Nobody disagrees with the suggestion (comment that it would be less cluttered)

    • example of no underlying MARC (which makes one think there is not a full record - but it is full)

    • if empty elements get suppressed from display, so the order or display may switch around

    • Suggestion that there would be switching position unless empty space fills the suppressed elements

    • from chat ("It depends...if empty fields are not visible to the user, it could be forgotten that field exists especially by someone who doesn't know this data as well. It is something I come across in other applications. Empty fields are only visible in the edit screen and it is not apparent whether it is deliberately empty field or accidental") JG.

    • Khalilah is aware of this issue and suggests some mockups of these suggestions be made

    • Mouse-over functionality to see what is there - to make the most of real estate? (CW)

    • Maybe a summary page?

    • From Felix in chat ("Maybe we could even display/suppress fields by resource type. When you are looking at a monograph, no journal elements will display etc.? Does that make sense?")

    • how to deal with data that has to do with each other in a collapse vs show context (looking for a way to deal with all the empty or '-'s)

    • Martina S from chat ("I think in orders the not needed fields are grayed out")

    • a toggle? all or reduced

    • we don't want to forget data 

    • Mockup with a toggle?

    • Khalilah thinking about what a mockup would need and what specifically is being requested (such as another pane)

    • Asking if this is something that would be a folio-wide pattern (who to talk to, etc)

    • relative to mode of issuance, what elements should be displayed for he mockup

    • Martina S form chat ("I would like to pick this up with App Interaction - and I always vote for patterns across Folio:)")

    • Jackie G says in chat ("It is a type of model that the software Jira uses")

    • we need space for reasonable updates and data viewing (not too rigid)

    • LW asks for a mockup or 'drawing' to show what needs to display or not to display

    • Khalilah will take contact with Kimie Kester re. help out with some UX work to illustrate the discussed options

 

 

Future MM meetings (ongoing)

 

Add ideas here

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

 

 

present?

Name

Organization

present?

Name

Organization

 

Aaron Trehub

Auburn

 

Ann-Marie Breaux

EBSCO

 

Ann Kardos

UMass Amherst

x

@Charlotte Whitt

Index Data

 

Christie Thomas

Chicago

    x

Christin Seegert

hbz

 

Colin Van Alstine

Smith (FC)

 

Damian Biagi

 

 

Dennis Bridges

Stacks

 

Dennis Christman

Duke University

     

Douglas Chorpita

Goethe Uni Frankfurt

 

Dracine Hodges

Duke University

 

Felix Hemme

ZBW

 

Filip Jakobsen

 

 

Jacquie Samples

Duke University

 

Jason Kovari

Cornell

 

Jenn Colt

Cornell

 

Jennifer Eustis

UMass Amherst

 

Jessica Janecki

Duke University

 

Kristen Wilson

Index Data

x

Laura Wright

Cornell

 

Lisa Furubotten

Texas A&M

 

Lisa McColl

Lehigh University

 

Lisa Sjögren

Chalmers

 

Lynn Whittenberger

 

 

Magda Zacharska

EBSCO

 

Martina Schildt

VZG

 

Nancy Lorimer

Stanford

 

Natascha Owens

Chicago

 

Niels Erik Nielsen

 

 

Patty Wanninger

EBSCO

 

Rita Albrecht

HeBIS-Verbundzentrale

 

Sara Colglazier

MHC/5C

 

Tiziana Possemato

 

 

Theodor Tolstoy

EBSCO

 

Wayne Schneider

Index Data