Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "inventoryNumber" to holdings #2128

Open
TobiasNx opened this issue Jan 16, 2025 · 1 comment
Open

Add "inventoryNumber" to holdings #2128

TobiasNx opened this issue Jan 16, 2025 · 1 comment
Assignees

Comments

@TobiasNx
Copy link
Contributor

TobiasNx commented Jan 16, 2025

In ITM $B Alma provides the inventory number of an item. Currently this is not mapped to lobid. In context of hbz/lobid-extra-holdings#1 (comment) DE-Sol1 was requesting this.

schema.org does not have an inventory number, as far as I can see.
sdo:sku seems to have an matching definition:

The Stock Keeping Unit (SKU), i.e. a merchant-specific identifier for a product or service, or the product to which the offer refers.

But is often used in the schema.org library examples for the call number. See: https://www.w3.org/community/schemabibex/wiki/Holdings_via_Offer and
schemaorg/schemaorg#733 (comment)

Alternative http://terminology.lido-schema.org/lido00113 but not sure if this work?

Or we add our own property.

@acka47 what do you think?

We also should think about if we add the inventory date (ITM $D) and the inventory update date (ITM $Y).

<datafield tag="ITM" ind1=" " ind2=" ">
<subfield code="H">2214088280007830</subfield>
<subfield code="x">kA</subfield>
<subfield code="f">BOOK</subfield>
<subfield code="v">kA</subfield>
<subfield code="p">04</subfield>
<subfield code="X">System</subfield>
<subfield code="Y">2003-10-27 01:00:00 Europe/Berlin</subfield>
<subfield code="n">GA 2989</subfield>
<subfield code="M">49HBZ_BRIDGE_SAS</subfield>
<subfield code="s">1</subfield>
<subfield code="d">0</subfield>
<subfield code="V">System</subfield>
<subfield code="b">keinBarcode</subfield>
<subfield code="a">2314088260007830</subfield>
<subfield code="c">GA 2989</subfield>
<subfield code="B">1991.591</subfield>
<subfield code="D">20031027</subfield>
<subfield code="W">2024-12-12 07:13:58 Europe/Berlin</subfield>
<subfield code="u">Z9035</subfield>
<subfield code="w">Z9035</subfield>
</datafield>

maps currently to:

hasItem: [...
   {
      "label": "lobid Bestandsressource",
      "type": [
        "Item",
        "PhysicalObject"
      ],
      "callNumber": "GA 2989",
      "serialNumber": "keinBarcode",
      "currentLibrary": "Z9035",
      "currentLocation": "kA",
      "heldBy": {
        "isil": "DE-Sol1",
        "id": "http://lobid.org/organisations/DE-Sol1#!",
        "label": "Stadtarchiv Solingen, Bibliothek"
      },
      "inCollection": [
        {
          "id": "http://lobid.org/organisations/DE-Sol1#!",
          "label": "Stadtarchiv Solingen, Bibliothek"
        }
      ],
      "id": "http://lobid.org/items/990013049400206441:DE-Sol1:2314088260007830#!"
    },

It should also include:

"inventoryNumber": "1991.591",
"inventoryDate" : "2003-10-27",
"dateUpdated": "2003-10-27"

Not sure if this is correctly modeled.

@acka47
Copy link
Contributor

acka47 commented Jan 16, 2025

I plead for focusing on the requested information and after taking a look at Bibframe, RDA and LOV I am for creating our own property in lobid-vocabs.

@acka47 acka47 assigned TobiasNx and unassigned acka47 Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

2 participants