Hi everyone,
As you may know, you can include Sitelinks (also known as interwiki links
or interlanguage links) that go from individual Items in Wikidata to pages
on other Wikimedia sites including Wikisource
<https://en.wikipedia.org/wiki/Wikisource>. Until now, it was not possible
to manage the interwiki links to/from multilingual Wikisource on Wikidata.
This was due to the unusual technical setup of multilingual Wikisource as
well as the fact that we can only link to one page for a topic on any given
wiki (multilingual Wikisource can theoretically have several pages covering
the same topic in different languages though this is very rare).
We resolved the technical constraint and starting today you can connect
pages on multilingual Wikisource with the other language-specific versions
of Wikisource so these interwiki links don't have to be maintained in the
wikitext anymore. After adding a sitelink, the sitelink appears on the Item
page (in the Sitelinks section) with language code mul. The restriction of
only being able to link to one page on multilingual Wikisource per Item
stays in place and was considered acceptable based on feedback by the
Wikisource community.
This feature was requested by users from the Wikisource community. We hope
that it can give them more access to Wikidata and the freedom to add
multiple links to different Items.
If you encounter any issues or want to provide feedback, feel free to use this
Phabricator ticket <https://phabricator.wikimedia.org/T138332>.
Cheers,
--
Mohammed Sadat
*Community Communications Manager for Wikidata/Wikibase*
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
I was just having a look at Wikisources' logos on Wikidata, and there
are quite a few that don't have one yet: https://w.wiki/x6V
I've tried to add as many as I can find, but if anyone happens to know
the correct SVGs for the missing ones, it'd be great to complete the
list. (Note that it's the 'logo image' not the 'image' property.)
Thanks,
Sam.
Hi everyone,
I hope you're all well.
I'm sorry I didn't post for a long time, so here is some news (not
exhaustive, feel free to answer with your own news):
- first and foremost, the Wishlist is back and it starts next Monday:
https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2021 let's gather
our best idea again this year!
- as usual, if you did something related to Wikisource, don't hesitate to
add it on
https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/2020_Report
(especially in this strange year, if you did some online activities, I'd
love to hear about it!)
- an "Affiliates Data Survey" run by mail and by the Foundation is coming;
I'll get in touch with you soon, if you are interested to share your
experience with the Wikisource community, feel free to contact me in
private.
- here is a very interesting and promising project to improve
Wikidata-Wikisource Integration :
https://meta.wikimedia.org/wiki/Wikicite/grant/Improving_Wikidata-Wikisourc…
Finally, as an official user group, the Foundation requires 2 primary
contacts, for now (and since a long time), I'm the only contact, which is
problematic.
Also, for me, I'd be happy to have some help ;)
Are there any candidates?
Cheers,
For the WCUG,
Nicolas
Last week, we had a Indic Wikisource Proofreadthon 2020 event. see
here for full details
https://meta.wikimedia.org/wiki/Indic_Wikisource_Proofreadthon_2020
Though I did not participate in this event, (feels sad for this. Life
is too messy nowadays), I thought to build a small tool to give report
on any wikipedia user’s contribution on a given wikisite for a given
date range.
It may help to calculate, measure, decide on the contributions for
such competitions.
Mediawiki has a good API to fetch user contributions.
https://www.mediawiki.org/wiki/API:Usercontribs
Get all edits by a user.
https://www.mediawiki.org/wiki/Special:MyLanguage/API:Usercontribs
For my wonder, there was a sample python code on the same page.
The code gave only 500 results. I wrote a loop to get the data batch
by batch till all the data is received.
Published the tool here –
https://github.com/tshrinivasan/wiki_user_contributions_report
How to run?
python3 get_user_contributions.py <language> <wikisite> <username>
<start_date> <end_date>
This will give the data as a CSV file. Used a csv-to-html converter
utility to convert this to a web page with all the data in a sortable
table.
For my wonder, my friend Dinesh Karthik, converted this as a nice web
application with flask, dash and hosted in heroku.
https://wiki-user-contributions.herokuapp.com/
Source : https://github.com/Dineshkarthik/wiki-user-contributions
Thanks to Info-farmer for providing the idea, Bartosz Dziewoński on
wikipedia mailing list for answering all my questions, Dinesh for
making a web application quickly.
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
is a good place to ask any tech questions regarding wikipedia.
Thanks to all wikisource contributors for the event and in general.
--
Regards,
T.Shrinivasan
My Life with GNU/Linux : http://goinggnu.wordpress.com
Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com
Get Free Tamil Ebooks for Android, iOS, Kindle, Computer :
http://FreeTamilEbooks.com
Hi everyone!
This week we (the Community Tech
<https://meta.wikimedia.org/wiki/Community_Tech> team, of which I'm a
part) are going to roll out phab:T256392
<https://phabricator.wikimedia.org/T256392> which will move the
functionality of the MediaWiki:Gadget-WSexport.js
<https://en.wikisource.org/wiki/MediaWiki:Gadget-WSexport.js> gadget
into the Wikisource extension
<https://www.mediawiki.org/wiki/Extension:Wikisource>. There are a bunch
of Wikisources that have this gadget, and others that provide similar
links via common.js or other scripts, and I and the other CommTech
engineers will be scooting around cleaning up scripts wherever we can,
but if anyone notices anything amiss please let me know!
Any existing translations that I could find have been copied into the
extension, but there are still a few languages missing translations.
Have a look at
translatewiki:Special:MessageGroupStats?group=ext-wikisource
<https://translatewiki.net/w/i.php?title=Special:MessageGroupStats&language=…>
and translate any that you know.
This is a smallish change and is a precursor to the larger change that
hopefully will come soon of enabling a 'download' button at the top of
works (as some Wikisources already do). See phab:T266262
<https://phabricator.wikimedia.org/T266262> for more about that.
Thanks,
Sam.
PS The 'Choose other format' link is still annoying in that it doesn't
prefill the title. This will be fixed soon, in T256345
<https://phabricator.wikimedia.org/T256345>.
In 2005, at the first Wikimania in Frankfurt, Germany,
Magnus Manske asked me if I could open up my Scandinavian
book scanning website Project Runeberg to German and
other languages, or release the software as open source.
I refused, as my software is just a rapid prototype that
would need to be rewritten from scratch anyway. But I
said that Wikisource could be used for this purpose. At
the time, Wikisource was only a wiki for e-text. As a
proof of concept, I put up "Meyers Blitz-Lexikon" as
the first book with scanned page images in Wikisource,
https://de.wikisource.org/wiki/Seite:LA2-Blitz-0005.jpg
and soon after the "New Student's Reference Work",
https://en.wikisource.org/wiki/Page:LA2-NSRW-1-0013.jpg
This was the basic inspiration for the "Proofread Page"
extension, now used in Wikisource.
In 2010-2011 I tried to use Wikisource, but I thought
this extension was too hard to work with. From scanner
to finished presentation, Wikisource was so much slower
to work with than my own system. By primary gripes are:
It is too hard to upload PDF files to Commons, it's too
hard to create the Index page, each page is not created
immediately (making the raw OCR text searchable), and
pages hidden in the Page: namespace are not always
indexed by search engines. Unfortunately, the system
hasn't improved much in the last decade.
(My criticism of my own website's system is a lot
harsher, but hits different targets.)
There is also a difference in how we view copyright,
as my own website can cut corners and scan some books
that are "most likely" out of copyright, which is
something Wikimedia's user communities never accept.
In 2012, I thought the time had finally come to rewrite
my software, but I failed to organize a project around
this, and instead I continued to use the existing system,
just adding volume. Indeed, Project Runeberg has grown
from 0.75 million book pages in 2012 to 3.1 million
pages today.
Now in 2020, I'm finally tired of my existing system's
limitations. What should I do? It's not 2005 or 2012
anymore. What has changed in that time?
I can't move everything over to Wikisource, because of
the copyright differences.
Should I start to use Mediawiki + ProofreadPage and
convert my collection to that format?
Should I develop my own modification of Mediawiki?
Is that a stable ground to work from?
It seems to me that PHP, MariaDB and the architecture
of Mediawiki with extensions has now been the same for
a long time. Will this last for the next 20 years?
Or is there today some other existing systems that
solve the same problem, that weren't available in 2005?
(And that Wikisource would have picked up, if it were
started today, instead of developing its own extension.)
--
Lars Aronsson (lars(a)aronsson.se)
Project Runeberg - free Nordic literature - http://runeberg.org/
"There is also a difference in how we view copyright,
as my own website can cut corners and scan some books
that are "most likely" out of copyright, which is
something Wikimedia's user communities never accept."
Some of the community accept this. Polish Wikisource project uploaded
translation of one's Montgomery book, as "pseudonymous" work without any
proofs that it is pseudonym (even if they are, they are against COM:PRP).
It's still on Commons and AFAIK rejected to delete by admins or not decided
yet.
Mateusz Malinowski
niedz., 27 gru 2020, 13:02 użytkownik <
wikisource-l-request(a)lists.wikimedia.org> napisał:
> Send Wikisource-l mailing list submissions to
> wikisource-l(a)lists.wikimedia.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> or, via email, send a message with subject or body 'help' to
> wikisource-l-request(a)lists.wikimedia.org
>
> You can reach the person managing the list at
> wikisource-l-owner(a)lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wikisource-l digest..."
>
>
> Today's Topics:
>
> 1. Systems for proofreading scanned books (Lars Aronsson)
> 2. Re: Systems for proofreading scanned books (J Hayes)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 26 Dec 2020 19:23:02 +0100
> From: Lars Aronsson <lars(a)aronsson.se>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Cc: Wikisource <wikisource-l(a)lists.wikimedia.org>
> Subject: [Wikisource-l] Systems for proofreading scanned books
> Message-ID: <e04dc83b-0da2-0c89-fc39-c5f28e0b5443(a)aronsson.se>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> In 2005, at the first Wikimania in Frankfurt, Germany,
> Magnus Manske asked me if I could open up my Scandinavian
> book scanning website Project Runeberg to German and
> other languages, or release the software as open source.
>
> I refused, as my software is just a rapid prototype that
> would need to be rewritten from scratch anyway. But I
> said that Wikisource could be used for this purpose. At
> the time, Wikisource was only a wiki for e-text. As a
> proof of concept, I put up "Meyers Blitz-Lexikon" as
> the first book with scanned page images in Wikisource,
> https://de.wikisource.org/wiki/Seite:LA2-Blitz-0005.jpg
> and soon after the "New Student's Reference Work",
> https://en.wikisource.org/wiki/Page:LA2-NSRW-1-0013.jpg
>
> This was the basic inspiration for the "Proofread Page"
> extension, now used in Wikisource.
>
> In 2010-2011 I tried to use Wikisource, but I thought
> this extension was too hard to work with. From scanner
> to finished presentation, Wikisource was so much slower
> to work with than my own system. By primary gripes are:
> It is too hard to upload PDF files to Commons, it's too
> hard to create the Index page, each page is not created
> immediately (making the raw OCR text searchable), and
> pages hidden in the Page: namespace are not always
> indexed by search engines. Unfortunately, the system
> hasn't improved much in the last decade.
>
> (My criticism of my own website's system is a lot
> harsher, but hits different targets.)
>
> There is also a difference in how we view copyright,
> as my own website can cut corners and scan some books
> that are "most likely" out of copyright, which is
> something Wikimedia's user communities never accept.
>
> In 2012, I thought the time had finally come to rewrite
> my software, but I failed to organize a project around
> this, and instead I continued to use the existing system,
> just adding volume. Indeed, Project Runeberg has grown
> from 0.75 million book pages in 2012 to 3.1 million
> pages today.
>
> Now in 2020, I'm finally tired of my existing system's
> limitations. What should I do? It's not 2005 or 2012
> anymore. What has changed in that time?
>
> I can't move everything over to Wikisource, because of
> the copyright differences.
>
> Should I start to use Mediawiki + ProofreadPage and
> convert my collection to that format?
>
> Should I develop my own modification of Mediawiki?
> Is that a stable ground to work from?
>
> It seems to me that PHP, MariaDB and the architecture
> of Mediawiki with extensions has now been the same for
> a long time. Will this last for the next 20 years?
>
> Or is there today some other existing systems that
> solve the same problem, that weren't available in 2005?
> (And that Wikisource would have picked up, if it were
> started today, instead of developing its own extension.)
>
>
> --
> Lars Aronsson (lars(a)aronsson.se)
> Project Runeberg - free Nordic literature - http://runeberg.org/
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 26 Dec 2020 18:20:06 -0500
> From: J Hayes <slowking4(a)gmail.com>
> To: "discussion list for Wikisource, the free library"
> <wikisource-l(a)lists.wikimedia.org>
> Subject: Re: [Wikisource-l] Systems for proofreading scanned books
> Message-ID:
> <CAN38RzKojj9K=
> nZ50Lbbvv5ZUND9WcA5kCRGeh++33ohfHB5Gg(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> My suggestions:
> Simplified UX to upload works is on the wishlist
> But a tool that led to user to interact on multiple projects to produce a
> “rough draft” work from a scan would be a great step forward.
> Copyright might be eased for a local copy at wikisource, not on commons.
> But you would need some community consensus. If you were bringing tools,
> they might work with you, you should reach out to them. You could also
> transfer over the easy copyright works to wikisource, and retain the loose
> ones at your site. (The value to using wikisource is the increased
> visibility being integrated in Wikipedia, and community building potential)
> So I would brainstorm some goals, and begin a conversation / partnership
> with your wikisource language community toward an action plan.
> If I can be of help let me know.
> Cheers
> Jim hayes
>
>
> On Sat, Dec 26, 2020 at 1:23 PM Lars Aronsson <lars(a)aronsson.se> wrote:
>
> > In 2005, at the first Wikimania in Frankfurt, Germany,
> > Magnus Manske asked me if I could open up my Scandinavian
> > book scanning website Project Runeberg to German and
> > other languages, or release the software as open source.
> >
> > I refused, as my software is just a rapid prototype that
> > would need to be rewritten from scratch anyway. But I
> > said that Wikisource could be used for this purpose. At
> > the time, Wikisource was only a wiki for e-text. As a
> > proof of concept, I put up "Meyers Blitz-Lexikon" as
> > the first book with scanned page images in Wikisource,
> > https://de.wikisource.org/wiki/Seite:LA2-Blitz-0005.jpg
> > and soon after the "New Student's Reference Work",
> > https://en.wikisource.org/wiki/Page:LA2-NSRW-1-0013.jpg
> >
> > This was the basic inspiration for the "Proofread Page"
> > extension, now used in Wikisource.
> >
> > In 2010-2011 I tried to use Wikisource, but I thought
> > this extension was too hard to work with. From scanner
> > to finished presentation, Wikisource was so much slower
> > to work with than my own system. By primary gripes are:
> > It is too hard to upload PDF files to Commons, it's too
> > hard to create the Index page, each page is not created
> > immediately (making the raw OCR text searchable), and
> > pages hidden in the Page: namespace are not always
> > indexed by search engines. Unfortunately, the system
> > hasn't improved much in the last decade.
> >
> > (My criticism of my own website's system is a lot
> > harsher, but hits different targets.)
> >
> > There is also a difference in how we view copyright,
> > as my own website can cut corners and scan some books
> > that are "most likely" out of copyright, which is
> > something Wikimedia's user communities never accept.
> >
> > In 2012, I thought the time had finally come to rewrite
> > my software, but I failed to organize a project around
> > this, and instead I continued to use the existing system,
> > just adding volume. Indeed, Project Runeberg has grown
> > from 0.75 million book pages in 2012 to 3.1 million
> > pages today.
> >
> > Now in 2020, I'm finally tired of my existing system's
> > limitations. What should I do? It's not 2005 or 2012
> > anymore. What has changed in that time?
> >
> > I can't move everything over to Wikisource, because of
> > the copyright differences.
> >
> > Should I start to use Mediawiki + ProofreadPage and
> > convert my collection to that format?
> >
> > Should I develop my own modification of Mediawiki?
> > Is that a stable ground to work from?
> >
> > It seems to me that PHP, MariaDB and the architecture
> > of Mediawiki with extensions has now been the same for
> > a long time. Will this last for the next 20 years?
> >
> > Or is there today some other existing systems that
> > solve the same problem, that weren't available in 2005?
> > (And that Wikisource would have picked up, if it were
> > started today, instead of developing its own extension.)
> >
> >
> > --
> > Lars Aronsson (lars(a)aronsson.se)
> > Project Runeberg - free Nordic literature - http://runeberg.org/
> >
> >
> >
> > _______________________________________________
> > Wikisource-l mailing list
> > Wikisource-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> >
>
