hypertopic / geoxene Goto Github PK

Description

What is the valuable outcome that cannot be achieved with current features?

For the moment, users have to manually go to each vase's page to add the spatial attribute to localize them on the map. It would be easier for them to be able to see all the vases that doesn't have this spatial attribute and have for example a page that allows them to easily set the tomb's number of the vases that are not localized yet.

For which stakeholder (people, role, project, domain) is it important?

Especially for people who want to be able to see easily the vases not localized on the map yet (that miss the spatial attribute), and easily set the tomb where they were found, as a bulk.

Which user action should be enabled (or restricted)? For who?

Examples: Display non-localized vases on a specific page and set their location as a bulk.

• See which vases don't have a set spatial attribute.
• Offer to the user the possibility to set this attribute for all the unspecified vases (bulk).

Additional details (solutions you think about, or workarounds you tried)

Deliverables status

Phase 1

• Scenarios (Gherkin)
• Mockups
• Implementation strategy

Phase 2

• Implementation

Phase 3

• Screencast

From GoogleMaps documentation :

A place ID is a textual identifier that uniquely identifies a place. The length of the identifier may vary (there is no maximum length for Place IDs).
https://developers.google.com/maps/documentation/places/web-service/place-id

A place ID is necessary in Porphyry to be able to click on a marker.

Description

What is the valuable outcome that cannot be achieved with current features?
Users can now create new locations but cannot delete them, which can be a problem as it forces a developer to delete unwanted ones directly from the SQLite database.

For which stakeholder (people, role, project, domain) is it important?
Especially for people who already use GeoXEne to insert new locations as they might need to delete unwanted ones.

Which user action should be enabled (or restricted)? For who?

As there are no roles implemented yet on GeoXEne, any user can delete an unwanted location (as he can insert a new one)

Phase 1

• Scenarios (Gherkin)
• Mockups
• Implementation strategy

Phase 2

• Implementation
  Phase 3

• Screencast