Comments (15)
@timvdstap Once we have the different datasets available within the Hakai CKAN website. It would be good to generate a DOI for each individual dataset.
from hakai-datasets.
I think having a global attribute DOI is alright, it doesn't follow any conventions but also doesn't break any.
If we need to follow a convention like ACDD then populating the id and naming_authority attributes would be a standard way to follow the convention guidelines. We can certainly have the DOI in multiple fields. ACDD also doesn't specify which naming_authority, Hakai would just have one so it's easy otherwise, other groups may want to prioritize.
Linking to CKAN record, I think that makes sense if we interpreted the CKAN record as the master hub and long-term repository for each dataset through its different versions and methods to access (If ERDDAP is dropped in the future, that DOI should point to the newest and greatest ERDDAP 2.0 ...).
from hakai-datasets.
Hi @timvdstap, I just added the Dosser et al. dataset to the table above for all the hakai datasets. All those would need a DOI attached to the Hakai CKAN record. Let me know when this is available!
from hakai-datasets.
Hey @JessyBarrette -- I'll pass this request on to @Br-Johnson if that's OK. Brett's more experienced with minting DOIs!
@Br-Johnson any chance you can help Jessy out with this?
from hakai-datasets.
No problem. The CKAN record for the nutrient dataset says it's deleted...
Just wondering why in the titles of the CKAN datasets do they end in ',Research'? I noticed there are some ',Provisional' records as well. What is the strategy there?
I will mint DOIs for Chlorophyll, Water Properties, and Dosser et al. now.
from hakai-datasets.
OK, I've updated the DOI table above with the appropriate DOIs
from hakai-datasets.
from hakai-datasets.
Thanks the DOIs were now added to the CKAN metadata records. I will also update the ERDDAP datasets to include the DOIs by following the ACDD convention {"id" and "naming_authority" global attributes).
from hakai-datasets.
Let's track the DOI update to the ERDDAP datasets here:
- Chlorophyll Research
- CTD Profile Research
from hakai-datasets.
We should consider how we implement DOIs in ERDDAP. Ocean Networks Canada and Scripps use a non-standard DOI global attribute. Partly, because the datasets already had a separate id that wasn't a DOI. See ONC example here and Scripps example here
Here is an ERDDAP google groups discussion on the matter.
I've done what ACDD recommends (as you point out) as well with IYS datasets on ERDDAP, but I suppose there is no harm in taking both approaches and include a DOI global attribute as well as 'id' and 'naming_authority'.
Thoughts @pramod? CIOOS Data Management Task Team is discussing how to implement DOIs for CIOOS generally and we'll have to decide on a standard for how to include DOIs...
from hakai-datasets.
Thanks for adding this info, @Br-Johnson . Interesting to see where ONC was actively asking about this. If helpful, we could follow-up with Reyna and/or Chantel Ridsdale from ONC, as they have also thought about this quite a bit. It makes sense to me to have the DOI link to the metadata record, as we are doing; however, ONC may be taking a different approach. However, note that Reyna/ONC may be feeling a bit over-extended these days, so we should be careful and reduce parallel threads of activity with ONC. @pramod-thupaki has most recently interacted with Reyna/ONC, so he can perhaps comment on when/if/how to best engage them about this particular topic.
from hakai-datasets.
OK, sounds good @raytula. Just to make sure I'm being clear I'm just talking about the minor detail of which global attribute the DOI is located under in the the ERDDAP .XML file. I don't even know what use-cases this would affect other than if queries for an ERDDAP dataset were made to an ERDDAP server based on trying to find a specific DOI you might have to look in multiple attributes based on the discrepancy I noted above. But I'm not sure when or if anyone would even need to make such a query.
Where the DOI lands is indeed something that ONC does differently though which I think you know. ONC has a 'Dataset Landing Page' with basic metadata about the DOI, whereas we as you know point to CKAN as our landing page.
from hakai-datasets.
@Br-Johnson @JessyBarrette thanks for the additional info/feedback. I withdraw my suggestion to sync up with ONC about this. Happy to proceed in whatever way makes most sense to you guys.
Yes, I view the CKAN record as the 'master hub', so makes sense for users to land there,
from hakai-datasets.
Apologies for the slow response, I have summarized my opinions/findings below ...
Re: DOI as global attribute on ERDDAP - This appears to follow the best practices. As there is no conflict with standards, this seems the way to go. Need to see how this would work with versioning datasets (is this being discussed at the DMPTT ?)
Re: DOI Landing page - using the CKAN record for this is consistent with our practices. Question - what about CKAN records that have multiple ERDDAP datasets (collections?)
Re: syncing with ONC - Doesn't seem necessary at this point. We should continue working with ONC and rest of CIOOS on DMPTT ... connecting to individuals in ONC might be more productive if we have something specific we want them to comment on - in an offline manner (shared docs and such).
The ONC wiki (here) has details on their DOI practices and future plans.
from hakai-datasets.
Here is another resource we can help to guide our plans - RDA Guidelines for Making Data Citable
Note - not for light reading !
from hakai-datasets.
Related Issues (20)
- Skeena River Fisheries CTD Data Provisional/Research datasets HOT 1
- github action tests HOT 1
- Update hakai-datasets to latest and greatest HOT 1
- Hakai ERDDAP is sending notifications to info at cioospacific.ca
- New ERDDAP Dataset: Hakai HPLC dataset Research dataset
- ...
- Algae Explorer Sentinel datasets daily and 8 day datasets HOT 1
- BamfieldBoL remote station new dataset HOT 6
- Decide which repo will be base repo for Hakai Data Mob. tasks and issues HOT 5
- [Issue]: SewardBoL view is not available and is breaking the creation of the different erddap views. HOT 1
- KC Buoy DO data is missing HOT 2
- Hakai Goose server is unstable HOT 18
- Add Hakai ERDDAP uptime check link HOT 1
- Deploy ERDDAP through Caprover HOT 4
- Rename Hakai ERDDAP repository? HOT 4
- Which email address should Hakai ERDDAP admin points to HOT 21
- Tracking downloads with plausible and ERDDAP HOT 17
- Maintain Datasets Files between the different servers HOT 2
- Vulnerability with postgresql driver HOT 7
- ERDDAP with NGINX HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from hakai-datasets.