Add predecessors and successors (formerly: Include MAB fields 530 to 533 in RDF)

acka47 commented 9 years ago

As asked for by NWBib customers, see https://wiki1.hbz-nrw.de/x/FoDgAw -> Funktionsvergleich "Einzeltrefferanzeige", 2.1. From the MAB documentation:

530       TITEL VON BEZUGSWERKEN

          Indikator:
          blank = verbale Beschreibung
          x     = reziproke Beziehung
          y     = nicht reziproke Beziehung
          z     = nicht differenzierte Beziehung

531       HINWEISE AUF FRUEHERE AUSGABEN UND BAENDE

          Indikator:
          blank = verbale Beschreibung
          x     = reziproke Beziehung
          y     = nicht reziproke Beziehung
          z     = nicht differenzierte Beziehung

532       HINWEISE AUF FRUEHERE UND SPAETERE SOWIE ZEITWEISE
          GUELTIGE TITEL

          Indikator:
          blank = verbale Beschreibung
          x     = reziproke Beziehung
          y     = nicht reziproke Beziehung
          z     = nicht differenzierte Beziehung

533       HINWEISE AUF SPAETERE AUSGABEN UND BAENDE

          Indikator:
          blank = verbale Beschreibung
          x     = reziproke Beziehung
          y     = nicht reziproke Beziehung
          z     = nicht differenzierte Beziehung

Links have to be included into NWBib after implementation.

dr0i commented 7 years ago

Ok, but what properties shall we use?

dr0i commented 7 years ago

Also there is possible the same problem mentioned in https://github.com/hbz/lobid-resources/issues/200#issuecomment-277987790.

acka47 commented 7 years ago

NWBib customer didn't ask for it again. Removing the API 2.0 tag as we can also do this later.

ChristophEwertowski commented 7 years ago

Looked for properties which could be used to express the contents of the MAB fields: 530 (Titel von Bezugswerken): Don't know if we should implement this. The relationship to related resources could be expressed but the title shouldn't be added to the relation. http://id.loc.gov/ontologies/bibframe/relatedTo could work. 531 (Hinweise auf frühere Ausgaben und Bände): http://id.loc.gov/ontologies/bibframe/precededBy (owl:ObjectProperty) or http://id.loc.gov/ontologies/bibframe/replacementOf (owl:ObjectProperty) 532 (Hinweise auf frühere und spätere sowie zeitweise gültige Titel): The nearest thing would be something like http://id.loc.gov/ontologies/bibframe/variantType (literal) 533 (Hinweise auf spätere Ausgaben und Bände): http://id.loc.gov/ontologies/bibframe/succeededBy (owl:ObjectProperty)

To do:

[x] Looking what's in the fields
[x] Drawing a json structure

ChristophEwertowski commented 7 years ago

http://lobid.org/hbz01/HT017317344 (530, 531) and http://lobid.org/hbz01/HT002191548 (532, 533) are examples for resources which have the wanted fields.

Snippet from HT017317344:

<datafield tag="530" ind1="z" ind2="1">
  <subfield code="p">Bis 2010,3(Febr.) Sonderausg. zu</subfield>
  <subfield code="a">TM Fashion-Trendmagazin</subfield>
  <subfield code="9">HT014630291</subfield>
</datafield>
<datafield tag="530" ind1="z" ind2="1">
  <subfield code="p">Ab 2010,4(März) Sonderausg. zu</subfield>
  <subfield code="a">TM</subfield>
  <subfield code="9">HT016412349</subfield>
</datafield>
<datafield tag="531" ind1="z" ind2="1">
  <subfield code="p">Vorg.</subfield>
  <subfield code="a">TM Düsseldorf fashion guide</subfield>
  <subfield code="9">HT014507359</subfield>
</datafield>

Snippet from HT002191548:

<datafield tag="532" ind1="z" ind2="1">
  <subfield code="p">16.1929 - 19.1932 ---></subfield>
  <subfield code="a">
Essen / Statistisches Amt: Vierteljahresberichte des Statistischen Amtes der Stadt Essen
  </subfield>
  <subfield code="9">HT006962851</subfield>
</datafield>
<datafield tag="532" ind1="z" ind2="1">
  <subfield code="p">1948 - 1950 ---></subfield>
  <subfield code="a">Essen: Statistische Monatsberichte</subfield>
  <subfield code="9">HT006961367</subfield>
</datafield>
<datafield tag="532" ind1="z" ind2="1">
  <subfield code="p">43.1990 - 44.1991 ---></subfield>
  <subfield code="a">Essen nennt Zahlen</subfield>
  <subfield code="9">HT003683389</subfield>
</datafield>
<datafield tag="533" ind1="z" ind2="1">
  <subfield code="p">Forts. ---></subfield>
  <subfield code="a">
Essen: Statistischer Halbjahresbericht der Stadt Essen
  </subfield>
  <subfield code="9">HT013374914</subfield>
</datafield>

All fields have three subfields:

p: what is referenced to (531, 533) (e.g. Vorg., Nachf.)? Erscheinungsweise (530, 532). Not standardisied
a: title
9: contains the HT numbers
```
relationship: [
{id: http://lobid.org/resources/[XYZ];
type: example.org/precededBy},   
{id: http://lobid.org/resources/[XYZ];
type: example.org/succeededBy},
{id: http://lobid.org/resources/[XYZ];
type: example.org/undefinedRelationship}
]
```
The fields 530 and 532 I would map to the last object. The titles of the MAB fields don't have to be included into the RDF/JSONLD. For the two examples only in one case the subfield a didn't match the title (the second 530 field in the first example) and instead a "Zusatz zum Sachtitel" was inserted.

ChristophEwertowski commented 7 years ago

About the title in the subfield a: If we want to show the titles as links and not a clickable search like "Enthält" "XYZ Beiträge" we have to include them. Under point one it's stated that the linking should work like in the old NWBib: What was that like? Another question for implementation is: Exists for every preceding resource at least one succeeding resource and vice versa or would we have links in one direction only? @acka47 : Need your feedback.

acka47 commented 7 years ago

Generally, the only fields that actually make the relation clear are 531 (predecessor) and 533 (successor). Thus I suggest to follow the ZDB (see e.g. curl -L -H "Accept: text/turtle" http://ld.zdb-services.de/resource/2673588-X) and use http://rdaregistry.info/Elements/u/P60261 for the former and http://rdaregistry.info/Elements/u/P60278 for the latter adding the ID (subfield 9) and label (subfield a) of the resource to an object. This would mean ignoring 530 and 532 for now. For the examples the result would look like this:

{
  "@context": {
    "predecessor": {
      "type": "@id",
      "@id": "http://rdaregistry.info/Elements/u/P60261"
    },
    "successor": {
      "type": "@id",
      "@id": "http://rdaregistry.info/Elements/u/P60278"
    }
  },
  "id": "http://lobid.org/hbz01/HT017317344",
  "predecessor": {
    "id": "http://lobid.org/resources/HT014507359",
    "label": "TM Düsseldorf fashion guide"
  }  
}

{
  "@context": {
    "predecessor": {
      "type": "@id",
      "@id": "http://rdaregistry.info/Elements/u/P60261"
    },
    "successor": {
      "type": "@id",
      "@id": "http://rdaregistry.info/Elements/u/P60278"
    }
  },
  "id": "http://lobid.org/hbz01/HT002191548",
  "successor": {
    "id": "http://lobid.org/resources/HT013374914",
    "label": "Essen: Statistischer Halbjahresbericht der Stadt Essen"
  }  
}

ChristophEwertowski commented 7 years ago

Added predecessor and successor. See example json. The brackets were also removed, see example (test) and example (production, MAB field 533). In the test set are many predecessors and successors which have an ind2, e.g. weren't catalogued with an original. Shall we take them into account nonetheless?

acka47 commented 7 years ago

+1

dr0i commented 7 years ago

Deployed to production, closing.

acka47 commented 7 years ago

Reopening, as predecessors without ID are missing, for example http://lobid.org/resources/HT001236436

ChristophEwertowski commented 6 years ago

Also missing for RDA entries, e.g. HT019498390. Look at MAB 785 and probably 780. Requested by edoweb customers so inform jschnasse after this ticket is done. Also update table at hbz Wolke.

Example for MAB 780 and 785: HT018138676 (MAB). ~~Example for missing predecessor from MAB 531z: HT003654516.~~ Example had ind2="2". Right example: HT006853428 (MAB). Labels of predecessors without a GND-Id aren't included at the moment.

hbz / lobid

Add predecessors and successors (formerly: Include MAB fields 530 to 533 in RDF) #137