DVN internal instance

42 views
Skip to first unread message

Rebeca Barros

unread,
Aug 17, 2017, 12:54:12 PM8/17/17
to Dataverse Users Community

I intend to install a DVN instance in my work in order to organize and catalogue our datasets. However, this instance is has to be only local (with no network access available) because we are dealing with sensitive data. My initial thoughts is that we can create another instance (available for external access) and then import metadata from the first instance only for the datasets that we can share. Is there a simple way to do that?


Can I use the API to dump all my metadata info (in dataverse ou dataset level) in a way that I can import this in a new dataverse instance? 


I was reading about harvesting but since our first instance will be not available for internet protocols, I cannot use that. Either way, here is a valid doubt: There is not a way to (when harvesting) show the metadata in the harvesting client? I saw some harvesting files in Harvard Dataverse but once we click in the file, it leads you direct for the original site (I get the that is the idea) but I wonder if one cannot view the metadata info in the client prior to be leading to the original site.

Gautier, Julian

unread,
Aug 17, 2017, 1:26:40 PM8/17/17
to dataverse...@googlegroups.com
Hi Rebeca,

I'd like to ask about the second very interesting point you raised:

Either way, here is a valid doubt: There is not a way to (when harvesting) show the metadata in the harvesting client? I saw some harvesting files in Harvard Dataverse but once we click in the file, it leads you direct for the original site (I get that is the idea) but I wonder if one cannot view the metadata info in the client prior to be leading to the original site.

Could you write some more about why a viewer would want to view the metadata in the client, in your example Harvard Dataverse, before going to the original site? I have some ideas about why (and it's been brought up by others), but I'm interested in your use-cases.

Thanks!

--
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/17329f2b-96ce-476f-a5be-e758aa310f9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Julian Gautier
Product Research Specialist, IQSS

Rebeca Barros

unread,
Aug 18, 2017, 11:40:50 AM8/18/17
to Dataverse Users Community

Hi, Julian.

 

For my scenario, it would be helpful because I would have one instance only for metadata search/visualization. i.e.:

  • Instance 1 - Storage for metadata + real data;
  • Instance 2 - Programmed Harvesting metadata from Instance 1 and interface for search and visualize all metadata related.

But, thinking of a final user view, there are some harvesting servers where the metadata visualization is not so easy like the Dataverse interface or where is not so simple to find the export metadata option (to name a few). Anyway, it would be simpler for a user to search within the full metadata and find out if it is what he expects, than to have to go to another external site to find this out.


On Thursday, August 17, 2017 at 2:26:40 PM UTC-3, Gautier, Julian wrote:
Hi Rebeca,

I'd like to ask about the second very interesting point you raised:

Either way, here is a valid doubt: There is not a way to (when harvesting) show the metadata in the harvesting client? I saw some harvesting files in Harvard Dataverse but once we click in the file, it leads you direct for the original site (I get that is the idea) but I wonder if one cannot view the metadata info in the client prior to be leading to the original site.

Could you write some more about why a viewer would want to view the metadata in the client, in your example Harvard Dataverse, before going to the original site? I have some ideas about why (and it's been brought up by others), but I'm interested in your use-cases.

Thanks!
On Thu, Aug 17, 2017 at 12:54 PM, Rebeca Barros <bk.b...@gmail.com> wrote:

I intend to install a DVN instance in my work in order to organize and catalogue our datasets. However, this instance is has to be only local (with no network access available) because we are dealing with sensitive data. My initial thoughts is that we can create another instance (available for external access) and then import metadata from the first instance only for the datasets that we can share. Is there a simple way to do that?


Can I use the API to dump all my metadata info (in dataverse ou dataset level) in a way that I can import this in a new dataverse instance? 


I was reading about harvesting but since our first instance will be not available for internet protocols, I cannot use that. Either way, here is a valid doubt: There is not a way to (when harvesting) show the metadata in the harvesting client? I saw some harvesting files in Harvard Dataverse but once we click in the file, it leads you direct for the original site (I get the that is the idea) but I wonder if one cannot view the metadata info in the client prior to be leading to the original site.

--
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.
Reply all
Reply to author
Forward
0 new messages