Data export

Owned by Chris Hoffman
Last updated: Apr 15, 2011Version comment
2 min read

Needed by whom and when

Basic statements about who needs the functionality and by when.

PAHMA and UCJEPS: Some functions needed by the time they move to CollectionSpace as their production system

Overview

PAHMA and UCJEPS each have other systems that publish their collections data to the web and allow searching and browsing. This is a common need across many UC Berkeley collections.

Unknown macro: {multi-excerpt}

Data export UCB user stories for prioritization

Data export: PAHMA collection managers export data sets to support research requests.  Data shared vary depending on the type of objects being examined (ethnographic, sound/image, archaeological, and osteological).  See PAHMA data export examples for more information.

Data export: UCJEPS user or programmer exports collections data in a specified format to be used for the CCH search portal (Consortium of California Herbaria). The fields required for the export are approximately these:

  • Date: Aug 13, 1903
  • CNUM: None
  • CNUM_prefix:
  • CNUM_suffix:
  • Name: Abies bracteata
  • Accession_id: SD60209
  • Country: USA
  • State: California
  • County: Monterey
  • Location: Santa Lucia Mountains, western slopes, upper reaches of Big Creek
  • T/R/Section:
  • Elevation:
  • Collector: W. R. Dudley
  • Other_coll:
  • Combined_collector:
  • Habitat:
  • Associated_species:
  • Color:
  • Macromorphology:
  • Latitude:
  • Longitude:
  • Decimal_latitude:
  • Decimal_longitude:
  • UTM:
  • Notes:
  • Datum:
  • Max_error_distance:
  • Max_error_units:
  • Annotation:
  • Hybrid_annotation:

Data export: HAVRC user or programmer exports data in VRA Core 4 format or CDWA Lite format.

Data export: Developer can produce a data extract that can be used for various purposes.

Data export: User can perform a search for objects and export data in a common format.

Data export: Developer can develop a custom data extract format for a particular collection.

Data export: PAHMA user or programmer exports collections data in a specified format to be used for Delphi faceted browser system.  Note: Actually, in the current system, Delphi queries PAHMA's collection management system directly to populate Delphi's ontology and indices.  Whether this same approach will be used with CollectionSpace remains to be seen.  However, the Delphi developer (Patrick Schmitz) believes Delphi will query CollectionSpace.  Question: What is the format of the data needed for Delphi?

Data export: UC Botanical Garden user or programmer exports collections data in a specified format to be used for the BNHM Data Warehouse.  UC Botanical Garden also supplies data for a plant propagation information web site.  Currently that is developed as a direct data integration (the plant propagation web site queries the live data rather than a data extract).

Data export: User can perform a search for objects and export the data in a custom format developed for that collection.

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.

UCJEPS Export to CCH is required. format is not critical. IPECAC protocol is sufficient

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