Geospatial services

Needed by whom and when

Basic statements about who needs the functionality and by when.

Museum X: Probably not needed by the time PAHMA and UCJEPS go live -- not replacing current functionality.

Overview

Geospatial services enrich object records in order to provide better geospatial information that can be used for analysis and visualization.

User stories for definition

Geospatial services: CollectionSpace user can perform georeferencing (the process of converting text descriptions of locations to computer-readable geographic locations, such as a GIS system use)

Geospatial services: Administrator can perform bulk georeferencing on a set of records

Geospatial services: Locations can be validated (e.g., states or regions are in the correct country; latitude/longitude values are within the boundaries of political or geographic areas identified on the record)

Prioritization of user stories

As definitions and priorities are clarified, the user stories above should be moved into relative order below.

Must have for 1.x-MUSEUM (when they go live in system)

Placeholder for required functionality.  As a general rule, functionality that you need and use now should go here or where you have existing data.  However, this is up to the museum.  We will have to balance requirements against resources and timelines.

Placeholder

MUSEUM could wait six to twelve months

What could wait?  These will be re-prioritized at a later date.

Placeholder

MUSEUM would like to have this eventually

These are nice to have but not a near term requirement.

Placeholder