omeka / omeka/plugin-Geolocation
Resolve inconsitency between datamodel and interface
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
It looks like the datamodel allows multiple locations per item, but the user interface does not. With exposure of the API, a client could post new locations in a way that the current admin UI doesn't allow.
Maybe the Omeka 2.1-compatible plugin changes UI to allow multiple locations, and maybe even eats its own dogfood?
Playing with this on branch multiple_locations
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 multiple_locations branch and comparing the datamodel's support for multiple locations with the admin UI and API behavior. Confirm the expected Omeka 2.1-compatible interface, then verify that locations can be added consistently through the admin UI and API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100