| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | AC | AD | AE | AF | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | volume | Relation to Vince Bareau's The Codex Metadata Model | Details | Status | Input Type (for editable Codex mode) | Function | Repeatable | Required | Mapping from MARC | Mappring from Orders ux.folio.org/prototype/en/orders (Acquisition Small Group + Charlotte) | Comments/Questions - SMEs | Comments/Questions - Developers (Niels Erik Nielsen) | Comments from the Gap analysis | Discussion Notes Working group meeting #1 (10/23/2017) | Discussion Notes Working group meeting #2 (10/27/2017) | Discussion Notes Working group meeting #3 (11/3/2017) | Discussion Notes Working group meeting #4 (11/10/2017) | ||||||||||||||||
2 | https://wiki.folio.org/x/VZkV | https://wiki.folio.org/x/4ZgV | The most updated MARC mapping is following doc: https://docs.google.com/spreadsheets/d/11lGBiPoetHuC3u-onVVLN4Mj5KtVHqJaQe4RqCxgGzo/edit#gid=0 | https://docs.google.com/spreadsheets/d/1JnvLq-pQ861pNnW_AEn0xsSujr9yTuM8MOHSWJ_XSZA/edit#gid=274537874 | |||||||||||||||||||||||||||||
3 | FOLIO ID | instance-id | System-assigned, non-repeatable, read-only, maps to instance-id in Codex | ✓ | Read only | - Auto-generated by FOLIO - Read-only | NR | Y | N/A | N/A | |||||||||||||||||||||||
4 | Human readable ID | System-assigned, non-repeatable, read-only, maps to the FOLIO ID, instance-id | Read only | - Auto-generated by FOLIO - Read-only | NR | Y | |||||||||||||||||||||||||||
5 | Metadata Source | instance-source | ✓ | Read only | Auto-populated with source of the codex record and its format, if applicable (e.g. "Local: MARC" or "EPKB") | NR | Y | N/A | N/A (source may be the order app, if bib data is added via the order record) | See: https://discuss.folio.org/t/on-primary-identifiers-in-folio/1826 | |||||||||||||||||||||||
6 | Resource Title | instance-title | Text, non-repeatable, maps to instance-title in Codex | ✓ | Text | NR | Y | 245 $a - Title (NR) $b - Remainder of title (NR) $c - Statement of responsibility, etc. (NR) $f - Inclusive dates (NR) $g - Bulk dates (NR) $h - Medium (NR) $k - Form (R) $n - Number of part/section of a work (R) $p - Name of part/section of a work (R) $s - Version (NR) | Title | Differentiate between title statement and uniform title in UI display | |||||||||||||||||||||||
7 | Alternative Title | instance-altTitle | ✓ | Text | R | N | 246 $a - Title (NR) $b - Remainder of title (NR) $f - Inclusive dates (NR) $g - Bulk dates (NR) $h - Medium (NR) $i - Display text (NR) $n - Number of part/section of a work (R) $p - Name of part/section of a work (R) 247 $a - Title (NR) $b - Remainder of title (NR) $f - Inclusive dates (NR) $g - Miscellaneous information (R) $h - Medium (NR) $n - Number of part/section of a work (R) $p - Name of part/section of a work (R) 240 a - Uniform title (NR) $d - Date of treaty signing (R) $f - Date of a work (NR) $g - Miscellaneous information (R) $k - Form subheading (R) $l - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section of a work (R) $o - Arranged statement for music (NR) $p - Name of part/section of a work (R) $r - Key for music (NR) $s - Version (NR) 130 $a - Uniform title (NR) $d - Date of treaty signing (R) $f - Date of a work (NR) $g - Miscellaneous information (R) $h - Medium (NR) $k - Form subheading (R) $l - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section of a work (R) $o - Arranged statement for music (NR) $p - Name of part/section of a work (R) $r - Key for music (NR) $s - Version (NR) $t - title of a work (NR) | not available from order; not needed per acq small group | Our music cataloger suggests 240 be moved to "Preferred title" -- thoughts? (-Laura) Would we also want to do this with the 130 then? Is it possible to map the 130 to Preferred title for serials? (Chicago) | ||||||||||||||||||||||||
8 | Related Title | Not included in Codex | ✓ | Text | R | N | 760 - Main Series Entry $a - Main entry heading (NR) $t - Title (NR) 762 - Subseries Entry $a - Main entry heading (NR) $t - Title (NR) 765 - Original Language Entry $a - Main entry heading (NR) $t - Title (NR) 767 - Translation Entry $a - Main entry heading (NR) $t - Title (NR) 770 - Supplement/Special Issue Entry $a - Main entry heading (NR) $t - Title (NR) 772 - Supplement Parent Entry $a - Main entry heading (NR) $t - Title (NR) 773 - Host Item Entry $a - Main entry heading (NR) $t - Title (NR) 774 - Constituent Unit Entry $a - Main entry heading (NR) $t - Title (NR) 775 - Other Edition Entry $a - Main entry heading (NR) $t - Title (NR) 776 - Additional Physical Form Entry $a - Main entry heading (NR) $t - Title (NR) $i - Relationship information (NR) 777 - Issued With Entry $a - Main entry heading (NR) $t - Title (NR) 780 - Preceding Entry $a - Main entry heading (NR) $t - Title (NR) 785 - Succeeding Entry $a - Main entry heading (NR) $t - Title (NR) 786 - Data Source Entry $a - Main entry heading (NR) $t - Title (NR) 787 - Other Relationship Entry $a - Main entry heading (NR) $t - Title (NR) $i - Relationship information (NR) | not available from order record; maybe add post-v1 (maybe a concern down the road; eBook in a package, or continues/continued by serials) | thoughts about $i or other subfields? I included $i for 776 and 787; should it be included for all? also, the 76x-78x fields don't really account for multi-part monographs or other situations with analytics; does a 130/830 relationship possibly work for those hierarchical relationships? 5/24/18 - for 700/710 include the author (subfield acqd) and title (subfield t) in the string | ||||||||||||||||||||||||
9 | Edition | instance-version | ✓ | Text | NR | N | 250 $a - Edition statement (NR) $b - Remainder of edition statement (NR) | Need to add Edition to order record item details (optional field) | Add 254 $a -Musical Presentation Statement -Joseph. IMPORTANT: This need to be repeatably - comment at WOLFcon MM-SIG session (CW). | ||||||||||||||||||||||||
10 | Series Statement | instance-series | ✓ | Text | R | N | 490 $a - Series statement (R) $v - Volume/sequential designation (R) 830 $a - Uniform title (NR) $d - Date of treaty signing (R) $f - Date of work (NR) $g - Miscellaneous information (R) $h - Medium (NR) $k - form subheading (R) $l - Language of a work (NR) $m - Medium of performance for music (NR) $n - Number of part/section of a work (R) $o - Arranged statement for music (NR) $p - Name of part/section of a work (R) $r - Key for music (NR) $s - Version (NR) $t - Title of a work (NR) $v - Volume/sequential designation (NR) | not available from order record; maybe add post-v1 | 490 Is the transcribed version of the 830, if the series has an authority record. So, the subfield indicators for the 490 should be evaluated when choosing to map these very separate elements. They should not be conflated into a single metadata element in FOLIO since the 830 is the Uniform Title of the Series. Perhaps it would be OK to do so for the Codex, but not for the cataloging metadata. | ||||||||||||||||||||||||
11 | Resource Identifier | instance-identifier-value | ✓ | Text | A series of commercial, system, and local identifiers applied to a resource for the purposes of communicating with external systems and/or as access points across systerms | R | N | 001 Control Number 010 $a,z - LCCN (z:cancelled) 020 $a,z - ISBN (z: cancelled/invalid) 022 $a|,y,z - ISSN (l: linking, y: incorrect; z: cancelled) 024 $a,z - Other Standard Identifier (z:cancelled) 027 $a,z - Standard Technial Report Number (z: cancelled) 028 $a,b - Publisher Number (b: source) 030 $a,z - CODEN (z: cancelled) 035 $a,z - System Control Number (z: cancelled) 074 $a,z - GPO Item Number (z:cancelled) Locally-defined fields | Item Detail Product ID (Note: if identifier entered, inventory needs to know the type of ID) Likely need validation of ISBN and ISSN numbers Make the identifer field repeatable in the order record; always pair it with the identifier type. Maybe coordinate list of identifier types with Charlotte. | 5/24/18 Add label for invalid (z), etc. | |||||||||||||||||||||||
12 | Resource Identifier Type | instance-identifier-type | ✓ | Select | R | N | ISBN, ISSN, Other Standard Identifier, Standard Technical Report Number, Publisher Number, CODEN, GPO Item Number Control Number (001) LCCN System Control Number Locally-defined identifiers | Aim to coordinate the Identifier Type list with Charlotte (add vendor number to the standard list) | Values to include ISBN, ISSN, Standard Technical Report number, Publisher Number, CODEN, Control Number (001), GPO Item Number, LCCN, System Control Number, Other Standard Identifier, and locally-defined identifiers GBV: propose to add formally incorrect ISBN and formally incorrect ISSN GBV 2: Would this be the appropriate place for properties like DOI, URN and Handle? | ||||||||||||||||||||||||
13 | Creator | instance-creator | Text input component, but authority controlled - opportunity to link to external authority files? | N | 110 $a,b,c,d,e,f,g,k,l,n,p,t,u: corporate name 111$a,b,c,d,e,f,g,k,l,n,p,q,t,u: conference name 100 $a,b,c,d,e,f,g,k,l,n,p,q,t,u: personal name | N/A | Differentiate between personal name, corporate name, and meeting name. Ideally will link to appropriate name authority file for record creation. | CW (11/10/2017): Discussed this with Wayne Sneider, and Niels Erik Nielsen. There is a useful distinction between primary contributor and an added entry, but we can capture that with a contributor type, or a qualifier. Niels Erik has in the Elements schema for the Inventory app implemented the contributor field, with a qualifier - so this changes in elements is not a 'dramatic' change in the Instance schema. | Decision: Creator will be incorporated in the Contributor element. This means that Creator as is own element will not be implemented | ||||||||||||||||||||||||
14 | Contributor | instance-contributor | ✓ | Text input component, but authority controlled - opportunity to link to external authority files? | R | N | 700 $a - Personal name (NR) $b - Numeration (NR) $c - Titles another words associated witha name (R) $d - Dates associated with a name (NR) $e - Relator term (R) $f - Date of a work (NR) $g - Miscellaneous information (R) $h - Medium (NR) $k - Form subheading (R) $l - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section of a work (R) $o - Arranged statement for music (NR) $p - Name of part/section of a work (R) $q - Fuller form of name (NR) $r - Key for music (NR) $s - Version (NR) $t - Title of a work (NR) $u - Affiliation (NR) 710 $a - Corporate name or jurisdiction name as entry element (NR) $b - Subordinate unit (R) $c - Location of meeting (R) $d - Date of meeting or treaty signing (R) $e - Relator term (R) $f - Dateof a work (NR) $g - Mischellaneous information (R) $h - Medium (NR) $k - Form subheading (R) $l - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section/meeting (R) $o - Arranged statement for music (NR) $p - Name of part/section of a work (R) $r - Key for music (NR) $s - Version (NR) $t - Title of a work (NR) $u - Affiliation (NR) 711 $a - Meeting name or jurisdiction name as entry element (NR) $b - ? On KH's list, but not on MARC21 (LOC) $c - Location of meeting (R) $d - Date of meeting (NR) $e - Subordinate unit (R) $f - Date of a work (NR) $g - Miscellaneous information (R) $h - Medium (NR) $k - Form subheading (R) $l - Language of a work (NR) $n - Number of part/section/meeting (R) $p - Name of part/section of a work (R) $q - Name of meeting following jurisdiction name entry element (NR) $s - Version (NR) $t - Title of a work (NR) $u - Affiliation (NR) 720 $a - Name (NR) $d - ? On KH's list, but not on MARC21 (LOC) $e - Relator term (R) ? Not on KH's list, but in MARC21 (LOC) $f,g,h,k,l,m,n,o,p,r,s,t,x - ? On KH's list, but not on MARC21 (LOC) Relationship to work expressed in $e and/or $4 for 700 and 710, in $j for 711, and $e for 720. | Need to add author/editor to the order record item details (optional field) | Distinguish relationship based on $e, $j, and/or $4 Ideally will link to appropriate name authority file for record creation | ||||||||||||||||||||||||
15 | Subject Headings | Not included in Codex | ✓ | Text | R | N | Subject Added Entry: 600 Personal Name (R) 610 Corporate Name (R) 611 Meeting Name (R) 630 Uniform title (R) 647 Named Event (R) 648 Chronological Term (R) 650 Topical term (R) 651 Geographic name (R) 654 Faceted Topical Terms. Focus term (R) 662 Hierarchical Place Name (R) Index Term: 653 Uncontrolled term (R) 655 Genre/Form (R) 656 Occupation (R) 657 Function (R) 658 Curriculum Objective (R) Local Subject Access Fields (R): 690 691 695 696 697 698 699 | not available from order; not needed per acq small group | Ideally will link to appropriate subject authority file for record creation. | If we have all subject subfields in one instance field, we can do filtering. | |||||||||||||||||||||||
16 | Classification | Not included in Codex | ✓ | Text | R | N | 050 $a Library of Congress classification number 055 $a Canadian classification number 060 $a NLM Classification number 070 $a National Agricultural Library classification number 080 $a Universal Decimal Classification Number 082 $a Dewey Decimal Classification Number 083 $a Additional Dewey Decimal Classification Number 084 $a Other Classification Number 086 $a Government Document Classification Number, $z Canceled/invalid classification number, $2 Number source 090 $a Locally assigned LCtype call number 092 $a Locally assigned Dewey Call Number 096 $a Locally assigned NLM-type Call Number 099 $a Locally assigned other classification number | not available from order; not needed per acq small group | CW: Would 090-099 be reflected in 852 - se Call numbers in the Holdings tab LW: my institution currently stores most item-level call number info in the bibliographic record (occasionally in the item record and only very rarely in a holdings record); we currently use 099 extensively for government documents (e.g., UN Report numbers). I could see this being a migration issue (though not an insurmountable one) -- ideally of course we would not store holdings/item-level data in bibliographic records. | ||||||||||||||||||||||||
17 | Classification Identifier Type | Not included in Codex | ✓ | Text | N | LC, Canadian Classification, NLM, National Agricultural Library, UDC, Dewey, Additional Dewey, GDC | not available from order; not needed per acq small group | GBV: please add: RVK (Regensburger Verbundklassifikation), BK (Basisklassifikation); maybe add all classification codes listed here: https://www.loc.gov/standards/sourcelist/classification.html | |||||||||||||||||||||||||
18 | Publisher | instance-publisher | ✓ | Text | R | N | 260 $b - Name of publisher, distributor, etc. (R) 264 $b - Name of publisher, distributor, manufacturer (R) | Need to add Publisher to the order record item details (optional field) | Add "role", mapped from 264 2nd indicator https://www.oclc.org/bibformats/en/2xx/264.html 0 Production 1 Publication 2 Distribution 3 Manufacture 4 Copyright notice date | ||||||||||||||||||||||||
19 | Place of Publication | Not included in Codex | ✓ | Text | R | N | 260 $a - Place of publication, distribution, etc. (R) 264 $a - Place of production, publication, distribution, manufacture (R) | not available from order; not needed per acq small group | |||||||||||||||||||||||||
20 | Publication Date | instance-date | TEXT -- four digit year for MARC; initial had date-picker here, whih is fine for items with a more granular date applied, but MARC records will only have years | R | N | 008/07-14 is the best source of this data, especially for serials, although publication/distribution date is also recorded textually in the 260$c or 264$c.; For serials we will also need to map data from the 362 fields to show specific statement of coverage. May be a range for continuing publications. | Need to add Pub Date to the order record item details (optional field) | If the date information is a fact of the publication -- e.g., publication, manufacture, distribution, or copyright, with publication being the most operational of the group -- then it should go at the resource level. With regard to dates, there are three dates that have distinct meaning: Publication date: when the resource was published (for many materials, designated only by year), or the period of time during which the resource was published (for continuing publications) Subscription date/period: the time for which my subscription to a resource is valid, e.g., my subscription runs from January 1, 2017 until December 31, 2017 Coverage dates; The publication dates to which I have access -- e.g., January 2000 until December 2010. So together you could have an ejournal with a publication date of Janury 1990 to present, for which you have subscription access from January 1 2017 until December 31 2017 for content coverage from January 2000 until December 2010. Of these, only publication date is a fact of the resource itself. ====================== Need to normalize dates -- MARC records aren't likely to have a mm/dd, just year -- but other resources may have more complete date info. Storing a mm/dd format for MARC records that have only a year date is a corruption of data. Also, is a publication truly repeatable? | |||||||||||||||||||||||||
21 | URL | Not included in Codex | ✓ | Text | R | N | 856 $u - Uniform Resource Identifier (R) | not available from order; not needed per acq small group | Display 856|u when present UNLESS data from KB is provided. Notes re. the use of the URL, e.g. access restriction, authentication ?? Example: 856 $z Click here to view online version; access limited to Brown University users. $u http://RL3TP7ZF5X.search.serialssolutions.com/?V=1.0&L=RL3TP7ZF5X&S=JCs&C=INDIMAGOFH&T=marc Chicago: We would also want the $3 Materials Specified to display. And to use the indicators for differentiation: Resource or Related Resource. | ||||||||||||||||||||||||
22 | Resource Type | instance-type | ✓ | Select | Need to determine where this data comes from -- content, media, and carrier mappings? Those fields mapped in some way to a FOLIO-defined list? | NR - R | Y | 336$c = thesaurus 336$a or$b for term see https://www.loc.gov/standards/valuelist/rdacontent.html for mappings 008/18-34 Books 28 - Government publication 29 - Conference publication 30 - Festschrift 31 - Index 32 - Undefined 34 - Biography 008/18-34 Computer Files 26 - Type of computer file 27 - Undefined 28 - Government publication 29-34 - Undefined 008/18-34 Maps 008/18-34 Music 008/18-34 Continuing Resources 008/18-34 Visual Materials 008/18-34 Mixed Materials | Material type Questions: Per Charlotte, material type is used in item, resource type in inventory - make sure we use the proper term in order Possibly coordinate the standard list with Charlotte | Resource = RDA Content https://www.loc.gov/standards/valuelist/rdacontent.html per agreement at Wolfcon 2018 should be thesaurus - value pairs i.e. rdacontent - cartographic dataset allow for local expansion of resource types using a local thesaurus - local term pairs Field is required and should be a defined list of options; will continue to work with SIG to determine how this field should be mapped and any intersection with RA SIG. CW: FOLIO Glossary: Item type: An identifier assigned to each item in a library that, in circulation, is one component that can determine whether or not such an item can be borrowed and, if so, the conditions of the loan. Item types are generally defined by each library and can be either a specific format (e.g., “DVD”, “CD”, “Map”, etc.) or an indicator of borrowing eligibility (e.g., “Circulating”, “Non-Circulating). In practice, item type itself does not determine loan conditions but is used in combination with location and borrower type. Question: In the loan rules we use the term: Material type. Is this the term we use for Item type, and how is this distinct from Resource type. Would there be any problem with making this repeatable? (Laura) | The loan rules require 4 fields as input: * item type (like "book" or "dvd" or "umbrella") * loan type (like "rare", "special-items", "temporary-collection-k") * patron group (like "undergrad" or "cataloger") * shelving location See https://issues.folio.org/browse/CIRCSTORE-8 If we use resource type as item type it cannot be repeatable (or there must be a primary type used for the load rules). (Julian Ladisch) | CW: Post alpha-release! List of Resource Types (to be discussed with RA SIG. Need to be configurable): Audio cassette Book Cd-rom Compact Disc Computer Disc Electronic resource Dvd Dvd-rom Globe Kit Laserdisc Manuscript Map Microfiche Microfilm Microform Motion picture Notated music Nonprojected graphic Picture Projected graphic [e.g., slide] Realia Remoted-sensing image Sound recording Tactile material Text Unspecified Videorecording | |||||||||||||||||||||
23 | Format | instance-format | ✓ | Select | NR R | N | 338$c for thesaurus 338$a or $b for term see https://www.loc.gov/standards/valuelist/rdacarrier.html for mappings | not available from order; not needed per small group | Format = RDA Carrier https://www.loc.gov/standards/valuelist/rdacarrier.html per agreement at Wolfcon 2018 should be thesaurus - value pairs i.e. rdacarrier- audio cartrige allow for local expansion of resource types using a local thesaurus - local term pairs (-Laura) I'd like to see either this or Resource Type repeatable. 007 is repeatable, but I suspect we would only be using position 00, in which case would repeatability still make sense? Those values are a - Map c - Electronic resource [this does not distinguish between tangible/remote] d - Globe f - Tactile material g - Projected graphic [e.g., slide] h - Microform k - Nonprojected graphic m - Motion picture o - Kit q - Notated music r - Remoted-sensing image s - Sound recording t - Text v - Videorecording z - Unspecified | CW: Examples of Formats (to be discussed with RA SIG. Need to be configurable): Abstract Anthology Archive Article Artwork Audio Recording Blog Book Book Chapter Case Case Study Computer program Conference Database Dissertation Document E-Book Electronic Article Government Document Grant Image Interview Journal Legal Document Legislation Letter Manuscripts Map Music Newspaper Newspater Article Pamphlet Patent Poem Presentation Reference Entry Research Dataset Review Score Series Standards Statistical Data Set Technical Report Text Resource Thesis Transcript Video Website Working Paper | |||||||||||||||||||||||
24 | Physical Description | Not included in Codex | ✓ | Text | R | N | 300 $a - Extent (R) $b - Other physical details (NR) $c - Dimensions (R) $e - Accompanying material (NR) $f - type of unit (R) $g - Size of unit (R) | not available from order; not needed per small group | |||||||||||||||||||||||||
25 | Language | instance-language | ✓ | Select | https://www.loc.gov/marc/languages/introduction.pdf | R | N | 008/35-37 041 | not available from order record; maybe add post-v1 | ||||||||||||||||||||||||
26 | Not included in Instance Metadata Elements | instance-rights | Text | Access rights associated with the resource | NR | N | 506??? | User Limit? Maybe Note to Vendor | Copyright | ||||||||||||||||||||||||
27 | Notes | Not included in Codex | ✓ | Text | R | N | 500, 501, 502, 504, 505, 506, 507, 508, 510, 511, 513, 514, 515, 516, 518, 520, 521, 522, 524, 525, 526, 530, 533, 534, 535, 536, 538, 540, 541, 542, 544, 545, 546, 547, 550, 552, 555, 556, 561, 562, 563, 565, 567, 580, 581, 583, 584, 585, 586, 588, 59X (https://www.loc.gov/marc/bibliographic/bd5xx.html) | Item Detail - Description | Display 500,505, 583, 59X fields in Bib/Item UI, perhaps with indicator showing that other note fields exist? | ||||||||||||||||||||||||
28 | Date Added to FOLIO | instance-lastModified | ✓ | System | System-supplied date/timestamp | NR | Y | [Automatically assigned by Inventory] | Necessary for limiting based on date of entry. Chicago: We should have updated date as a separate element, along with created by and updated by elements to capture user ids. | ||||||||||||||||||||||||
29 | Ancillary data that impacts searching, limiting, etc. against the Codex | ||||||||||||||||||||||||||||||||
30 | Suppress in Discovery | Not included in Codex | Y/N flag | NR | N | Acq will likely know this more than Cat; consider having a flag in order, but can't map until then; might be used for mono series main recorders, package records - bib records needed to attach the order to, but are not the way you want to display the purchases to patrons | Denotes a bibliographic record that should not be displayed in the discovery interface. Option can be set at either instance or holdings/item level. | ||||||||||||||||||||||||||
31 | Staff Suppress | Not included in Codex | Y/N flag | NR | N | not available from order; not needed per small group | Denotes a bibliographic record that should not be displayed in staff interface UNLESS a "show all" option is selected. Option can be set at either instance of holdings/item level. If flag is set to yes, app-level business logic can be implemented to display all or only unsuppressed Codex entries. | ||||||||||||||||||||||||||
32 | Previously Held | Not included in Codex | Checkbox | Need to know whether an item was previously held by the library for things like Hathi access, etc. | NR | N | not available from order; not needed per small group | For print resources, primary use case is to support rights to Hathi Trust content. For e-resources, libraries want to track what was held when, how packages change over time, etc. This functionality is likely dependent on KB support, as not all KBs track these changes. Suggest treating this as a separate use case, as I need to know specifically what I previously held in this case. | |||||||||||||||||||||||||
33 | |||||||||||||||||||||||||||||||||
34 | |||||||||||||||||||||||||||||||||
35 | |||||||||||||||||||||||||||||||||
36 | Current Holdings | Current holdings = Yes if at least one associated item (physical or electronic) is in current holdings (Selected in EPKB, Current holdings for physical (local?) items) | N/A | N/A | [Automatically assigned by Inventory] | Inferred from attached holdings (so perhaps not stored explicitly as part of the Codex), but necessary for limiting/faceting and results display. Ideally could scope to library or consortium view based on user requirements. | |||||||||||||||||||||||||||
37 | |||||||||||||||||||||||||||||||||
38 | Below the pink line is beta | ||||||||||||||||||||||||||||||||
39 | Notes | Administrative notes. | Text | A place for staff to capture notes. | Y | N | not available from order; not needed per small group | Chicago: Administrative notes, not bibliographic notes. Should be able to export notes to local MARC fields with source MARC bib record. We should also be able to map data or set default values for these fields when importing a source bibliographic record | |||||||||||||||||||||||||
40 | Labels (as a separate element is replaced by the Tags app) | Administrative or functional tags. | Text / Select | A place for staff to assign labels to a record. | Y | N | These would be tags assigned to the inventory record, NOT tags assigned to the order record. | Chicago: Locally, we use administrative labels as fixed codes that can added at the bib / holdings / item level for reporting, filtering, and other functional processes. Examples of labels that we use include: ISER / ASER (inactive / active serial), YBPebook (to indicate a record for an individually purchased monograph), audstream / vidstream (for ease of filtering streaming audio and video materials). We have named fields for some of these elements locally, but I think a generic Labels element that can be populated at the bib, holdings, or item level would be more flexible. Should be able to export notes to local MARC fields with source MARC bib record or holdings / item data. We should also be able to map data or set default values for these fields when importing a source bibliographic record (Would the Package Codex object be a better way of collecting some of these materials together functionally? Can instances belong to more than one package? GBV: We use labels at the bibliographic level for national licences and digital collections. One instance can be associated with multiple labels. Having a field to store these values is a must-have. An example for a label would be ZDB-1-BEP for "Berkeley Electronic Press Academic Journals". | |||||||||||||||||||||||||
41 | Status | Administrative categorization | Select | Assignment of bib status to indicate where a record is in the workflow or the type of record. | N | Y | [in process with the item status group] | Chicago: Locally, we use this to track where a record is in the cataloging workflow, e.g., UnCataloged, Cataloging Complete, Short Cataloged (complete cataloging not required), etc. It is possible that the Labels element could also be used for this purpose? Should be able to export notes to local MARC fields with source MARC bib record or holdings / item data. We should also be able to map data or set default values for these fields when importing a source bibliographic record | |||||||||||||||||||||||||
42 | Publication Frequency | Text | Current and former publication frequency for serials | Y | N | 310 $a,b; 321 $a,b | not available from order; not needed per small group | Chicago: useful for holdings work and processing periodicals/serials | |||||||||||||||||||||||||
43 | Publication Range [must have] | Text | Range of sequential designation/chronology of publication, or date range. Tells me the range of issues published under the title in the title field. | Y | Y if known | 362 $a Date of publication and / or sequential designation $z Source of information | order only has pub date; anything more complex will need to come from cataloging record | Texas A&M: This is important, since the holdings work is done while looking at the instance record. I need to see the range of published items to tell if my holdings are correct and to insure I do not add item records for pieces that do not belong in the run. For example: Title 1: v.1-27 and Title 2: v. 28-123. Tells staff that only items for v. 1-27 should be on the holdings record for title 1; that it's wrong to add any items after v. 27. This field also gives staff a hint as to what the numbering pattern and designation captions should be. Real example: 362 1# Began with: Vol. 82, no. 1 (July 1960); ceased with: Vol. 148, no. 12 (Dec. 2012). Could live wihtout the $z, have to have $a. | |||||||||||||||||||||||||
44 | Ownership and Custodial History | Text | Field that contains information concerning the ownership and custodial history of the described materials. | Y | N | 561 $a,3,5,6,8 | not available from order; not needed per small group [is this provenance-related info?] | GBV: Because the information in this field is item specific, it would be better placed on the item level. But according to the MARC specification, this element belongs to the bibliographic level. | |||||||||||||||||||||||||
45 | Created by (user) | ✓ | UUID implemented. Display user name in readable form would be a new feature in the Record metadata component | NR | System supplied | ||||||||||||||||||||||||||||
46 | Date Updated | ✓ | Record metadata component | Y | System supplied | ||||||||||||||||||||||||||||
47 | Updated by (user) | ✓ | UUID implemented. Display user name in readable form would be a new feature in the Record metadata component | Y | System supplied | ||||||||||||||||||||||||||||
48 | Mode of Issuance | Select sample data: Monograph; Sequential Monograph; Serial; Integrating Resource; Other | Lynn W.: indicates if discrete (complete in 1 or more) or continuing and if static or updating | Leader 07 - Bibliographic level a - Monographic component part b - Serial component part c - Collection d - Subunit i - Integrating resource m - Monograph/Item s - Serial 008/21 | 006/04: Type of continuing resource # - None of the following d - Updating database l - Updating loose-leaf m - Monographic series n - Newspaper p - Periodical w - Updating Web site | - No attempt to code | This new element was discussed in the working group on Resource Type, Format, and Material Type. At WOLFCon it was decided to be added to Instance records. Following values to be implemented for sample data: Monograph; Sequential Monograph; Serial; Integrating Resource; Other Lynn W.: "Static works (aka monographs?) Diachronic works Integrating monographic work (ex: conference website) Sequential monographic work (aka monographic series?) Integrating continuing work (ex: news website) Serial work (sequential continuing work) | ||||||||||||||||||||||||||||
49 | |||||||||||||||||||||||||||||||||
50 | |||||||||||||||||||||||||||||||||
51 | |||||||||||||||||||||||||||||||||
52 | |||||||||||||||||||||||||||||||||
53 | |||||||||||||||||||||||||||||||||
54 | |||||||||||||||||||||||||||||||||
55 | |||||||||||||||||||||||||||||||||
56 | |||||||||||||||||||||||||||||||||
57 | |||||||||||||||||||||||||||||||||
58 | |||||||||||||||||||||||||||||||||
59 | |||||||||||||||||||||||||||||||||
60 | |||||||||||||||||||||||||||||||||
61 | |||||||||||||||||||||||||||||||||
62 | |||||||||||||||||||||||||||||||||
63 | |||||||||||||||||||||||||||||||||
64 | |||||||||||||||||||||||||||||||||
65 | |||||||||||||||||||||||||||||||||
66 | |||||||||||||||||||||||||||||||||
67 | |||||||||||||||||||||||||||||||||
68 | |||||||||||||||||||||||||||||||||
69 | |||||||||||||||||||||||||||||||||
70 | |||||||||||||||||||||||||||||||||
71 | |||||||||||||||||||||||||||||||||
72 | |||||||||||||||||||||||||||||||||
73 | |||||||||||||||||||||||||||||||||
74 | |||||||||||||||||||||||||||||||||
75 | |||||||||||||||||||||||||||||||||
76 | |||||||||||||||||||||||||||||||||
77 | |||||||||||||||||||||||||||||||||
78 | |||||||||||||||||||||||||||||||||
79 | |||||||||||||||||||||||||||||||||
80 | |||||||||||||||||||||||||||||||||
81 | |||||||||||||||||||||||||||||||||
82 | |||||||||||||||||||||||||||||||||
83 | |||||||||||||||||||||||||||||||||
84 | |||||||||||||||||||||||||||||||||
85 | |||||||||||||||||||||||||||||||||
86 | |||||||||||||||||||||||||||||||||
87 | |||||||||||||||||||||||||||||||||
88 | |||||||||||||||||||||||||||||||||
89 | |||||||||||||||||||||||||||||||||
90 | |||||||||||||||||||||||||||||||||
91 | |||||||||||||||||||||||||||||||||
92 | |||||||||||||||||||||||||||||||||
93 | |||||||||||||||||||||||||||||||||
94 | |||||||||||||||||||||||||||||||||
95 | |||||||||||||||||||||||||||||||||
96 | |||||||||||||||||||||||||||||||||
97 | |||||||||||||||||||||||||||||||||
98 | |||||||||||||||||||||||||||||||||
99 | |||||||||||||||||||||||||||||||||
100 |