--
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+unsubscribe...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/f887b9e1-8bd8-4468-abb4-e61b1b662136%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
A new feature called "File Replace" was recently developed in https://github.com/IQSS/dataverse/issues/2290 and will ship with the next version of Dataverse, which we expect to be 4.6.1. For now, you can read about it at https://github.com/IQSS/dataverse/blob/f0f5aea31b5020fcfe0ead5383fbd9211f466c31/doc/sphinx-guides/source/user/dataset-management.rst#replace-filesYou're right about the existing workflow or workaround for replacing files until 4.6.1 is released.I hope this helps!Phil
On Thu, Feb 16, 2017 at 4:15 AM, Anders Conrad <a...@kb.dk> wrote:
Hi,
In our testing of Dataverse, we have reached to the use case of redpositing new versions of a data file that has already been deposited and published.
It would seem that versioning of files is not supported? We understand that the workflow would have to be: 1. delete existing version of file, 2. deposit new version of file, 3. publish.
Is that correct?
I am not an expert in REST API's, but this could maybe become a use case for a future Native API file upload?
By the way, we will be at IDCC next week, hope to meet some of you Dataverse folks there!
Cheers,
Anders
--
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/f887b9e1-8bd8-4468-abb4-e61b1b662136%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Phil, many thanks, you always seem to have the features we think of, ready in your sleeve... :-)
The File Replace feature seems to be spot on. I hope it will also be covered by the API.
Thank you!
Anders
Den torsdag den 16. februar 2017 kl. 13.27.36 UTC+1 skrev Philip Durbin:
A new feature called "File Replace" was recently developed in https://github.com/IQSS/dataverse/issues/2290 and will ship with the next version of Dataverse, which we expect to be 4.6.1. For now, you can read about it at https://github.com/IQSS/dataverse/blob/f0f5aea31b5020fcfe0ead5383fbd9211f466c31/doc/sphinx-guides/source/user/dataset-management.rst#replace-filesYou're right about the existing workflow or workaround for replacing files until 4.6.1 is released.I hope this helps!Phil
On Thu, Feb 16, 2017 at 4:15 AM, Anders Conrad <a...@kb.dk> wrote:
Hi,
In our testing of Dataverse, we have reached to the use case of redpositing new versions of a data file that has already been deposited and published.
It would seem that versioning of files is not supported? We understand that the workflow would have to be: 1. delete existing version of file, 2. deposit new version of file, 3. publish.
Is that correct?
I am not an expert in REST API's, but this could maybe become a use case for a future Native API file upload?
By the way, we will be at IDCC next week, hope to meet some of you Dataverse folks there!
Cheers,
Anders
--
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+unsubscribe...@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/f887b9e1-8bd8-4468-abb4-e61b1b662136%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-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/decde675-55a4-4035-9581-6d934e877c55%40googlegroups.com.
Absolutely the upcoming file replace feature is included in the API. We haven't tagged 4.6.1 yet but you can read the API docs at https://github.com/IQSS/dataverse/blob/019bbb3841060f4bde88745a8cda2eb3258361a5/doc/sphinx-guides/source/api/native-api.rst#files
On Fri, Feb 17, 2017 at 5:58 AM, Anders Conrad <a...@kb.dk> wrote:
Phil, many thanks, you always seem to have the features we think of, ready in your sleeve... :-)
The File Replace feature seems to be spot on. I hope it will also be covered by the API.
Thank you!
Anders
Den torsdag den 16. februar 2017 kl. 13.27.36 UTC+1 skrev Philip Durbin:
A new feature called "File Replace" was recently developed in https://github.com/IQSS/dataverse/issues/2290 and will ship with the next version of Dataverse, which we expect to be 4.6.1. For now, you can read about it at https://github.com/IQSS/dataverse/blob/f0f5aea31b5020fcfe0ead5383fbd9211f466c31/doc/sphinx-guides/source/user/dataset-management.rst#replace-filesYou're right about the existing workflow or workaround for replacing files until 4.6.1 is released.I hope this helps!Phil
On Thu, Feb 16, 2017 at 4:15 AM, Anders Conrad <a...@kb.dk> wrote:
Hi,
In our testing of Dataverse, we have reached to the use case of redpositing new versions of a data file that has already been deposited and published.
It would seem that versioning of files is not supported? We understand that the workflow would have to be: 1. delete existing version of file, 2. deposit new version of file, 3. publish.
Is that correct?
I am not an expert in REST API's, but this could maybe become a use case for a future Native API file upload?
By the way, we will be at IDCC next week, hope to meet some of you Dataverse folks there!
Cheers,
Anders
--
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/f887b9e1-8bd8-4468-abb4-e61b1b662136%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/decde675-55a4-4035-9581-6d934e877c55%40googlegroups.com.
Philipp
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@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/f887b9e1-8bd8-4468-abb4-e61b1b662136%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+unsubscribe...@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/decde675-55a4-4035-9581-6d934e877c55%40googlegroups.com.
--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-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/e6551dfb-c6e1-4541-828c-3af33ef7089b%40googlegroups.com.