a survey sounds like a good idea to me the easier it is to send in responses the more answers you’ll get
in a survey monkey type survey you’d have to give instructions on every single question how to find the answer; eg: dspace version - look under into HTML headers database-type: look into dspace.cfg OS version — which command to run eg: "uname -a" in Linux the simpler/fewer the questions the more answers alternatively: write a cli script - put it into /dspace/bin make ant update run the script and echo instructions how to mail results to a collection email make sure output is easy to parse so results can be added to a spreadsheet / accumulated / … that of cause is a lot more work and may not be worth the extra effort compared to the survey monkey approach I also counsel against exposing the data publicly Monika — Monika Mevenkamp Digital Repository Infrastructure Developer Princeton University Phone: 609-258-4161 Skype: mo-meven > On Nov 16, 2016, at 10:07 AM, Monika C. Mevenkamp > <moni...@exchange.princeton.edu> wrote: > > a survey sounds like a good idea to me > the easier it is to send in responses the more answers you’ll get > > in a survey monkey type survey you’d have to give instructions on every > single question how to find the answer; > eg: dspace version - look under into HTML headers > database-type: look into dspace.cfg > OS version — which command to run eg: "uname -a" in Linux > > alternatively: write a cli script - put it into /dspace/bin > make ant update run the script and echo instructions how to mail results to a > collection email > make sure output is easy to parse so results can be added to a spreadsheet / > accumulated / … > > I would also counsel against exposing the data publicly > > Monika > > > — > Monika Mevenkamp > Digital Repository Infrastructure Developer > Princeton University > Phone: 609-258-4161 > Skype: mo-meven > >> On Nov 16, 2016, at 8:15 AM, Alan Orth <alan.o...@gmail.com> wrote: >> >> I had forgotten about that registry, helix! Our repository is >> certainly very out of date there (name, version, link, etc). >> >> Anyways, my proposal was simply to circulate a survey that people >> could answer, very low tech. :) >> >> Regards, >> >> On Wed, Nov 16, 2016 at 1:53 PM, emilio lorenzo <elore...@arvo.es> wrote: >>> >>> El 16/11/2016 a las 12:23, helix84 escribió: >>>> >>>> >>>> That part is already available. >>>> >>>>> vote 1- for second part.... Not very sure about harvesting or exposing >>>>> versions and modules across system interface. Too many advantages for >>>>> networks hooligans and hackers.. >>>> >>>> Well, first, those parts are already there and publicly exposed >>>> (xmlui, jspui, oai, rest, rdf), so the right thing to do is to make >>>> them resilient against attacks, not to pretend they're not exposed. >>>> Second, there must be an option for the administrator not to expose >>>> this information (not all repositories are production and public >>>> installations). >>> >>> Well, I understood Alan´s proposal as exposing the software stack of the >>> Dspace installations, not only Dspace interfaces.... and telling the world >>> that an installation has a operating system or a database some years old is >>> quite sensible (IMHO), although a competent hacker could figure out a lot of >>> things about an installation without our help :-) >>> >>> and of course our first priority has to be >>>> >>>> make them resilient against attacks >>> >>> But not every installation has the time or resources to keep its >>> installation updated and safe. That is the reality... >>> Regards >>> Emilio >>> >>> >>> >>>> And finally, this is supposed to actually help security. You'll be >>>> able to register your instance (just once) along with your email >>>> address and then get a custom-tailored notification that your >>>> particular installation is affected by a security bug because you're >>>> using version X.Y with module Z. >>>> >>>> >>>> Regards, >>>> ~~helix84 >>>> >>>> Compulsory reading: DSpace Mailing List Etiquette >>>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "DSpace Technical Support" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to dspace-tech+unsubscr...@googlegroups.com. >>> To post to this group, send email to dspace-tech@googlegroups.com. >>> Visit this group at https://groups.google.com/group/dspace-tech. >>> For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> Alan Orth >> alan.o...@gmail.com >> https://englishbulgaria.net >> https://alaninkenya.org >> https://mjanja.ch >> "In heaven all the interesting people are missing." ―Friedrich Nietzsche >> GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to dspace-tech+unsubscr...@googlegroups.com. >> To post to this group, send email to dspace-tech@googlegroups.com. >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. > ________________ Monika Mevenkamp mo.me...@gmail.com http://mo-meven.tumblr.com/ http://mcmprogramming.com/mo.meven/ -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
