-
Notifications
You must be signed in to change notification settings - Fork 2
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
Possibly change who to contact for support #137
Comments
Hi @jmjamison. I apologize for adding to the confusion in that email you sent to Dataverse support. When I replied to your email to Dataverse support, I linked to the section in the Dataverse User Guides about Geoconnect without really understanding the instructions. @pdurbin did some digging and it looks like after the step you followed in the Geoconnect readme for contacting Dataverse support, someone from Dataverse support should work with you to add your Dataverse to a "Registered Dataverses" list. I have those instructions and I'll email you in RT again to get your installations added. I hope that sheds some light on the situation and helps us figure out how to make sure we provide the right support. |
Sorry to confuse things more from my side but I heard from Dataverse support that they couldn't help me with this.
Jamie
UCLA Library Data Science Center
[email protected]
http://orcid.org/0000-0002-5116-5724
310-825-0716
…-----------------------------------------------------------------------------
"An asset is only an asset if you can access it ..."
AMIA (Association of Moving Image Archivists)/Digital Asset Symposium 2008
________________________________________
From: Julian Gautier <[email protected]>
Sent: Tuesday, July 23, 2019 12:16:25 PM
To: IQSS/geoconnect
Cc: Jamison, Jamie; Mention
Subject: Re: [IQSS/geoconnect] Possibly change who to contact for support (#137)
Hi @jmjamison<https://github.com/jmjamison>. I apologize for adding to the confusion in that email you sent to Dataverse support. I linked to the section in the user guides about Geoconnect without really understanding the instructions.
@pdurbin<https://github.com/pdurbin> did some digging and it looks like after the step you followed in the Geoconnect readme<https://github.com/IQSS/geoconnect/blob/master/README.md> for contacting Dataverse support, someone from Dataverse support should work with you to add your Dataverse to a "Registered Dataverses" list.
I have those instructions and I'll email you in RT again to get your installations added.
I hope that sheds some light on the situation and helps us figure out how to make sure we provide the right support.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#137?email_source=notifications&email_token=AABYCOINYHQD3SH4AZ2URODQA5KITA5CNFSM4IF3N7D2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2UEW6Y#issuecomment-514345851>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AABYCONYZKMB6JBF5WH7JRTQA5KITANCNFSM4IF3N7DQ>.
|
@jmjamison no problem. I gather from https://groups.google.com/d/msg/dataverse-community/Itazpn2Otmk/d0RfpGXZEAAJ that you aren't getting the error you originally reported: That is, it seems to be working now. Thank you to @jggautier for adding your Dataverse installation to Harvard's installation of Geoconnect. Any more thoughts on this issue? Do you have any interest in fixing up the README? 😄 If you're not aware, GitHub has an browser-based editor you could use. 😄 |
The item:
Dataverse support is unable to help with this, suggested I contact Phil and/or Worldmap. Possibly the email should be for worldmap support?
The text was updated successfully, but these errors were encountered: