Dates in citation

[Jonathan Bohan]

In the citation at the top of each study record, it reads like this:

U.S. Census Bureau, 2017, "Current Population Survey, August 1968: Smoking Supplement", doi:10.6077/J5/IAP5WN, Cornell University, V1

I understand that "2017" is the date it was published on Dataverse, however, we would like it to reflect the date it was originally added to our archive. 

Is this possible?

Thanks,

Jonathan Bohan

CISER

[Pete Meyer]

Hi Jonathan,

This is sounding very similar to something I've encountered while working on moving previously published datasets into Dataverse.  I've been addressing this by changing the respective `createdate` and `publicationdate` entries in the `dvobect` table (in postgresql), and reindexing (which may not be necessary, but seems unlikely to hurt).

I'd recommend being careful (and making sure you have database backups) beforehand if you decide to go this route.

Best,
Pete

[Condon, Kevin M]

There is an API command that lets you change this:

Sets the dataset field type to be used as the citation date for the given dataset (if the dataset does not include the dataset field type, the default logic is used). The name of the dataset field type should be sent in the body of the reqeust. To revert to the default logic, use :publicationDate as the $datasetFieldTypeName. Note that the dataset field used has to be a date field:

PUT http://$SERVER/api/datasets/$id/citationdate?key=$apiKey

---

From: dataverse...@googlegroups.com <dataverse...@googlegroups.com> on behalf of Pete Meyer <me...@hkl.hms.harvard.edu>
Sent: Wednesday, March 7, 2018 3:12:16 PM
To: Dataverse Users Community
Subject: [Dataverse-Users] Re: Dates in citation

 

--
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/2e3d0000-8b26-4432-bf17-c17074f92a0c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Durand, Gustavo]

There's also an API to change which date field is used for a particular dataset's citation. From the API guide:

( http://guides.dataverse.org/en/latest/api/native-api.html#datasets )

Sets the dataset field type to be used as the citation date for the given dataset (if the dataset does not include the dataset field type, the default logic is used). The name of the dataset field type should be sent in the body of the reqeust. To revert to the default logic, use :publicationDate as the $datasetFieldTypeName. Note that the dataset field used has to be a date field:

PUT http://$SERVER/api/datasets/$id/citationdate?key=$apiKey

Restores the default logic of the field type to be used as the citation date. Same as PUT with :publicationDatebody:

DELETE http://$SERVER/api/datasets/$id/citationdate?key=$apiKey

On Wed, Mar 7, 2018 at 3:12 PM, Meyer, Peter Adrian <me...@hkl.hms.harvard.edu> wrote:

Hi Jonathan,

This is sounding very similar to something I've encountered while working on moving previously published datasets into Dataverse.  I've been addressing this by changing the respective `createdate` and `publicationdate` entries in the `dvobect` table (in postgresql), and reindexing (which may not be necessary, but seems unlikely to hurt).

I'd recommend being careful (and making sure you have database backups) beforehand if you decide to go this route.

Best,
Pete

On Wednesday, March 7, 2018 at 3:03:15 PM UTC-5, Jonathan Bohan wrote:

--

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-community@googlegroups.com.