2020-10-08 Metadata Management Meeting notes

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

PC Agenda and Minutes

• Entity Management WG has finished its effort and has received support from MM
• Privacy SIG is hoping for rejuvenation

• no other updates or announcements

• 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 "

• 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

Add ideas here

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

x

VZG

Stanford

Index Data