Representation of package entity in Inventory (Container record). Design and technical decisions
CSP Request Details
CSP Rejection Details
CSP Approved
Description
Environment
Potential Workaround
Attachments
clones
relates to
Checklist
hideTestRail: Results
Activity
Cate Boerema April 3, 2019 at 8:48 AM
Well, this story looks like it describes work a PO would do and it is assigned to you, Charlotte. I thought you had created for personal work tracking reasons or something. I'd like to keep the team backlog populated with user stories that are intended for developers and which are dev-ready. This means they should have scenarios (if they are user stories) or clear acceptance criteria (if they are spikes).
That's great the is analysis complete. I didn't actually realize this was part of that, as there are so many UXPROD features linked to this story. Each user story should only have one UXPROD feature linked to it.
Charlotte Whitt April 3, 2019 at 7:40 AMEdited
- I don't understand your comment about 'cluttering'?
The container record implementation - is Analysis Complete, and ready to go! When developer resources are available - .
CC: ,
Cate Boerema April 3, 2019 at 7:34 AM
is this meant to capture your work? Can we mark it draft then or something? Because I feel it is cluttering up the core functional backlog.
Wayne Schneider April 13, 2018 at 7:11 PM
Some possible data models:
Traditional monograph: https://docs.google.com/drawings/d/e/2PACX-1vSQri_d6TepUcmnHpfAu-tQB1jeSIQAcRnZeRKQ-NMj3OluVGCeshzO9YNSqztWumMWQqvrn_E-WMkM/pub?w=554&h=370
Bound-with records (no packages): https://docs.google.com/drawings/d/e/2PACX-1vREuH4rSkgvwXrfWQySAJP-hq0oR0yb3urWljgb-sXEg_4pYW7zT6za2FkfPr2Tsgi1-F9a9oXPtqzt/pub?w=557&h=376
Bound-with records (with packages): https://docs.google.com/drawings/d/e/2PACX-1vRUUalOXuUY8sHTJ__jffHH_XUaDJhZFvyO2UaKPveibcAQf66qjgEniSNsfXDckpre9F-lwotOb9Aq/pub?w=723&h=466
Hierarchical records: https://docs.google.com/drawings/d/e/2PACX-1vRe48gRP61LDrC98nlE3aEcTFiSSvR66zUDFbr_jHfrsltIAo9Gb09cCHfY-RYgu2bYW5tzeuZ9mTOI/pub?w=848&h=698
Niels Erik Nielsen April 13, 2018 at 5:13 PMEdited
Write up what changes we expect to the data structure from adding a 'Package' entity to support packages and potentially bound-with. , and analytic records.
Details
Details
Assignee
Charlotte WhittReporter
Charlotte WhittLabels
Priority
P3
Purpose: Gather important requirements, technical design, write specs, make architectural decisions on how to implement the package entity in Inventory.
Several SMEs talk about this - latest at the MM-SIG meeting on 4/5/2018 (https://folio-org.atlassian.net/wiki/display/MM/2018-04-05+Metadata+Management+Meeting+Notes) and on Discuss (https://discuss.folio.org/t/bib-records-required-in-inventory-to-create-orders/1737/12) - and they all give it high priority. It's a topic on the agenda for the WOLFcon developer meet
Package is part of the five entity described by Vince Bareau in the Codex Metadata Model: https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=5854462.
Link to: package.json: https://github.com/folio-org/raml/blob/master/schemas/codex-next/package.json
Link to: packageCollection.json: https://github.com/folio-org/raml/blob/master/schemas/codex-next/packageCollection.json
Document "Local Packages in Inventory (UIIN-155)": https://docs.google.com/document/d/1DakHW6D5_09uKJPQzCSTwycP0gqkPs6E7k35_KpfCxg/edit
Usecases discussed with MM-SIG and ERM subgroup: https://docs.google.com/document/d/1DakHW6D5_09uKJPQzCSTwycP0gqkPs6E7k35_KpfCxg/edit#heading=h.qoqu1vta1deq
Container Metadata Elements: https://docs.google.com/spreadsheets/d/1RCZyXUA5rK47wZqfFPbiRM0xnw8WnMCcmlttT7B3VlI/edit#gid=163842260
It's relevant to solve for V1.