2019-02-21 Metadata Management Meeting notes

Date

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


Discussion items

ItemWhoNotes
Product Council Update

Tech Council requesting technical writer for documentation, possibly also consultant for end-user documentation.

Last week: formation of Implementation Group; will talk about implementation process, features analysis, gap analysis.

No decision yet re: in-person meeting.

Subgroup Updates

Of general interest:  Call for Forum Facilitation volunteer, one position open.  Please contact Laura if interested.

Filip is back & Data Import is refining prototype for matches & actions. At end of sprint tomorrow. Cate Boerema is asking for what will be accomplished in Q1 vs what needs to be pushed back to Q2

Cancelled orders

What is the desired behavior in Inventory re: Instance/Holdings when an order is cancelled in Acquisitions?

Acquisition &  Inventory integration - slide deck: https://docs.google.com/presentation/d/16M_PVJ2rS4dglfASv1KADt9gn4kuucb1ZbqVSJhBH7k/edit#slide=id.g4cdf76c5ce_0_10

Dennis B. and Charlotte led discussion on Acquisitions & Inventory integration.
Greg (Developer) working on Order app has questions about how to handle cancelled and deleted orders and the effect on Inventory.  (Also see column K in Inventory Beta-Metadata Elements spreadsheet).   Charlotte and Dennis currently working on interaction between Orders module to Inventory (Orders/Inventory integration (MODORDERS-69) and Receiving app to Inventory.

Discussion of draft order, and what happens when for some reason the order is cancelled or deleted etc.?  What is the responsibility for then cleaning up Inventory objects?  What are the different cases where we might wish to keep the Instance and Holdings records or not? 

Preference is for default that items/holdings are kept but suppressed and marked as cancelled?  Then reused if needed?

Feedback will be discussed with Greg.

Please display cancelled objects in a different color!

Codex Vision DocumentLaura E Daniels

The Codex Vision - TC Review

MM has been asked for feedback. Felix has started a google doc:

https://docs.google.com/document/d/1CFTBADw2jej_nCN1GD-41ubNOjIApn_g7OuulWKMUFA/edit

Still time to provide feedback, MM feedback important. 

Question:  Is our model meeting our needs?  Do we need the intermediation of the CODEX?

Charlotte: At the moment we need to build the system for implementation, but in parallel we can work on thinking ahead about the CODEX. 

Different questions arise: 5 Colleges: For now we are using MARC, but we'll need the CODEX when we integrate non-MARC metadata.  Laura: Or will the Inventory schema itself solve that problem?   Jennifer: What is the difference between Inventory and CODEX?  Aaron: What about metadata from archival systems?

Laura has coied the CODEX vision document into a Google doc, please contact Laura if you have interest in verbal discussion, with Mike, one-on-one, in group, etc.

Alerts & notifications in Inventory

Laura E Daniels(if there's time)

Spread sheet to capture requirements: https://docs.google.com/spreadsheets/d/1CCHAxfBWM4y3ixOJxfE--8qmTDsOOLOCQNc7KEEOKxM/edit#gid=1479847776

Quick review

Pending.

present?

Name

Organization

      Alice Krim
xAnn-Marie Breaux

Ann KardosUMass Amherst
xCharlotte WhittIndex Data

Christie Thomas

Colin Van AlstineSmith (FC)

Damian Biagi

Dennis ChristmanDuke University

Dracine HodgesDuke University



Filip Jakobsen

Jacquie SamplesDuke University

Jason Kovari

Jennifer EustisUMass Amherst

Jessica JaneckiDuke University
xLaura Wright

Lisa FurubottenTexas A&M

Lisa McCollLehigh University

Lisa Sjögren

Lynn Whittenberger
xMary AlexanderUniv. of Alabama
xNatascha Owens

Niels Erik Nielsen

Patty Wanninger

Sarah SchmidtDuke University

Tiziana Possemato



Jenn Colt



Martina Schildt

VZG

xSara ColglazierMHC/5C

Nancy Lorimer

Stanford

xAaron TrehubAuburn

Wayne SchneiderIndex Data

Kristen WilsonIndex Data