Re: [jats-list] a new JATS wiki

["Beck, Jeff (NIH/NLM/NCBI) [E]" <beck@xxxxxxxxxxxxxxxx>]

The main properties I would be concerned about would be openness,
stability, and perpetuity.

I'm not really worried about logins for authors (although openID would be
nice when it is available), ugly URLs, or WYSIWYG editing.

We're spreading out pretty well now into a community. We have the standard
at NISO, the non-normative supporting documentation at NLM, and the
discussion list hosted by Mulberry.

Of the two choices, my preference would be for the institution over the
individual. Things will happen, and it might be easier to do a recovery
from an institutional IT department than from an individual site. But that
would be my only concern, and I thank you both for offering to set this up
and host.

Jeff

On 10/19/12 10:05 AM, "Maloney, Christopher (NIH/NLM/NCBI) [C]"
<maloneyc@xxxxxxxxxxxxxxxx> wrote:

>Kudos, Kevin, for such quick action on this idea!
>
>I would also offer that we could host it at jatspan.org.  I do not have a
>preference, but I am willing to host it there, and would also mention
>that I have a little bit of experience, in that I already have a test
>Mediawiki installation set up on that machine, at
>http://chrisbaloney.com/wiki (pay no attention to that domain name!)
>It's a LAMP app, and pretty easy to install and administer.
>
>In response to your bullet points, I see the pros and cons as:
>
>a) ... same
>
>b)  This is a personal site, but I would have no problem with giving a
>few others admin rights to this wiki, or we could move it into the cloud
>so that it wasn't on my personal machine, and collaborate on it there.
>One con to it being a personal site is that it tends to go down whenever
>we have a huge snow- or wind-storm on the east coast USA.
>
>c)  We wouldn't depend on any IT service for upgrades / changes.  Of
>course, that also means we wouldn't benefit from their time and
>expertise, either.  And if an institution manages it, as opposed to a
>group of volunteers, then maybe things would get done in a more timely
>way.  I am pretty busy these days, and we can't be sure of others jumping
>in to help with admin tasks, so this might be the most important
>consideration.  On the other hand, again, as I mentioned, Mediawiki, from
>what I've seen so far, is pretty easy to run.
>
>d) ... same
>
>e)  The URL is very pretty!  (As an aside, when you search for "jatspack
>and jatspan" in Google, it asks, "Did you mean 'jetpack and japan'?".
>How cool is that?)
>
>Of course, if you could get University of Michigan to serve a cleaner
>domain name, then there might be better options.  I'd like something more
>generic than "jatswiki", because presumably the same site could have
>other tools, eventually.  (After inquiring once, I've been getting spam
>from the guy who owns "jats.org" for a while now, but so far his price is
>still a too steep!)
>
>If University of Michigan were to host a new clean domain, and put a wiki
>up there, would they also be able to host other tools / subsites / etc.
>at the same domain?
>
>f)  It's not related to the choice of hosting solution, but I like
>Mediawiki.  The Wikimedia folks are hard at work on a wysiwyg editor, and
>hopefully will have something by early next year.
>
>
>Thanks again for getting the ball rolling on this.
>
>________________________________________
>From: Kevin Hawkins [kevin.s.hawkins@xxxxxxxxxxxxxxxxxx]
>Sent: Wednesday, October 17, 2012 6:28 PM
>To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
>Subject: [jats-list] a new JATS wiki
>
>Thanks to everyone at this year's JATS-Con: great papers, great
>organizing, and great audience questions.  I would be joining you
>tonight for the "after party" if I weren't sitting at the airport on my
>way home.
>
>We talked a bit about providing ways for members of the community to
>share JATS customizations, Schematron rules, tools, and more without
>leaving the burden of maintaining such a resource on the folks at the
>NLM.  One idea was to do this as a wiki in order to avoid needing to
>have a webmaster who responds to people's requests to add resources,
>which lowers the barrier to participation (people just make a quick
>edit), and which allows the collection of resources to grow organically
>instead of in a top-down fashion.
>
>If others are interested, I could set up a MediaWiki 1.13.1 instance
>hosted at the University of Michigan.  Here's an example of another such
>site:
>
>http://webservices.itcs.umich.edu/mediawiki/ml2sig/
>
>The new JATS wiki could be readable by everyone and editable only by
>those who create a guest login at the University of Michigan.
>
>Some advantages to this wiki setup at U-M:
>
>a) By making people create a guest user account, we outsource the
>problem of filtering spambots to U-M's login creation process instead of
>appointing someone to look after the site for malicious account creation
>and posting of gibberish on pages.  (If you doubt that this happens, ask
>me about why the TEI wiki changed to requiring approval of new users by
>one of the moderator.)
>
>b) By hosting at U-M rather than on someone's personal website, we
>ensure an institutional home for the content.  While I may not be at U-M
>forever, the institution, through http://www.lib.umich.edu/mpach , will
>be committed to JATS for the foreseeable future.
>
>Some disadvantages:
>
>c) It's hosted by the university's central IT services, so I am
>dependent on them to upgrade MediaWiki and add extensions depending on
>their schedule and desires.
>
>d) There is no timetable that I'm aware of for implementation of
>Shibboleth or OpenID, so people will need to create a guest user account
>to use the system.  It's easy but a hassle for everyone to have yet one
>more account.
>
>e) The URL is kind of ugly.  However, I can probably get
>jatswiki.publishing.umich.edu or register something new (jatswiki.org?)
>instead.
>
>f) It's MediaWiki.  There's no WYSIWYG editor.  We all know that people
>don't like to write in markup.
>
>--Kevin