Narrative Description for Sprint 1 PreOrder Logical Data Model

General Information

• 2 Primary entities: Pre-Order and the associated Title (i.e., bibliographic resource) that is under consideration for ordering
• I drafted this based on
  • attributes listed by Stuart Miller (Team Darby) in the Sprint 1 Item 3 Library Staff Request (User Story 7103) fspec found at https://docs.google.com/a/kuali.org/document/d/1laWfZZ9j7UbjWLYeAiO0U6TdG1CntU-Yw-k8h-Tg1C4/edit?hl=en#
  • the Order entity and attributes identified by the OLE Data Modeling subgroup https://docs.google.com/a/kuali.org/document/d/1_hKPHChb6ceoEzdUDxFubBPymu6lEJJcSm-HkCyODr8/edit?hl=en#
    • I did not include the "Order Line" attributes because I'm not entirely clear on this concept…
• See also full Kuali OLE Conceptual Model created by the Data Model subgroup for a fuller sense of how bibliographic and authority entities relate to each other.
• I have not yet done any analysis as to how an OLE Pre-Order/Order might equate to a KFS Purchase Order.
• I have not yet indicated field lengths or types.
• The draft LDM was drawn using "Gliffy" on the Kuali OLE wiki – and can not create ddls.

Pre-Order Entity
(Question: Should this just be "Order" and the amount/type of data determines and/or status determines if it is a "pre-order" or an "order"?)
Attributes
Pre-Order ID

• Primary Key

Pre-Order Date ID

• Links to date type and date
• Date Types = created, ordered, mailed, claimed, received, renewed (to be addressed by workflow?)
  • Types taken from the DM subgroups "Order" entity description

Request Type ID

• Request Types (per Stuart) = Purchase, License – libraries can add more data values

Request Source Type ID

• Request Source Types (per Stuart) = Open URL, in-house – libraries should also be able to add more data values

Request Source URL

• An Open Source URL can be entered/stored here – per Stuart (and per Sprint 1, Item 2 Create Manual Request (User Story 2650) https://docs.google.com/a/kuali.org/document/d/1T9RDGtkPC_qNgV1cn4Z0t_xKRpIL0NdckkjoEvky0EE/edit?hl=en#)

Title ID

• Link to a Title (aka Bib document) in the Document Store? Could be in MARC XML, MODS, FRBR, Dublin Core, EAD?
• Link to Title Entity with some info and then link to the Document Store?

Supplier

• Agent (Vendor/Publisher) supplying the pre-ordered Title
• This area needs lots of work - the DM Subgroup wanted a recursive relationship for Agents – where one Agent is the parent of another and where the Agents can be typed, e.g., - Vendor, Publisher, Consortia, Libraries, Institutions , Individuals within a specific organization (ex: technical support contact). I have not fully fleshed out the Agent entity but have, for now, only included an ID and a name.
• Need to figure if we can re/use the Vendor database in KFS
• Question: Would we consider using the Authority.Name entity to capture Vendor information?

User ID

• Multiple "users" can be associated with the Pre-Order – Requestor, Selector (can be one and the same user with different roles) – workflow?

Note ID

• Both Stuart and DM Subgroup want to be able to associate multiple "processing" notes with the pre-order record

Unit Price

• Stuart noted price needs to be captured, DM subgroup calls this "unit price"

Price Source

• From Stuart – presumably just a note field to indicate from where the requestor/selector got the price information.

Number of Copies

• Indicate the number of copies requestor/selector wants to order

Scope of Order

• Per the DM subgroup this would indicate: one time vs. continuing, specific volumes

Title Entity
Note: Not entirely sure how to model this as the attributes could/would all be included within the XML document that describes the Title.
Attributes

• Title ID – Primary Key

• Title Type ID
  • I added this with a link to an authority list/pick list with the possible values of Creation-level, Edition-level, Collection-Level, Holdings, Item, Ad-hoc – which are all bibliographic types per the OLE Conceptual Model created by the DM subgroup
• Title
  • This equates to the MARC 245 field (and its indicators and subfields)
  • If this data is stored relationally, as well as in a tagged XML field – how would want to format it? Based on MARC guidelines? With indicators, subfield codes? Or, would we parse out the MARC 245 field relationally? See http://www.loc.gov/marc/bibliographic/bd245.html

• Date of Publication (Per Stuart)
  • I think the associated MARC 008 field positions 07-10 (Date 1) and 11-14 (Date 2) See http://www.loc.gov/marc/bibliographic/bd008.html

• Place of Publication
  • Place of Publication – usually stored in MARC 008 positions 15-17. See http://www.loc.gov/marc/bibliographic/bd008.html
  • Question: Could this be pulled from the Agent (Publisher) data? Or, are there multiple places of publication and the library staff would want to select/enter the appropriate one?
• Physical Description (Per Stuart)
  • There are multiple MARC 3XX fields that traditionally capture physical descriptive information – not sure how we capture this information at the Pre-order stage if we intend to store it relationally – presumably the appropriate XML tagging would be used in a stored XML descriptive document.

Publisher

• • Agent (Publisher) of the pre-ordered Title
  • Not sure if Place of Publication would be pulled from here or not.
  • See previously raised questions on the Agent entity.

• Authority.Name ID
  • There are many "names" that could be associated with a Title in a wide variety of roles, i.e., author, subject, and added entry (contributor and the contribution role) – those roles are designated as such by MARC via the (1XX), (6XX), (7XX) fields respectively.
  • Names can be Person, Corporate, Meeting, Uniform Title – and designated as such by the X00, X10, X11, and X30 MARC fields, respectively

• Authority.Places ID
  • Geographic authorities can either be subjects of a Title or can indicate the place of publication (per the Conceptual model)
• Authority.Concept/Object ID
  • These are (generally) the topical subjects of the Title
• Format ID
  • Traditionally, this information is conveyed via the MARC 008 fixed length field. Within 008 data elements are positionally defined by type of material. Descriptions of the elements defined for field 008 positions 18-34 are in seven separate sections corresponding to the following type of material configurations: Books (BK), Computer Files (CF), Maps (MP), Music (MU), Continuing Resources (CR), Visual Materials (VM), and Mixed Materials (MX). See http://www.loc.gov/marc/bibliographic/bd008.html for more information.
  • I think what Stuart wants is to be able to associate a Format Type with a Title during the Pre-Order process. He wants an authority/pick list with the MARC format types: Books (BK), Computer Files (CF), Maps (MP), Music (MU), Continuing Resources (CR), Visual Materials (VM), and Mixed Materials (MX). But, he also wants to be able to add locally defined formats to that authority/pick list as well.

Standard Number Type ID

• Per Stuart – need to know the type of standard number associated with the Title that is being pre-ordered
• Standard Number Type Values = ISBN, ISSN - libraries should be able to add more data values

Standard Number

Title Recursive Relationship

• A titles can be related to another Title, e.g., as a parent Series and well as in the FRBR types of relationships Collection, Creation, Edition, etc.