Talk:Data Ingestion Guidance: Difference between revisions
No edit summary |
No edit summary |
||
Line 21: | Line 21: | ||
#If you are already on the portal page, the 'Register A Collection' is in the menu under your login name in the upper right of the page. | #If you are already on the portal page, the 'Register A Collection' is in the menu under your login name in the upper right of the page. | ||
---- | ---- | ||
#About this next section:Data Requirements | #About this next section:Data Requirements--[[User:Dpaul|Dpaul]] ([[User talk:Dpaul|talk]]) 18:33, 9 January 2014 (EST) | ||
#I would avoid the word <strike>ownership</strike>, if at all possible to help the community get around this issue (eventually). This reinforces ideas / misconceptions, and adds to confusion about data, media (and copyright, and intellectual property, etc). Something like this for number 2... | #I would avoid the word <strike>ownership</strike>, if at all possible to help the community get around this issue (eventually). This reinforces ideas / misconceptions, and adds to confusion about data, media (and copyright, and intellectual property, etc). Something like this for number 2... | ||
##You have permission to contribute this dataset to iDigBio. | ##You have permission to contribute this dataset to iDigBio. | ||
Line 35: | Line 35: | ||
::validate (or verify) that "special characters" (diacritics like umlauts, tilde, cedilla) are correct in your dataset. | ::validate (or verify) that "special characters" (diacritics like umlauts, tilde, cedilla) are correct in your dataset. | ||
---- | ---- | ||
From Morphbank http://www.morphbank.net/About/Manual/imagePhilosophy.php to see how we worded "permissions" issue (revolving around images). | From Morphbank http://www.morphbank.net/About/Manual/imagePhilosophy.php to see how we worded "permissions" issue (revolving around images).--[[User:Dpaul|Dpaul]] ([[User talk:Dpaul|talk]]) 18:33, 9 January 2014 (EST) | ||
---- | ---- | ||
#These following links (to me) are not Data Requirements. (at the bottom of the page in review). They are '''Image/Media Issues''' or '''Image/Media Guidance''' | #These following links (to me) are not Data Requirements. (at the bottom of the page in review). They are '''Image/Media Issues''' or '''Image/Media Guidance'''--[[User:Dpaul|Dpaul]] ([[User talk:Dpaul|talk]]) 18:33, 9 January 2014 (EST) | ||
##Additional info about image format is here: https://www.idigbio.org/content/idigbio-image-file-format-requirements-and-recommendations | ##Additional info about image format is here: https://www.idigbio.org/content/idigbio-image-file-format-requirements-and-recommendations | ||
##If you need to learn about acceptable Creative Commons licenses in iDigBio: https://www.idigbio.org/content/idigbio-intellectual-property-policy | ##If you need to learn about acceptable Creative Commons licenses in iDigBio: https://www.idigbio.org/content/idigbio-intellectual-property-policy | ||
Line 43: | Line 43: | ||
##If you are contemplating writing a proposal (e.g., to NSF) and want to coordinate your data with iDigBio: https://www.idigbio.org/content/collaborating-idigbio-grant-proposals | ##If you are contemplating writing a proposal (e.g., to NSF) and want to coordinate your data with iDigBio: https://www.idigbio.org/content/collaborating-idigbio-grant-proposals | ||
##If you are brand new to iDigBio and looking for some entry-level info about the project, try here: | ##If you are brand new to iDigBio and looking for some entry-level info about the project, try here: | ||
---- | |||
At some future date, I would hope we have enough staff to re-visit, re-write our ingestion documentation.--[[User:Dpaul|Dpaul]] ([[User talk:Dpaul|talk]]) 18:33, 9 January 2014 (EST) | |||
I would like us to avoid a page, that has a link, that leads to a page with much-repetitive content, that leads to yet another page (often a pdf or .doc) that also has links in it. If I had to follow all of this, as a novice, I would be drowning. I think we'd need one person -- to do this (so that it's consistent) and it would need to be at least 50% of their job until done. It's better, but still I think we can streamline it more.--[[User:Dpaul|Dpaul]] ([[User talk:Dpaul|talk]]) 18:33, 9 January 2014 (EST) |
Revision as of 19:33, 9 January 2014
--Dpaul 16:49, 9 January 2014 (EST)
- Regarding data@idigbio.org now that dp has a gator link, does this mean I can be added to the mailing list that "sees" data@idigbio.org--Dpaul
- Where do users send email if they have a question
- (At Morphbank, to keep this straightforward, all email requests for help go to morphbank@scs.fsu.edu
- We do not have 2 separate paths for help / issues requests.
- I am assuming (I think) that clicking to send "feedback" generates a Redmine ticket (efficient and transparent). But, data@idigbio.org is not transparent.--Dpaul
- About this Section: Registering Your Collection in Preparation for Data Ingestion
- I suggest a different order. See next.--Dpaul
When your data are ready for ingestion, please see the next steps.
- Get an iDigBio account for yourself (if you don't have one yet). https://www.idigbio.org/auth/login.php
- These are the only login credentials you will need.
- Log in with your iDigBio account username and password. https://www.idigbio.org/auth/login.php
- Register your collection. http://portal.idigbio.org/register OR
- Register your collection at GRBIO
- Repository: http://grbio.org/find-biorepositories OR
- Institutional Collections: http://grbio.org/find-institutional-collections
- If you are already on the portal page, the 'Register A Collection' is in the menu under your login name in the upper right of the page.
- About this next section:Data Requirements--Dpaul (talk) 18:33, 9 January 2014 (EST)
- I would avoid the word
ownership, if at all possible to help the community get around this issue (eventually). This reinforces ideas / misconceptions, and adds to confusion about data, media (and copyright, and intellectual property, etc). Something like this for number 2...- You have permission to contribute this dataset to iDigBio.
- for number 3. do we need to explain or justify? how about
- Data Format choices
- DarwinCore archive format OR
- CSV files mapped to Darwin Core (and other relevant standards, example Audubon Core)
- Data Transfer
- Darwin Core Archive files harvest via IPT and RSS
- CSV files via (...)
- Data Format choices
- for number 4, please add UTF-8 reference. something like:
- UTF-8 encoding preferred (should be required).
- validate (or verify) that "special characters" (diacritics like umlauts, tilde, cedilla) are correct in your dataset.
From Morphbank http://www.morphbank.net/About/Manual/imagePhilosophy.php to see how we worded "permissions" issue (revolving around images).--Dpaul (talk) 18:33, 9 January 2014 (EST)
- These following links (to me) are not Data Requirements. (at the bottom of the page in review). They are Image/Media Issues or Image/Media Guidance--Dpaul (talk) 18:33, 9 January 2014 (EST)
- Additional info about image format is here: https://www.idigbio.org/content/idigbio-image-file-format-requirements-and-recommendations
- If you need to learn about acceptable Creative Commons licenses in iDigBio: https://www.idigbio.org/content/idigbio-intellectual-property-policy
- Next, General Information (nothing to do with Data Requirements, etc.)
- If you are contemplating writing a proposal (e.g., to NSF) and want to coordinate your data with iDigBio: https://www.idigbio.org/content/collaborating-idigbio-grant-proposals
- If you are brand new to iDigBio and looking for some entry-level info about the project, try here:
At some future date, I would hope we have enough staff to re-visit, re-write our ingestion documentation.--Dpaul (talk) 18:33, 9 January 2014 (EST) I would like us to avoid a page, that has a link, that leads to a page with much-repetitive content, that leads to yet another page (often a pdf or .doc) that also has links in it. If I had to follow all of this, as a novice, I would be drowning. I think we'd need one person -- to do this (so that it's consistent) and it would need to be at least 50% of their job until done. It's better, but still I think we can streamline it more.--Dpaul (talk) 18:33, 9 January 2014 (EST)