Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

With CollectionSpace 1.0, the schema have changed, and therefore so will the data mapping and customizations we are employing in the UCJEPS deployment of CollectionSpace 1.0.  This is not a final data mapping for the University and Jepson Herbaria. This is just a next iteration.  Changes from the previous mapping are in blue.

Data

This iteration will focus on object cataloging data, loans out, and relationships.

If time permits, we will load a 10,000 object record data set. Otherwise, we will stick with the data set loaded into the 0.7 instance (approx 1300 specimens, plus all loans, all persons, all organizations from SMaSCH)

Object cataloging data

See the CollectionSpace catalog schema for 0.7

SMaSCH

CollectionSpace object schema

CS User Interface Title (** = different from UI)

Note

accession.accession_id

object_number

Accession Number **

Change field title

institution.inst_name

collection

Collection

Dropdown (Collection values)

accession.coll_num_prefix + coll_number + coll_num_suffix

other_number

Number

Moved to Field Collection Number.  Is this feasible, or leave as is?

"collector number"

other_number_type

Number Type

Not needed if we move this to Field Collection Number.

accession.notes

comments

Notes Comments


objkind.kind

form (Object Description Information)

Form

Dropdown (Form values)

taxon_fullname.fullname

title

Taxon **

Change field title

accession.phenology (decoded)

phase (Object Description Information)

Phenology **

Change field title. Dropdown (Phenology values)

accession.early_jdate (calc)

field_collection_date_earliest

Field Collection Date Earliest

Custom 

accession.late_jdate (calc)

field_collection_date_latest

Field Collection Date Latest

Custom

accession.datestring

field_collection_date

Field Collection Date Custom

Was a custom field but now exists in the 1.0 schema

committee.committee_abbr

field_collection_collector (?)

Field Collection Collector

CustomWas a custom field in 0.7 map. Field_collection_collector now exists, and is tied to Org and Person authorities.  Feasible to put in correct place?

accession.loc_lat_decimal

field_loc_lat_decimal

Field Location Latitude Decimal

Custom

accession.loc_long_decimal

field_loc_long_decimal

Field Location Longitude Decimal

Custom

accession.loc_place (calc)

field_loccollection_place (?)

Field Location Verbatim Custom **

Was a custom field in 0.7 map, but now exists in 1.0 map

accession.loc_county

field_loc_county

Field Location County

Custom

accession.loc_state

field_loc_state

Field Location State

Custom

accession.loc_country

field_loc_country (temp custom)

Field Location Country

Custom

accession.loc_elevation

field_loc_elevation (temp custom)

Field Location Country

Custom

accession.coll_num_prefix + coll_number + coll_num_suffix

?

Field collection number

Was Now available in 1.0 (was in Other Number .  Is this feasible or leave as is?in 0.7 map)

committee.committee_abbr

?

Field collection collector

Was Now available in 1.0 (was a custom field.  Now exists ) and is tied to person and org authorities.  Is this feasible or leave as is?

"catalog date"

date_association

Date Association

Fixed text. Where is this? (will be Associated Date Type; in 1.0 probably have to use Associated Date Note)  Do not load into 1.0.  May end up in Associated Date information eventually, or create date/modify date.

accession.catalog_date

catalog_date

Date Text Where is this? Associated Date (1.0 and future)

Fixed text. Do not load into 1.0.  May end up in Associated Date information eventually, or create date/modify date.

Notes

  • loc_county, loc_state, and loc_country will not be supported by dropdowns for now
  • field_collector will not be controlled by an authority in this iteration.
  • Collecting event information is being added as custom temporary fields.  CollectionSpace will have a separate authority system for collecting events and collectors, so these mappings will change in the future.

...

SMaSCH

CollectionSpace loans out schema

CS User Interface Title (** = different from UI)

Note

loan_event.uc_loan_num + loan_event.jeps_loan_num

Loan out number

 

smasch has two types of loan identifiers.
Loan Number relates accessions in a single collection that make up a loan.
Loan ID relates loans from each collection that make up a loan.
"Loan Number" = collection + loan_num
"Loan ID" = loan_id

loan_event.curr_inst

Borrower

 

Probably should keep this as borrowing institution (organization authority)

loan_event:         
  curr_for_fname,
  curr_for_lname,
  curr_for_position

Borrower's contact

 

Probably should keep this as borrowing agent (person authority)

 

 

loan_event.inhouse_notes + loan_event.noteworthy_inclusions

Loan out note

 

 

loan_event.loan_status +
loan_detail.return_status

Loaned object status

 

It looks like this field is not currently active.  smasch keeps track of two status types:
loan status ('Active' or 'Cancelled')
return status ('All in', 'All out', 'Partial', 'Discrepancy', 'Unknown')

Loan date?

 

Loan Out Date

Does SMaSCH have a loan date?

Relationships

  • Loan Out to Object

...

  1. Collection values:
    1. Jepson Herbarium
    2. University of California Herbarium, UC Berkeley
    3. University of California
  2. Form values:
    1. Illustration
    2. Mounted on Paper
    3. Photocopy
    4. Photograph
    5. Stored in a Box or Bag
  3. Phase (Phenology) values:
    1. Cone
    2. Flowering
    3. Flowering/Fruiting
    4. Fruiting
    5. Spores/Sporangia
    6. Vegetative (non-reproductive)
  4. Loaned Object Status values:
    1. Active (Unknown)
    2. Active (All Out)
    3. Active (All In)
    4. Active (Partial)
    5. Active (Discrepancy)
    6. Cancelled (Unknown)
    7. Cancelled (All Out)
    8. Cancelled (All In)
    9. Cancelled (Partial)
    10. Cancelled (Discrepancy)
  5. Other Number Type values:
    1. Other herbaria accession number
    2. Copied from accession number
    3. Exsiccatae number
    4. Project number
    5. Genbank number
    6. Destructive sampling number
    7. Internal cross reference
    8. Miscellaneous

Name Authority: Person

SMASCH

cSpace Person Schema

CS User Interface Title (** = different from UI)

Note

person.person_id
borrower.borrower_id

Legacy ID

 

borrower is not part of smasch; newly created to generate pk id for borrowers in loan_event table.

person.first_name +
     person.other_name +
     person.last_name
loan_event.curr_for_fname +
     loan_event.curr_for_lname

Display Name

 

 

person.first_name
loan_event.curr_for_fname

Forename

 

 

person.other_name

Middle Name

 

 

person.last_name
loan_event.curr_for_lname

Surname

 

 

person.bio_notes

Biographical Note

 

 

person.birth_year

Birth Date

 

 

person.death_year

Death Date

 

 

loan_event.curr_for_position

Occupation

 

 

loan_event.curr_inst

Group

 

 

'collector' + '; name source: ' + data_source.data_src_name  
'borrower'

Name Note

 

 

...