Skip to content

Instantly share code, notes, and snippets.

@drh-stanford

drh-stanford/Survey of geospatial repository efforts.md

Created February 16, 2017 20:21
Show Gist options
  • Save drh-stanford/0e22c9f5ce780c106fd45c1d91d71d16 to your computer and use it in GitHub Desktop.
Save drh-stanford/0e22c9f5ce780c106fd45c1d91d71d16 to your computer and use it in GitHub Desktop.
Download ZIP
Survey of geospatial repository efforts
Raw
Survey of geospatial repository efforts.md

Survey of geospatial repository efforts

I sent out a brief survey and have some results to share. Here are the primary questions from the survey:

  1. Do you currently have an institutional repository for non-geospatial content in production?
  2. Are you interested in implementing geospatial data repository?
  3. What are the primary function(s) you want in a geospatial data repository?
  4. What are you primary challenge(s) to implementing a geospatial data repository?

We had several (n=10) people from 9 institutions answer these questions: Colorado School of Mines, Colorado State University, Colorado at Boulder, Cornell, Harvard, Michigan, NYU, Stanford, and UC Santa Barbara.

Current

Six institutions are using DSpace, four are using Hydra, and one has a home-grown solution. A couple institutions are using both or are planning switching to Hydra.

Stage

The majority are in the planning stage currently, and three have implementations in production.

Services

Everyone wants discovery services! A few want access or delivery services. Most want preservation services, although that's not a first-step for many.

Challenges

Most everyone cited lack of resources or technical expertise as a barrier. Also, many have challenges selling the idea to management.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment