Discussion:
Make Wikisource "book-based"
(too old to reply)
Andrea Zanni
2016-11-16 11:23:00 UTC
Permalink
Raw Message
I made a draft on a proposal here:
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wikisource#Make_Wikisource_.22book-based.22

Please edit, it's a draft and I think it's a problem many of us know from a
long time.

The idea is that, if we had a system for MediaWiki to know what a book is,
we could
* better metadata management system, thus a better integration with Wikidata
* we could develop better tools, for example create automatic Indexes and
navigation templates, which would maybe enable us to "import" EPUBs
directly on Wikisource
* have a better workflow, making it easier to new users to use us
* have even better statistics and analytics: which are the *books* (not the
pages!) which are read o WIkisource?

etc.

IMHO, the Community Wishlist is a great opportunity to push for a systemic
development of Wikisource: I'm convinced we don't need little tools here
and there, but a systematic overview of what Wikisource framework,
workflows and software.
I'm open to discuss the merging of different proposals in the Wishlist.

Aubrey
David Cuenca Tudela
2016-11-16 12:29:25 UTC
Permalink
Raw Message
I like the idea of finishing the development of BookManager2, it is a pity
that the code was not reviewed
https://www.mediawiki.org/wiki/Extension:BookManagerv2

Cheers,
Micru
Post by Andrea Zanni
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_
Survey/Categories/Wikisource#Make_Wikisource_.22book-based.22
Please edit, it's a draft and I think it's a problem many of us know from
a long time.
The idea is that, if we had a system for MediaWiki to know what a book is,
we could
* better metadata management system, thus a better integration with Wikidata
* we could develop better tools, for example create automatic Indexes and
navigation templates, which would maybe enable us to "import" EPUBs
directly on Wikisource
* have a better workflow, making it easier to new users to use us
* have even better statistics and analytics: which are the *books* (not
the pages!) which are read o WIkisource?
etc.
IMHO, the Community Wishlist is a great opportunity to push for a systemic
development of Wikisource: I'm convinced we don't need little tools here
and there, but a systematic overview of what Wikisource framework,
workflows and software.
I'm open to discuss the merging of different proposals in the Wishlist.
Aubrey
_______________________________________________
Wikisource-l mailing list
https://lists.wikimedia.org/mailman/listinfo/wikisource-l
--
Etiamsi omnes, ego non
Alex Brollo
2016-11-16 15:55:26 UTC
Permalink
Raw Message
Please don't underestimate the critical point of editing interface and
editing tools (even if *small*...), proofreading is the core of wikisource
work and it is presently the bottle neck - any minor success about
proofreading comfort, speed & precision is highly valuable and really
effective.


Alex
Post by David Cuenca Tudela
I like the idea of finishing the development of BookManager2, it is a pity
that the code was not reviewed
https://www.mediawiki.org/wiki/Extension:BookManagerv2
Cheers,
Micru
Post by Andrea Zanni
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Surv
ey/Categories/Wikisource#Make_Wikisource_.22book-based.22
Please edit, it's a draft and I think it's a problem many of us know from
a long time.
The idea is that, if we had a system for MediaWiki to know what a book is,
we could
* better metadata management system, thus a better integration with Wikidata
* we could develop better tools, for example create automatic Indexes and
navigation templates, which would maybe enable us to "import" EPUBs
directly on Wikisource
* have a better workflow, making it easier to new users to use us
* have even better statistics and analytics: which are the *books* (not
the pages!) which are read o WIkisource?
etc.
IMHO, the Community Wishlist is a great opportunity to push for a
systemic development of Wikisource: I'm convinced we don't need little
tools here and there, but a systematic overview of what Wikisource
framework, workflows and software.
I'm open to discuss the merging of different proposals in the Wishlist.
Aubrey
_______________________________________________
Wikisource-l mailing list
https://lists.wikimedia.org/mailman/listinfo/wikisource-l
--
Etiamsi omnes, ego non
_______________________________________________
Wikisource-l mailing list
https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Sam Wilson
2016-11-17 05:16:43 UTC
Permalink
Raw Message
This is a good plan, Aubrey. We shouldn't be putting too much effort
into supporting systems or tools that are not *fundamentally* going in
the right direction. Of course, that's easy to say, but it's hard to
know which is what.

So, I'd say for example that storing this metadata in Index pages is not
sensible now that we've got wikidata: work type (e.g. book, journal),
title, language, author, translator, editor, illustrator, school,
publisher, year of publication, place of publication, ISBN, OCLC, LCCN,
ARK, and National Archives identifier.
So let's not build things that further cement the use of Index pages
for that stuff. (I don't mean that anyone has suggested anything
that would..).

I think the *proofreading* side of things is going well and we're
getting better at doing more and at higher quality. There are many
smallish things that we can do that will help in this realm.

But there are two other aspects that I think need a bit of a re-think
(or at least where we need to always keep the bigger picture in mind),
as Aubrey suggests:
1. the "project management" (for want of a better term) of getting a
work into wikisource and shepparding it through the various stages
until it's ready and green and done;
2. making things brilliant for *readers*! things like having
export/download options big and clear, and the same with links to
wikipedias and other language wikisources. And getting feedback
(especially about typos etc.); that should be simpler.
I don't really have any answers yet (am still reading through lots of
the stuff about https://meta.wikimedia.org/wiki/Book_management ) but
perhaps a narrowing down of proofreadpage to focus on proofreading
methodology only, and a new bookmanger extension that can give us lots
of the other stuff.

Am I sort of on track with you Aubrey (and others)?

—sam

PS The proposal phase of the Wishlist Survey finishes in about four
days, so come and edit proposals to make em great. :-)
Post by Andrea Zanni
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wikisource#Make_Wikisource_.22book-based.22
Please edit, it's a draft and I think it's a problem many of us know
from a long time.
The idea is that, if we had a system for MediaWiki to know what a book is,
we could
* better metadata management system, thus a better integration with Wikidata
* we could develop better tools, for example create automatic Indexes
and navigation templates, which would maybe enable us to "import"
EPUBs directly on Wikisource
* have a better workflow, making it easier to new users to use us
* have even better statistics and analytics: which are the *books*
(not the pages!) which are read o WIkisource?
etc.
IMHO, the Community Wishlist is a great opportunity to push for a
systemic development of Wikisource: I'm convinced we don't need little
tools here and there, but a systematic overview of what Wikisource
framework, workflows and software.
I'm open to discuss the merging of different proposals in the
Wishlist.
Aubrey
_________________________________________________
Wikisource-l mailing list
https://lists.wikimedia.org/mailman/listinfo/wikisource-l
Loading...