Forgot password? | Forgot username? | Register

Object-specific site / locality data

Object-specific site / locality data

Hi all,
This topic has come up in the Google Group emu-user-community (which has been active of late with UK and US people).

In archaeology and geology in particular, not so long ago when people collected things, they would only record the name of the site the object came from. After that, lat/longs or other information were recorded for the expedition as a whole, and that's reflected in the current design of the Collection Events module.

As technology has moved along, we can now record a set of coordinates that define the boundary of a site, and we can often pinpoint within the site where each object came from. This creates the need for precise location information per object. Has anybody done that yet?

Also, beyond the geospatial data collected, there are sets of data describing the environment in which the object was found (habitat, stratum) [it was recently pointed out to me that there can be whole datasets associated with this, including 3D modelling], and sometimes names that have been given to classify a particular part of the site, e.g. Structure 3, Burial Chamber 2, or Western Bank, near contact with Arunta Complex.

Should we add (has anyone added) tabs to the Catalogue to deal with this?

Another solution that occurs to me is a hierarchy of relationships in the Sites module. I've had a look and can't see one currently.

What do you all think?
Barbara

Administrator has disabled public posting. Please login or register in order to proceed.
There are 0 guests and 0 other users also viewing this topic

Board Info