Skip to content
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

What to do with an installation we find that isn't on the map? #145

Open
IlariaBelvedere opened this issue Jun 13, 2022 · 13 comments
Open
Labels
question Further information is requested

Comments

@IlariaBelvedere
Copy link

Hello,

checking on re3data I found a few Dataverse installations that are not listed on the map (as @pdurbin said, being on the map isn't mandatory and some of them could be in their demo phase).
What do we do with them? Could it be interesting to add a new sheet on the file about installations but specifying they are not on the map (for several reasons which maybe it is not right to explicitate)?
Give this matter an hand, please :)

@shlake
Copy link
Contributor

shlake commented Jun 13, 2022

@IlariaBelvedere
Not sure about all of the RE3Data Dataverse entries you found, but this one is actually a sub dataverse (collection) on Harvard’s
https://www.re3data.org/repository/r3d100010713

This one is as well:
https://www.re3data.org/repository/r3d100010949

They are not separate installations.

@IlariaBelvedere
Copy link
Author

Hello @shlake,
thank your for your reply :) Yes, I noticed that some of them - the majority among those not mentioned in the map - are sub Dataverse, so I did not include them in this cases. But there are other ones which seem separate installations, like: https://rdm.aau.edu.et/

https://adattar.unideb.hu/ (beta version)

https://dataverse.rhi.hi.is/

So I tried to ask about them on the chat, and @pdurbin suggested to ask the community here.
What do you think about it?
Thanks,

Ilaria

@IQSS IQSS deleted a comment from IlariaBelvedere Jul 6, 2022
@jggautier
Copy link
Contributor

(The previous comment was somehow duplicated so I delete the second one.)

Shouldn't we try to contact each installation to see if they'd like to be added?

@jggautier jggautier added the question Further information is requested label Jul 6, 2022
@IlariaBelvedere
Copy link
Author

Hello, thank you, my computer decided to write it twice ahah :)
Regarding the installations which are not on the map: it could be an idea to do as you suggested, maybe it is something to be done by one of the people who are working on Dataverse or do you think that I could send these mails?

@jggautier
Copy link
Contributor

I'd be fine with you or anyone else in the Dataverse community sending the emails :) If you can that would be great!

@pdurbin
Copy link
Member

pdurbin commented Jul 13, 2022

@IlariaBelvedere yes! Please feel free to email folks. Do you have Marion Wittenberg's address? She recently posted about a new installation here: https://groups.google.com/g/dataverse-community/c/7cUyLesUk-Q/m/7XM3UcirHAAJ

@IlariaBelvedere
Copy link
Author

IlariaBelvedere commented Jul 14, 2022 via email

@pdurbin
Copy link
Member

pdurbin commented Jul 14, 2022

@IlariaBelvedere yep, I just emailed her and cc'd you. Thanks!

@pdurbin
Copy link
Member

pdurbin commented Aug 25, 2022

@IlariaBelvedere your outreach efforts are working! Thanks! Check out this issue:

@jggautier
Copy link
Contributor

jggautier commented Sep 7, 2022

I mentioned contacting these repositories and meant that this could be done instead of keeping a list of installations that aren't on the map. I'm curious why we'd want to keep a list of Dataverse installations that aren't on the map? Here are some reasons I can think of:

  • So that we can consider these installations when we review the different types of Dataverse installations, such as for the "installation archetype" work that was done a while back, which can help inform what kinds of use-cases the Dataverse community supports
  • So that we keep a record of when the installation was last contacted and who contacted them, to avoid contacting them too often but to also know when to ask again if they'd like to be added to the map

Are there other reasons for keeping a list of Dataverse installations that aren't on the map?

@IlariaBelvedere
Copy link
Author

Hello,

Well, I think those are both good reasons. Another reason I think It could be useful It Is for studying reason, in the sense that knowing how many installations are out there (even those not on the map) can provide information and feedback about Dataverse spread and so on.
I have recently contacted the ones not on the map (at least the ones I found) and a few of them answered and asked to be added. Another interesting thing referred to this Is to create a space in the site/map where It could be displayed the work behind every installations (plugin, integrations ecc.). We were talking about this on the chat, and I should probably open another issue about this.

@pdurbin
Copy link
Member

pdurbin commented Sep 15, 2022

Another one! Thanks @IlariaBelvedere for reaching out to them! And thanks @shlake for adding it. 🎉

@jggautier I think of it as a sales funnel, I guess. Even though Dataverse is free as in beer. Or maybe conversion is the right term? Conversion rates? You want people to buy something. Or in our case, you want them to opt in to being on the map, to join our community. So it makes sense to check in with installations. How's it going? Do you need anything? Did we tell you you can put your installation on a map? That sort of thing. I guess this is basically your second bullet but I don't think we actually track when we last contacted anyone.

@jggautier
Copy link
Contributor

jggautier commented Sep 15, 2022

I forgot that on the spreadsheet you also added a "skip" column to record info about installations that didn't want to be on the map right away. So maybe we could add installation info to the spreadsheet and in the skip column indicate with a "yes" or "true" or something else that the installation shouldn't be added to the map. The code seems to be checking for any value in that column.

If one of the goals is to avoid multiple people contacting installations too often, so they're not bothered, I think some indication of the last time they were contacted would be helpful. Maybe a last_contacted_date column could be added for that info, and any date entered can be removed once the installation is added to the map.

I like the analogy of conversation rates!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants