2018-04-19 Metadata Management Meeting Notes

Former user (Deleted)

Filip Jakobsen (must leave the meeting 12:30 pm EST)

Niels Erik Nielsen, Wayne Schneider

UX-design. How would it make sense to experience Packages in Inventory (multiple hierarchical structures). Presentation of misc. wireframes.

Write up user stories?

Technical design, and presentation of some possible data models

________________

Filip

Currently in the inventory layout we have a nested list:

Instance

Holdings

Items

Option 1 - Showing Hierarchy

Option 2 - Show associated packages

Option 3 -

Laura - Do we have use cases?

Filip - Charlotte mentioned bound-withs,

Charlotte - Package is the container. It can include packages from Knowledge bases

Ann-Marie - Would this include a combined analyzed scenerios. Would a series record be an example?

Charlotte - Not leaning towards this

Laura - It's hard to give input when we don't have idea of what we'd use it for.

Filip - This is 100% determined by how we are going to using it.

Duke - For bound-withs it would have to be flexible. Option 1.

________________________

Wayne and Charlotte (Slides)

• Inventory Metadata Elements
  • instance
  • holdings
  • items
  • package (new)
• We have to model how we a managing eresources in inventory.
• Definition: Package represents a container of either Instances and/or Holdings.
• Usecases: represents all sorts of groups, including commercial package from a vendor will be represented in the Codex as a Package object of a particular type.
• Model shown:
  
  
• Laura - would we ever have a package that does not contain instances?
  
  • Jacquie - if nothing is in it, then there is no need for a package.
  • Niels Erik Nielsen - Package needs to support a bound-with structure. That is the reason for the link between package and item/holding.
  • Ann-Marie - An order
  • Christie - This item on this instance is on this package
  • We will make giving feedback to Filip a priority. We need to know conceptually how we will use packages.

Wayne

A way to use package entity to represent bound-withs

Ann-Marie - Would a package go directly to an item?

Laura suggested continuing this next week.

Charlotte - Suggested starting a spreadsheet with different usecase examples and map to the models above. And mark which would work.

Draft Package Use Cases here (please change as needed and add use cases, especially any that seem problematic):

https://docs.google.com/spreadsheets/d/1BPBpjNeY4SXQVYP15lP44dYMareq9w9RptPi-ewkCXI/edit#gid=0

Ann-Marie Breaux (Deactivated), Christie Thomas

___________________________

Christie Thomas

• Terminology - Tags are brief labels. Notes vs. tags: If a sentence is needed, the note field being developed is a better place.
• Use cases
• Not good cases - Codes vs. tags: codes that drive specific functionality. Tags should not be applied to something that is driving a functionality.Tags are for human reading, querying.
• This will be a stand alone App. It will appear in a sidebar
• Phase1 - assign a tag to a "record" - Permissions = "View-only; assign new tag; create new tag" Jacquie - curious about language limitations. Christie will take back to the subgroup and share.
• Conventions - no spaces allowed, lowercase only, default display will be alphabetical order
• In central admin can filter by tag and record type.
• Next Steps

Charlotte Whitt, Niels Erik Nielsen

Charlotte Whitt, Kimie Ou Yang