Add a tool tip defining what types of data would go in here: "Antibodies, Model Organisms, Cell Lines, Plasmids, and other Tools (software, databases, services)."
This idea came up again in a conversation between FASEB & NYU. They are interested in tracking the provenance of data, specifically looking at the shared resources such as laboratories sponsored by NSF/DOE/DOA/NIH and other core facilities. Two helpful points came up in the discussion:
This would be best to define at the project level- not the research output.
Regarding what we should call the field, they stated:
FASEB resources and reached out to several colleagues who work at different user facilities and centers, and checked acknowledgments for publications where these facilities and centers were used. The terminology that is used is "user facility" or "Major User Facility", or variations (i.e., "US Department of Energy Major User Facility" or "DOE-sponsored user facility" or "ORNL’s Center for Nanophase Materials Sciences by RCA, which is a US Department of Energy Office of Science User Facility").
We'll need to consider what field name will be the clearest to users.
This work should be done as a Lambda in the new Env so that we are not duplicating effort. This will allow them to be available to the DMPTool and the DMP upload/edit forms
@mariapraetzellis commented on Tue Sep 08 2020
To describe specific datasets we'll add RRIDs. API docs are here: https://scicrunch.org/browse/api-docs/index.html?url=https://scicrunch.org/swagger-docs/swagger.json
Name the field: "Key Resources"
Add a tool tip defining what types of data would go in here: "Antibodies, Model Organisms, Cell Lines, Plasmids, and other Tools (software, databases, services)."
@mariapraetzellis commented on Tue Aug 30 2022
This idea came up again in a conversation between FASEB & NYU. They are interested in tracking the provenance of data, specifically looking at the shared resources such as laboratories sponsored by NSF/DOE/DOA/NIH and other core facilities. Two helpful points came up in the discussion:
Regarding what we should call the field, they stated:
We'll need to consider what field name will be the clearest to users.
@mariapraetzellis commented on Wed Aug 31 2022
Some additional information from Anita:
You can search for an RRID using the SciCrunch API, which works the same way as the human version: https://scicrunch.org/resources/data/source/nlx_144509-1/search
SciCrunch API (you will need to hit the elastic search endpoint and get "RIN-tools"; We will need to reach out to RRID to get an exact call once we have an APIkey. description of services https://scicrunch.org/browse/api-docs/index.html?url=https://scicrunch.org/swagger-docs/swagger.json
To resolve/pull information about any RRID, you can just hit the name-to-thing resolver that you guys run human version https://n2t.net/RRID:SCR_007700 json version https://n2t.net/RRID:SCR_007700.json