...
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 | |
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 |
committee.committee_abbr | field_collector | Field 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? Yes [SS] |
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_loc_place | Field Location Verbatim | Custom |
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? Was already tied to org authority so it is feasible [SS]. |
"catalog date" | date_association | Date Association | Fixed text. Where is this? No longer in UI; still a placeholder in schema. (could be Associated Date Type; in 1.0 probably have to use Associated Date Note) [SS] 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? Not in | Fixed text. Do not load into 1.0 UI; still a placeholder in schema. Could use Associated Date (1.0 and future) [SS] . 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.
...