Transform "Schlagwortketten" (subject chains)

[dr0i]

No description provided.

[dr0i]

If the "Schlagwortketten" (beginning without permutations) are provided this data should appear in the "single hit" view of NWBib.
Example of a resource having 2 Schlagwortketten: http://193.30.112.134/F/?func=find-c&ccl_term=IDN%3DBT000003404 (BT000003404).

[fsteeg]

OK, so here are some details on the subject chains and how I'd imagine to transform them.

It seems the maximim number of subject chains is 10, since they use the 9xx fields. They start at 902 for the first chain and then use steps of five for each other chain, so the second chain would be 907, then 912, etc. See this example for a title with 9 chains:

http://lobid.org/resource?id=BT000006579&format=source

Now thats just the base chains. For each of these chains we can have any number of permutations (these reference the order of the subjects, so we need to preserve that). These are stored in the next field after the base chain (if I understood this correctly). So the permutations for the first chain are stored in 903, for the second in 908, then 913, etc. See this example:

http://lobid.org/resource?id=HT013577568&format=source

Often, the subjects are from the controlled GND vocabulary, but not always. See 'Geschichte 71 v. Chr.-70 v. Chr' in the example above.

So based on all of this, this is what I'd suggest for the transformation:

For each chain, we generate a literal containing all subject labels as comma separated values, plus all permuatations as comma-separated values in parens. So for HT013577568 (secons sample above), this would yield these 6 chains:

1. Rheinland, Römerzeit, Germanen, Münze, Geschichte 71 v. Chr.-70 v. Chr (23415, 34215, 43215)
2. Rheinland
3. Römerzeit, Münzfund, Geschichte 71 v. Chr.-70 v. Chr (2314, 3214)
4. Rheinlande im engeren Sinn, Römische Zeit, Germanische Völker, Metallgeld, Münzen
5. Rheinlande im engeren Sinn
6. Römische Zeit, Fundmünze, Münzschatz

On the triple level, we can use the same predicate for these, which will give us an array in JSON-LD:

<http://lobid.org/resource/HT013577568> <http://purl.org/lobid/lv#subjectChain> "Rheinland, Römerzeit, Germanen, Münze, Geschichte 71 v. Chr.-70 v. Chr (23415, 34215, 43215)".

<http://lobid.org/resource/HT013577568> <http://purl.org/lobid/lv#subjectChain> "Rheinlande im engeren Sinn, Römische Zeit, Germanische Völker, Metallgeld, Münzen".

[dr0i]

@acka47 please mint http://purl.org/lobid/lv#subjectChain

[acka47]

As subject headings with commas exist (examples here), we shouldn't use commas for seperating the components of a chain of subject terms. I suggest using a pipe ('|') instead.

[acka47]

Here's the pull reuquest for th lv:subjectChain property: hbz/lobid-vocabs#28. Please review.

[dr0i]

TODO: exchange separator , with | in transformation.

[fsteeg]

Display and search for subject chains deployed to staging:

http://test.lobid.org/nwbib/HT017732186
http://test.lobid.org/nwbib/search?subject=Forstmann

[acka47]

+1

[fsteeg]

Deployed to production, closing. See:

http://lobid.org/nwbib/HT017732186
http://lobid.org/nwbib/search?subject=Forstmann