Closed nichtich closed 3 years ago
I'd suggest to import them into the default instance. WebDewey shows these classes in the normal hierarchy, and it would be confusing to have concepts from the same concept scheme loaded from different places (I think this might not even be possible at the moment).
Ok. I imported a dozen classes but need more error checking because mc2skos still misses some cases and the resulting JSKOS requires post-processing.
It looks like add table numbers come in many variants so I propose iterative adding them:
These steps can also be done without actually importing the data. Get a list of add table numbers:
./bin/convert.js $INPUT | jq -r '.[].memberList[].uri|select(match(":.+:"))' | sort | uniq
Then compare to add table numbers converted from DDC dump.
Closing this issue as it does not require changes to coli-ana.
DDC add table numbers are special classes used for number-building only. Example:
T1--0901-0905:07 Museen, Sammlungen, Ausstellungen; Sammeln von Objekten
Add table numbers are not included in German DDC available via JSKOS Server. With https://github.com/scriptotek/mc2skos/pull/71, these classes can also be converted to JSKOS.
Question: import these classes into default JSKOS Server instance or make them available in a dedicated database? These classes are not meant to be used for indexing or browsing but only for number building and decomposition. Mapping them may still make sense for information retrieval. An additional type URI for add table numbers might help filtering.