Closed kirbykat closed 5 years ago
We already curate the data in a GitHub repository - https://github.com/D-PLACE/dplace-data - so let's just have people use the notification mechanisms available there. E.g. they could subscribe to release events and get notifications whenever something is released - thus triggering an update of the webapp.
Btw.: I also think we urgently need a test instance of the webapp. It's simply bad practice to upload unspecified states of the data to the public web app at any time. Having people report downloads no longer working is already the good case, in the worst case they'd perform their analyses with a different set of data after a new download and get confused.
@xrotwang I honestly think using GitHub will exclude a huge number of people who are not Git savvy. I am still figuring out how to post issues etc. I receive quite a lot of inquiries via the D-PLACE email from people less quantitative than the folks at MPI-SHH.
@kirbykat I can imagine that to be the case. But maintaining infrastructure of the kind you describe - email addresses, email lists, including documentation - is just a big pain. I really think we have to use the pull of attractive datasets like D-PLACE to get people into using new (and more appropriate) tools.
@xrotwang Well, I will volunteer to maintain a list, and if at some point it becomes unmanageable I will send the list an email with detailed instructions on how to track database changes on github. How does that sound? I figure the more "types" of users we can reach, the better.
Could be a new item in the drop down menu 'Subscribe' under 'Contact'?
I guess we'd have to set up a listserv for this. For the immediate future, is it easy to create a link that sends an email to the D-PLACE email address, with an auto-generated a subject line like "D-PLACE - sign up for updates"?