Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Resolve inconsitency between datamodel and interface

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
api, frontend

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.

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

Dominant language
JavaScript
Stars
12
Forks
22
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from omeka/plugin-Geolocation

All issues in omeka/plugin-Geolocation

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.