kit-data-manager / kit-data-manager/wap-server
Annotation URIs bound to hostname/port at creation time
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
At creation time, the annotation URI is determined based on the current hostname and port of the WAP server and will be stored in the RDF backend. At query time only annotation matching the current hostname and port are returned. This results in the situation that nothing is returned if one of these properties changes, e.g. after migrating a WAP Server from 'localhost' for testing to a production instance under a FQDN.
Currently, the only option in that case is carrying out the migration instructions descibed in a Wiki article.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the annotation URI creation and query behavior described in the issue, then read the linked migration instructions for the current data model and constraints. Determine how hostname and port changes should be handled without losing existing annotations; done criteria are not specified and need clarification before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100