Get info about deprecated and replaced Isils from Pica+ 035D $b

[TobiasNx]

          Okay. We can do this once. But what to do on future redirects? We suggest that you extract this from Pica+ 035D $b when importing our data.

Originally posted by @cKlee in https://github.com/hbz/lobid-resources/issues/1768#issuecomment-1557120618

[TobiasNx]

Added replaces and replacedBy properties:

http://test.lobid.org/organisations/DE-1373.json

"replaces": [
    {
      "isil": "DE-18-17",
      "id": "http://lobid.org/organisations/DE-18-17#!",
      "type": "Organisation"
    }
  ]

http://lobid.org/organisations/DE-464#!

"replacedBy": [
    {
      "isil": "DE-465",
      "id": "http://lobid.org/organisations/DE-465#!",
      "type": "Organisation"
    }
  ],

Added properties to the context: http://test.lobid.org/organisations/context.jsonld

[acka47]

Looks good but there are problems with the properties used: https://schema.org/replacedBy and https://schema.org/replaces don't exist, there is only a more complex ReplaceAction in schema.org. I took a short look at LOV but did not find a suitable property. Something around "predecessor" and "successor" could also work...

[TobiasNx]

What about: https://www.dublincore.org/resources/userguide/publishing_metadata/#dcterms:isReplacedBy https://www.dublincore.org/resources/userguide/publishing_metadata/#dcterms:replaces

or: https://d-nb.info/standards/elementset/gnd#successor https://d-nb.info/standards/elementset/gnd#predecessor

[acka47]

I like the gndo properties more as they explicitely mention corporate bodies in the description, e.g. gndo:predecessor:

A corporate body or a work being the predecessor of another corporate body or work

[TobiasNx]

there is also: https://d-nb.info/standards/elementset/gnd#precedingCorporateBody https://d-nb.info/standards/elementset/gnd#succeedingCorporateBody

[acka47]

there is also: https://d-nb.info/standards/elementset/gnd#precedingCorporateBody https://d-nb.info/standards/elementset/gnd#succeedingCorporateBody

Fine for me. e-resource packages do not have this kind of information, do they? If yes, the general property would be the safer choice.

[TobiasNx]

you are right. lets take the more general version.

[cKlee]

E-resource packages do have this data. So the more general should be the right choice.

[TobiasNx]

Added replaces and replacedBy properties:

http://test.lobid.org/organisations/DE-1373.json

"replaces": [
    {
      "isil": "DE-18-17",
      "id": "http://lobid.org/organisations/DE-18-17#!",
      "type": "Organisation"
    }
  ]

http://lobid.org/organisations/DE-464#!

"replacedBy": [
    {
      "isil": "DE-465",
      "id": "http://lobid.org/organisations/DE-465#!",
      "type": "Organisation"
    }
  ],

Added properties to the context: http://test.lobid.org/organisations/context.jsonld

Now the examples have successor and predecessor.

[TobiasNx]

Now the examples have successor and predecessor on prod too.

http://lobid.org/organisations/DE-464#!

"successor": [
    {
      "isil": "E-465",
      "id": ["http://lobid.org/organisations/E-465#!"](http://lobid.org/organisations/E-465#!),
      "type": "Organisation"
    }
  ]

http://lobid.org/organisations/DE-1373.json

"predecessor": [
    {
      "isil": "DE-18-17",
      "id": ["http://lobid.org/organisations/DE-18-17#!"](http://lobid.org/organisations/DE-18-17#!),
      "type": "Organisation"
    }
  ]

Now on prod.

Needs to be added to the GUI #497