-
Notifications
You must be signed in to change notification settings - Fork 25
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
Skosify Hochschulkompass classification #1
Comments
As the fields in 3.) are grouped into subject groups in 1.) I propose to use those for the SKOS file and create concepts out of 3.) which are put into |
There are:
So, I think we should go with the approach I already proposed:
|
@acka47 what about 2.? |
We might as well create collections out of these. I hesitated to add more complexity but if we have collections in the first place it probably does not matter to add some more. |
Ok. But does the |
O. My thinking was strange. We probably are just dealing with a three-level hierarchy (although the UI of the Hochschulkompass does not make it that clear), with Fächergruppen a top-level concepts, then Studienbereiche on second level and Studienfelder at the bottom. So we should represent this in SKOS accordingly. Here is an example:
|
BTW, taking a deeper look at the page, I also found a description of the classification at https://www.hochschulkompass.de/studienbereiche-kennenlernen.html:
|
Going forward with the vocab, we might add some documentation properties ( |
We agreed to adjust the namespace (not use "Hochschulkompass") and to configure the redirect with w3id. Will do that this week. |
See https://www.hochschulkompass.de/studium/studiengangsuche/erweiterte-studiengangsuche.html
There are three classifications:
We will have to find out which of those best to skosify.
The text was updated successfully, but these errors were encountered: