futres / template

user template for FuTRES data import
0 stars 0 forks source link

John changes #3

Closed jdeck88 closed 5 years ago

jdeck88 commented 5 years ago

I made a few changes to the template (beyond just formatting).
Basically, the changes were meant to align organismID,specimenType, and dataAggregate to DwC terms. I think the terms i provided map OK but we can talk about it if you want. I also filled out the entity_alias column for all fields.

jdeck88 commented 5 years ago

I think we should give precedence to DwC for the organismID... has a longer history of use. And, no, the GUID is not typically the same as the catalog number for a specimen

jdeck88 commented 5 years ago

If the goal is to make a unique reference only within the FUTRES universe we can do that easily with a UUID. Creating a persistent GUID is much harder.

John

On Tue, Jun 18, 2019 at 7:04 PM Meghan Balk notifications@github.com wrote:

@megbalk commented on this pull request.

Is it easy to generate a GUID for a specimen?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/futres/template/pull/3?email_source=notifications&email_token=AAIZ3ROUSL6JVVDBW6YCXADP3GH2VA5CNFSM4HZE2FZKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB36LM7Q#pullrequestreview-251442814, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIZ3RJ2OR735CKWPZJRLJLP3GH2VANCNFSM4HZE2FZA .

-- John Deck (541) 914-4739

jdeck88 commented 5 years ago

we should add a field called catalogNumber ( http://rs.tdwg.org/dwc/terms/catalogNumber)

On Wed, Jun 19, 2019 at 10:32 AM Meghan Balk notifications@github.com wrote:

@megbalk commented on this pull request.

Got it. Where can users report the catalog number?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/futres/template/pull/3?email_source=notifications&email_token=AAIZ3RLQXV6F6N2NRCNRRR3P3JURZA5CNFSM4HZE2FZKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB4BQJSA#pullrequestreview-251856072, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIZ3RPGCB6BWGQ3UPPYBRDP3JURZANCNFSM4HZE2FZA .

-- John Deck (541) 914-4739

ramonawalls commented 5 years ago

Actually, I think organismID is the wrong DwC field to use. Organisms in Darwin Core has a specific meaning that is not tied to specimens, but rather the individuals or collections of organisms (see http://purl.obolibrary.org/obo/PCO_0000031). Instead, I suggest we use http://rs.tdwg.org/dwc/terms/materialSampleID. @jdeck88 I am kind of shocked that you did not suggest using that in the first place, after the years of effort that went into it.

Very few specimens coming in to FuTRES will have GUIDs already, so, as John indicated, we will need to make internal IDs for those. If they do have one, great. We should use it.

I'm not sure about the entity alias -- I am going to give this some deep thought.

jdeck88 commented 5 years ago

I saw dwc:organismID in the URI field and i was thinking that we wanted to track a particular bone coming from the same organism. So, what about materialSampleID for the particular sample and organismID in cases where we know it is from the same individual?

On Wed, Jun 19, 2019 at 12:29 PM Ramona Walls notifications@github.com wrote:

Actually, I think organismID is the wrong DwC field to use. Organisms in Darwin Core has a specific meaning that is not tied to specimens, but rather the individuals or collections of organisms (see http://purl.obolibrary.org/obo/PCO_0000031). Instead, I suggest we usehttp://rs.tdwg.org/dwc/terms/materialSampleID. @jdeck88 https://github.com/jdeck88 I am kind of shocked that you did not suggest using that in the first place, after the years of effort that went into it.

Very few specimens coming in to FuTRES will have GUIDs already, so, as John indicated, we will need to make internal IDs for those. If they do have one, great. We should use it.

I'm not sure about the entity alias -- I am going to give this some deep thought.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/futres/template/pull/3?email_source=notifications&email_token=AAIZ3RJMLUY4RJWFBO446B3P3KCKLA5CNFSM4HZE2FZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYDBIGQ#issuecomment-503714842, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIZ3RJOIE3FYYSCKJHDT2LP3KCKLANCNFSM4HZE2FZA .

-- John Deck (541) 914-4739

meghalithic commented 5 years ago

So we need a few extra fields:

  1. spot for a catalog number using dwc: catalogNumber
  2. way to say if something is a fossil or not using organismID
  3. a way to say if something is part of a lot or an individual materialSampleID
jdeck88 commented 5 years ago

i just committed an update adding dwc:catalogNumber and dwc:materialSampleID. Left organismID in there which people can use to designate a particular organism. We can leave out the naval-gazing which will ultimately ensue when we start talking individuals and populations.

John

On Wed, Jun 19, 2019 at 12:49 PM Meghan Balk notifications@github.com wrote:

So we need a few extra fields:

  1. spot for a catalog number using dwc: catalogNumber
  2. way to say if something is a fossil or not using organismID
  3. a way to say if something is part of a lot or an individual materialSampleID

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/futres/template/pull/3?email_source=notifications&email_token=AAIZ3RJBFSXIHZ3ZUDTNTJ3P3KETTA5CNFSM4HZE2FZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYDCYVQ#issuecomment-503721046, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIZ3RJOZHO3DXMYHN43KWDP3KETTANCNFSM4HZE2FZA .

-- John Deck (541) 914-4739