search

RDFBones / RDFBonesPhaleron

An RDFBones implementation of the data collection routines developed for the Phaleron Bioarchaeological Project.
1 stars 0 forks source link

Collection of information on sampling of human remains #28

Open cuboideum opened 3 years ago

cuboideum commented 3 years ago

[...] Sampling (with info in notes) [and] X-ray/CT image taken are other aspects of skeleton treatment that could be recorded here.

Originally posted by @JEB13 in https://github.com/RDFBones/RDFBonesPhaleron/issues/20#issuecomment-924657438

cuboideum commented 3 years ago

I suggest there should be a separate module for sample taking record all the relevant information on affected elements, people and laboratories involved, objectives, implications for analyses, etc.

cuboideum commented 3 years ago

RDFBones has a mechanism to record the curation history of specimens. I could give a little talk on this in an online meeting if this might be helpful.

JEB13 commented 3 years ago

Hi Felix:

We discussed this today. I agree on the specific module for detailed information. While I don't have strong feelings about this, in that the inventory is impacted by sampling (subtraction of tissue), I wonder if there shouldn't be a spot where we record: Observer (Name for data caputure, with date and unlimited list); Data Entry (Name, date, unlimited); Sampled (name name -- with text box for description). Similarly X-ray/CT for paleopathology, following Observer; Data Entry?

eprevedo commented 3 years ago

Hello! Besides the participant roles (as you discussed above), here is what we decided regarding sampling information for now (i.e., to be included in the skeletal inventory): We would like a separate text box in the skeletal inventory entitled "sampling notes", wherein we would include the basic information we want as text (ie specimens, researcher, date). So, I think this is what we decided and that it will be simpler to remove this option from the participant roles, as this will be so specific and a single text box will suffice? @cuboideum @JEB13 @

JEB13 commented 3 years ago

I do think we need a separate module for detailed information. I was just thinking of a signal on the Inventory form that something that had been recorded was no longer there.

cuboideum commented 3 years ago

What @JEB13 means is a recorded change to the inventory, right? I have given this some thought in our previous research project. Probably it might be easier to present this in a meeting than in a comment on this issue.

JEB13 commented 2 years ago

Haven't we settled this in our discussion?

cuboideum commented 1 year ago

@hayesleigh and @cuboideum discusse this issue in a video conference on 10 August 2023. They decided to move it to the 'Future Development' milestone.