-
The current import process is inefficient, complicated, and not well documented (#24). A full rewrite of the import script is necessary. It consists of the following parts:
1. Good documentation!
…
-
I tried to import with the following error message:
./import.sh
> jskos-server@0.3.0 import /home/dt/Dokumente/jskos-server
> node import.js "-r" "-c"
running in development mode
Warning: If …
-
If you edit and save a mapping, it shows your name as the creator.
But when changing your Name the changes do not get applied to the saved mapping, the name stays the same as before, although it ough…
-
First check whether object type of two objects A and B match. Then append values from B to A unless they are single-valued (such as `prefLabel.en`) or complete arrays.
-
[DANTE](http://api.dante.gbv.de/) now supports fetching data for multiple concepts simultaneously by concatenating them with a `|`. In combination with `&properties=narrower`, we could speed up select…
-
Currently, MappingBrowser loads labels (and notations if necessary) for all concepts in all mappings each with a separate request. These requests should be bundled by concept registry, i.e. having onl…
-
Data import should be documented better to get started easily. This also requires some cleanup of import process (move parts of `scripts/import.sh` to `import.js`) and examples, e.g.:
* how to impo…
-
This is and should not be not used. Rights may be attached to identities as OAuth scopes but that's another issue.
-
`previous/next` are a nice alternative for simple ordering of concepts, as opposed to using the `skos:memberList` complexity. But I'm afraid SKOS doesn't have such props:
```jsonld
"previous": {
…
-
Concept schemes returned by the `/voc` endpoint should indicate whether the server can provide concepts for that scheme or not, for example by setting the `concepts` property to `[]`.