Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add TwoRavens generated variable-level DDI to Dataverse API #3604

Open
amberleahey opened this issue Jan 27, 2017 · 4 comments
Open

Add TwoRavens generated variable-level DDI to Dataverse API #3604

amberleahey opened this issue Jan 27, 2017 · 4 comments
Labels
Feature: API Feature: TwoRavens Type: Feature a feature request User Role: Curator Curates and reviews datasets, manages permissions

Comments

@amberleahey
Copy link

amberleahey commented Jan 27, 2017

For the Dataverse DDI Explorer add-on to solely rely on the DDI exported from Dataverse (without the need to load an additional file), the DDI requires the node to contain frequency and statistical information.
Including the frequency info simply requires the /codeBook/dataDscr/var/catgry/catStat nodes to be added. This frequency information was present in earlier editions of Dataverse (as can be seen from an older file migrated to our new dataverse instance https://dataverse.scholarsportal.info/api/datasets/export?exporter=ddi&persistentId=hdl%3A10864/10799), so it shouldn’t be too difficult to add it back.
The statistic information (including "vald","invd","max","min","mean","medn","mode" and "stdev" values) requires sumstat nodes with the following xml path /codeBook/dataDscr/var/sumStat.

If you could include this request, it would be greatly appreciated.

@djbrooke
Copy link
Contributor

Thanks @amberleahey! Nice talking with you earlier today.

I'm going to tag @scolapasta in case there are additional technical details that are at top of mind after the call.

@djbrooke djbrooke changed the title Add TwoRavens generated variable-level DDI to Dataverse API Add TwoRavens generated variable-level DDI to Dataverse API Jan 30, 2017
@djbrooke
Copy link
Contributor

Hey @amberleahey - we talked about this in our backlog grooming meeting today. We discussed a few different approaches to exposing the statistical information. @landreev - you mentioned you were going to add some details and ask a few questions.

@pdurbin pdurbin added the User Role: Curator Curates and reviews datasets, manages permissions label Jul 4, 2017
@amberleahey
Copy link
Author

amberleahey commented Oct 9, 2018

Hi folks, @lubitchv and I are revisting where this frequency and statistical information actually gets generated in DV and it would be good to understand a bit more about why and how we can get this stored in the DDI XML upon upload / ingest in DV rather than relying on seperate calls to R / Two Ravens generated files...again just getting up to speed on this, seems like it would be helpful for both Data Explorer and new Data Curation Tool to have this stored in DDI XML from the get go. Will investigate more and provide separate issue if we need to.

@pdurbin
Copy link
Member

pdurbin commented Sep 30, 2022

Related (I think):

Also, can we remove Two Ravens from the title? We haven't used it for years. I'm not sure how it's related.


Update:

v1 of Data Explore mentions the prep file: https://github.com/scholarsportal/Dataverse-Data-Explorer/blob/v2.1/assets/js/controllers/chart.js#L50

v2 doesn't mention prep but I'm not sure if it's used or not. I'm guessing @lubitchv knows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: API Feature: TwoRavens Type: Feature a feature request User Role: Curator Curates and reviews datasets, manages permissions
Projects
None yet
Development

No branches or pull requests

4 participants