--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/bb2e42ab-04fd-412d-b96d-05b455cbfe5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/78c661a8-f610-4de9-a666-12550328fa0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8GON0K%2BUcVOc_LO7c%2BUhzRdAYt1N137ahcogikBbcrX2g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
It would be convenient to identify restrictions per datafile rather than at a dataset level element, but there doesn't seem to be an explicit 'datafile' element in DDI 2.5 that I am aware of. I have not looked at DDI Lifecycle. Is this under future consideration for Dataverse? Steve knows a lot more about DDI 3&4 and may recommend I don't go there at this point...
As you say oai-ore and json output includes [restricted":true]. Is the json output built on any standard or is it and export of all the metadata and database fields existing for a dataset?
Perhaps the best place to add this is in the study description section of the DDI since that section provides a summary of all files in the dataset.
On Tue, May 14, 2019 at 6:28 AM Philip Durbin <philip...@harvard.edu> wrote:
Ah, thanks to both of you. I was having trouble finding an example.In a "vanilla" non-forked installation of Dataverse, you can see something like "There are 2 restricted files in this dataset." under "Restricted Files + Terms of Access" under the "Terms" tab of a dataset like https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/RKEZEPHere's where the number comes from in the code from a method called "getRestrictedFileCount":It looks like you can get "dvcore:restricted":true (or false) at the file level from the "OAI_ORE" export format: https://dataverse.harvard.edu/api/datasets/export?exporter=OAI_ORE&persistentId=doi:10.7910/DVN/RKEZEPYou can also get "restricted":true (or false) at the file level from the "dataverse_json" export format, but this is not based on a standard: https://dataverse.harvard.edu/api/datasets/export?exporter=dataverse_json&persistentId=doi:10.7910/DVN/RKEZEPThe current list of export formats can be found at http://guides.dataverse.org/en/4.14/user/dataset-management.html#supported-metadata-export-formatsIt sounds like want an OAI-PMH harvest-able field that gives just the number of restricted files (rather than adding them up). Something like "numberOfRestrictedFiles: 2". I can't imagine this would be hard to add as long as there's a field to put it in. Finding the right field in the right standard is the tricky part. :)I hope this helps,Phil
On Tue, May 14, 2019 at 5:44 AM Steven McEachern <stev...@gmail.com> wrote:
Hi Phil
We have renamed “Restricted Access” to “Controlled Access” in our ADA installation.
Cheers
Steve
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/78c661a8-f610-4de9-a666-12550328fa0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
----Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8GON0K%2BUcVOc_LO7c%2BUhzRdAYt1N137ahcogikBbcrX2g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Otherwise, a potential element is under the Data Access <dataAccs> 2.4 Section, where we could manually enter the metadata, which is not as enticing as generated datafile metadata:
Extent of Collection
<collSize> 2.4.1.4
Summarizes the number of physical files that exist in a collection, recording the number of files that contain data and noting whether the collection contains machine-readable documentation and/or other supplementary files and information such as data dictionaries, data definition statements, or data collection instruments.
Example:
<collSize>1 data file + machine-readable documentation (PDF) + SAS data definition statements</collSize>
Optional
Not Repeatable
Attributes: ID, xml:lang, source
Contains: #PCDATA, Link to other element(s) within the codebook.
Anyway, am open to suggestions.
Thanks
Janet
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/7949fb6f-add1-483b-863f-bf3f3f1c6104%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I'm open to suggestions as well but I wanted to respond to Janet asking about Dataverse's "native" JSON format: "Is the json output built on any standard or is it an export of all the metadata and database fields existing for a dataset?"No, the native Dataverse JSON format is not based on any standard. It's meant to be a relatively high fidelity "dump" or backup of what's in the database. It's the same format that's used in the native API to create a dataset.I hope this helps,Phil
On Wed, May 15, 2019 at 5:22 AM Janet McDougall - Australian Data Archive <janet.m...@anu.edu.au> wrote:
Hi All
I got distracted by thinking about access info per datafile level metadata, but as Phil says, it would also be good to have the calculated total of restricted files listed per dataset. If this was calculated content the DDI element/field would need to be reserved for export use only, or repeatable?
Otherwise, a potential element is under the Data Access <dataAccs> 2.4 Section, where we could manually enter the metadata, which is not as enticing as generated datafile metadata:
Extent of Collection
<collSize> 2.4.1.4
Summarizes the number of physical files that exist in a collection, recording the number of files that contain data and noting whether the collection contains machine-readable documentation and/or other supplementary files and information such as data dictionaries, data definition statements, or data collection instruments.
Example:
<collSize>1 data file + machine-readable documentation (PDF) + SAS data definition statements</collSize>
Optional
Not Repeatable
Attributes: ID, xml:lang, source
Contains: #PCDATA, Link to other element(s) within the codebook.
Anyway, am open to suggestions.
Thanks
Janet
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/7949fb6f-add1-483b-863f-bf3f3f1c6104%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.