[Wikisource-l] Re: MediaWiki, Wikisource extensions, and new implementations deployment

[Sam Wilson]

I think tackling one thing at a time makes lots of sense, especially if 
there's a process around it. I don't know who would run such a process, 
especially considering that developers will generally work on whatever 
they feel like! Perhaps we need to sketch out (on Meta?) a simple 
workflow for anyone working on Wikisource code (extensions only; gadgets 
are informal and should stay that way).


For me, I have a small amount of time to work on Wikisource stuff, and I 
generally work on whatever's most important. I don't have any actual way 
to gauge that though (I have wondered if we should encourage people to 
award tokens to Phabricator tasks, but it seems that there's no way to 
actually sort by number awarded).


And yep, https://en.wikisource.beta.wmflabs.org/ 
<https://en.wikisource.beta.wmflabs.org/> is there and can be used for 
testing. Merged changes are live there within ten minutes. However, 
unless a feature is disabled by a feature flag it'll also be live in 
production within a week, so it's often not great to merge something 
that needs end-user testing. Adding a feature flag is possible (e.g. a 
config var or a preference), but for some things it can be a fair bit of 
added complexity. Not that it's not worth it for some things, but it 
should be a decision and not the default way of doing things.


—Sam

On 22/11/21 8:08 pm, Ruthven wrote:

Hi all, and thanks for the info.

I get from your messages that there are two major points to be solved:
1. A clear lack of communication (mass messages are often unread or 
quickly read, because there is some abuse of the tool,  and what is 
important gets lost in the flood of messages). Probably it's not the 
role of developers to communicate, but someone has to do it.
2. A clear lack of management. There is a global lack of trust in 
Mediawiki developers for the reason above, but also because certain 
changes introduced more issues than they solved. I agree with Sam: 
there is a need for product managers, who can also communicate about 
important changes, but also check the development and be sure that new 
changes can be safely deployed. I mean: it's the basics of software 
development!


I don't think it's a matter of time if we focus on one feature at a 
time, test it, test it again, do beta test, and then merge it. We're 
not a software house: we do have time. I understand that volunteers 
might not be happy in being constrained by a strict workflow, but I 
also understand that work has to be done well or not done at all.


Btw, I understand that there is beta.wikisource somewhere. Maybe an 
invitation to the different projects to test the new features there 
before the merge, would be a good occasion to involve more people in 
quality control. (sorry if this has been done, and I've missed it)


Cheers,
A.
*Ruthven*on Wikipedia


On Mon, 22 Nov 2021 at 04:45, Sam Wilson <mailto:s...@samwilson.id.au>> wrote:


I think most Wikisource developers are likely to be on this list.
Of course, it's best to make sure there are Phabricator tickets
for every separate bug or feature request.

On 21/11/21 1:36 am, Ankry wrote:


Well, I was notified by techncally skilled users that the ned
OpenSeadragon library is much heavier and more memory consuming
than curreently used tools. So I can only hope that its load into
memory can be disabled if one needs so.

(may be critical while working on multiple pages at once)

However, I doubt if any technical comments from communities
expressed here will reach developers. And which wiki pages would
be more appropriate for such comments.

Ankry

W dniu 20.11.2021 o 14:33, Ruthven pisze:

Hi all,
  as usual, I get surprised every time there are major changes
on the MediaWiki software that are deployed without providing
advance warning to the community.
Every time it's the same story: something stops working on the
project. A gadget, a toolbar or some personalised JS.

This time it was T288141 (see
https://phabricator.wikimedia.org/T288141
<https://phabricator.wikimedia.org/T288141>), that was deployed
in all the Wikisources (then rolled back because WikiMedia
computer scientists are the best) completely
disrupting redesigning the image side of the Page namespace.
This affected the toolbars (see
https://phabricator.wikimedia.org/T296033
<https://phabricator.wikimedia.org/T296033>) and several gadgets
around all the Wikisources.

I am not saying that MediaWiki software shouldn't be improved:
it's normal that we're trying to get all we can from this
outdated software. I am just asking that major changes that
affect all the Wikisources should be announced in every single
Village Pump waaay before deploying them on the projects.

Is it possible, as a Usergroup, to do a little pressure to be
considered as a community and not as guinea pigs on which t

[Wikisource-l] Re: MediaWiki, Wikisource extensions, and new implementations deployment

[Sam Wilson]

I think most Wikisource developers are likely to be on this list. Of 
course, it's best to make sure there are Phabricator tickets for every 
separate bug or feature request.


On 21/11/21 1:36 am, Ankry wrote:


Well, I was notified by techncally skilled users that the ned 
OpenSeadragon library is much heavier and more memory consuming than 
curreently used tools. So I can only hope that its load into memory 
can be disabled if one needs so.


(may be critical while working on multiple pages at once)

However, I doubt if any technical comments from communities expressed 
here will reach developers. And which wiki pages would be more 
appropriate for such comments.


Ankry

W dniu 20.11.2021 o 14:33, Ruthven pisze:

Hi all,
  as usual, I get surprised every time there are major changes on the 
MediaWiki software that are deployed without providing advance 
warning to the community.
Every time it's the same story: something stops working on the 
project. A gadget, a toolbar or some personalised JS.


This time it was T288141 (see 
https://phabricator.wikimedia.org/T288141), that was deployed in all 
the Wikisources (then rolled back because WikiMedia computer 
scientists are the best) completely disrupting redesigning the image 
side of the Page namespace. This affected the toolbars (see 
https://phabricator.wikimedia.org/T296033) and several gadgets around 
all the Wikisources.


I am not saying that MediaWiki software shouldn't be improved: it's 
normal that we're trying to get all we can from this outdated 
software. I am just asking that major changes that affect all the 
Wikisources should be announced in every single Village Pump waaay 
before deploying them on the projects.


Is it possible, as a Usergroup, to do a little pressure to be 
considered as a community and not as guinea pigs on which to deploy 
new, partially-tested features?


Alex
*Ruthven*on Wikipedia

___
Wikisource-l mailing list --wikisource-l@lists.wikimedia.org
To unsubscribe send an email towikisource-l-le...@lists.wikimedia.org


___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org

[Wikisource-l] Re: MediaWiki, Wikisource extensions, and new implementations deployment

[Sam Wilson]

I totally understand this frustration, and I'm not really sure what the 
solution is. There's no WMF team responsible for Wikisource (other than 
the small amounts of work that my team, CommTech, gets to do; although 
I'm writing this email as my volunteer self). So it's up to whoever 
wants to do the work, and generally getting the work done comes first 
and any announcements or outreach are an after-thought and can sometimes 
get forgotten.


There's lots of development happening with Wikisource-related things at 
the moment, because there are more developers interested. Which is 
really great! I feel like it's exciting, and there's lots of enthusiasm. 
Some bits of the Wikisource stack have been unchanged for years and 
years, because they're quite complicated, and responsibility has fallen 
on the same few users to fix any problems. Now we seem to be in an era 
of new features, which comes with different challenges.


So I'm sorry if it feels like Wikisource is used as a guinea pig — I 
think it's more that the software stack here is unique among Wikimedia 
projects. Changes do get tested, nothing is ever merged that hasn't been 
checked by multiple developers. But we don't have a good system of 
rolling out big changes like the recent update to the zoom/pan library 
(from a homegrown system to OpenSeadragon).


We need more volunteer product managers! As in, people to have a good 
overview of what development is happening or needs to happen, and help 
it go smoothly. It's no harder than herding cats, surely!


Sorry, I don't think I'm writing any of this very clearly... all I 
really wanted to reply was "we're doing our best, and no one's got 
enough time!". But there's lots more to it.


—Sam


On 20/11/21 9:33 pm, Ruthven wrote:

Hi all,
  as usual, I get surprised every time there are major changes on the 
MediaWiki software that are deployed without providing advance warning 
to the community.
Every time it's the same story: something stops working on the 
project. A gadget, a toolbar or some personalised JS.


This time it was T288141 (see 
https://phabricator.wikimedia.org/T288141 
), that was deployed in all 
the Wikisources (then rolled back because WikiMedia computer 
scientists are the best) completely disrupting redesigning the image 
side of the Page namespace. This affected the toolbars (see 
https://phabricator.wikimedia.org/T296033 
) and several gadgets 
around all the Wikisources.


I am not saying that MediaWiki software shouldn't be improved: it's 
normal that we're trying to get all we can from this outdated 
software. I am just asking that major changes that affect all the 
Wikisources should be announced in every single Village Pump waaay 
before deploying them on the projects.


Is it possible, as a Usergroup, to do a little pressure to be 
considered as a community and not as guinea pigs on which to deploy 
new, partially-tested features?


Alex
*Ruthven*on Wikipedia

___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org

[Wikisource-l] Re: Help wanted: local labels for Wikisources on Wikidata

[Sam Wilson]

Good question! I meant to call that one out actually, because 
Multilingual Wikisource should have /all/ its labels! Especially, 
actually, in languages that /don't/ have a Wikisource of their own, 
because they're more likely to be using that one. :-)



On 2/8/21 4:20 pm, Ankry wrote:


I just wonder which lamguage description is missing for Multilingual 
Wikisource. :)


Ankry

On 02.08.2021 09:44, Sam Wilson wrote:


Hi everyone,

I noticed the other day that there are a bunch of Wikisources whose 
Wikidata items don't have labels in the languages of those Wikisources.


So if anyone knows how to write "Welsh Wikisource" in Welsh, it'd be 
great if you could go to Q24577651 
<https://www.wikidata.org/wiki/Q24577651> and add the Welsh label. 
Similarly for the rest of these:



[...]


wd:Q18198097 <http://www.wikidata.org/entity/Q18198097> 	Multilingual 
Wikisource


[...]



___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org

[Wikisource-l] Help wanted: local labels for Wikisources on Wikidata

[Sam Wilson]

Hi everyone,

I noticed the other day that there are a bunch of Wikisources whose 
Wikidata items don't have labels in the languages of those Wikisources.


So if anyone knows how to write "Welsh Wikisource" in Welsh, it'd be 
great if you could go to Q24577651 
 and add the Welsh label. 
Similarly for the rest of these:


wd:Q15156667  	Sanskrit 
Wikisource
wd:Q18198097  	Multilingual 
Wikisource

wd:Q21205461    Latin Wikisource
wd:Q24577647  	Belarusian 
Wikisource
wd:Q24577644  	Old English 
Wikisource

wd:Q24577650    Bosnian Wikisource
wd:Q24577651    Welsh Wikisource
wd:Q24577648  	Bulgarian 
Wikisource
wd:Q24577655  	Modern Greek 
Wikisource

wd:Q24577653    Danish Wikisource
wd:Q24577658    Persian Wikisource
wd:Q24577657  	Estonian 
Wikisource
wd:Q24577663  	Croatian 
Wikisource

wd:Q24577660    Faroese Wikisource
wd:Q24577661  	Galician 
Wikisource
wd:Q24577666  	Indonesian 
Wikisource
wd:Q24577664  	Haitian Creole 
Wikisource
wd:Q24577669  	Icelandic 
Wikisource
wd:Q24577674  	Limburgish 
Wikisource
wd:Q24577678  	Macedonian 
Wikisource
wd:Q24577676  	Lithuanian 
Wikisource
wd:Q24577682  	Norwegian 
Wikisource
wd:Q24577683  	Romanian 
Wikisource

wd:Q24577686    Slovene Wikisource
wd:Q24577684    Sakha Wikisource
wd:Q24577685    Slovak Wikisource
wd:Q24577688    Serbian Wikisource
wd:Q24577695  	Venetian 
Wikisource

wd:Q24577693    Turkish Wikisource
wd:Q24577696    Yiddish Wikisource
wd:Q24577697    Min Nan Wikisource
wd:Q54893569  	Piedmontese 
Wikisource
wd:Q97568657  	Ligurian 
Wikisource
wd:Q107387552  	Balinese 
Wikisource



___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org

[Wikisource-l] IA Upload (new server)

[Sam Wilson]

In an effort to improve performance, I've set up IA Upload on its own VPS:

https://ia-upload.wmcloud.org/ 

The Toolforge installation at https://ia-upload.toolforge.org/ 
 is still there, but if the VPS proves 
better we can redirect there.


Just wondering if anyone feels like testing out the new server and 
seeing if there's any improvement? Would love any feedback.


The ticket for this work is https://phabricator.wikimedia.org/T284528 



Thanks!

—Sam
___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org

[Wikisource-l] Re: Testing the new OCR tool

[Sam Wilson]

Yes sure! We probably don't want /too/ many test sites though, in case 
something is not working well.


We can roll out more wikis later (every couple of days).

On 8/6/21 2:25 pm, Rachmat W. wrote:

Dear Sam,

Is it possible to extend the test to idwikisource?

Best,
Rachmat


On Tue, Jun 08, 2021 at 1:21pm, Sam Wilson <mailto:s...@samwilson.id.au>> wrote:


Right, it's going to be deployed to hi, bn, mul, and ta tomorrow
morning (at about 04:30 IST). :-)

On 8/6/21 8:44 am, Sam Wilson wrote:


Hi all,

The new OCR tool is ready for testing, and we (the Community Tech
team) are wondering what Wikisources it should be rolled out to
first <https://phabricator.wikimedia.org/T283898>. Does anyone
have a suggestion of which two or three Wikisources would be
willing to give it a go? It isn't likely to break anything, and
the existing gadgets aren't impacted (it'll just give a separate
button, which could be confusing, but doesn't interfere with the
existing ones).

You can try it out on Beta now:

https://en.wikisource.beta.wmflabs.org/w/index.php?title=Page:War_and_Peace.djvu/55=edit

<https://en.wikisource.beta.wmflabs.org/w/index.php?title=Page:War_and_Peace.djvu/55=edit>

Note that the engine selection is saved in your browser's
LocalStorage, so will not be saved between browsers/devices but
will be saved between sessions on the same browser.

Thanks,
Sam.


___
Wikisource-l mailing list --wikisource-l@lists.wikimedia.org
To unsubscribe send an email towikisource-l-le...@lists.wikimedia.org


___ Wikisource-l
mailing list -- wikisource-l@lists.wikimedia.org
<mailto:wikisource-l@lists.wikimedia.org> To unsubscribe send an
email to wikisource-l-le...@lists.wikimedia.org
<mailto:wikisource-l-le...@lists.wikimedia.org> 



___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org

[Wikisource-l] Re: Testing the new OCR tool

[Sam Wilson]

Right, it's going to be deployed to hi, bn, mul, and ta tomorrow morning 
(at about 04:30 IST). :-)


On 8/6/21 8:44 am, Sam Wilson wrote:


Hi all,

The new OCR tool is ready for testing, and we (the Community Tech 
team) are wondering what Wikisources it should be rolled out to first 
<https://phabricator.wikimedia.org/T283898>. Does anyone have a 
suggestion of which two or three Wikisources would be willing to give 
it a go? It isn't likely to break anything, and the existing gadgets 
aren't impacted (it'll just give a separate button, which could be 
confusing, but doesn't interfere with the existing ones).


You can try it out on Beta now: 
https://en.wikisource.beta.wmflabs.org/w/index.php?title=Page:War_and_Peace.djvu/55=edit 
<https://en.wikisource.beta.wmflabs.org/w/index.php?title=Page:War_and_Peace.djvu/55=edit>


Note that the engine selection is saved in your browser's 
LocalStorage, so will not be saved between browsers/devices but will 
be saved between sessions on the same browser.


Thanks,
Sam.


___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org
___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org

[Wikisource-l] Testing the new OCR tool

[Sam Wilson]

Hi all,

The new OCR tool is ready for testing, and we (the Community Tech team) 
are wondering what Wikisources it should be rolled out to first 
. Does anyone have a 
suggestion of which two or three Wikisources would be willing to give it 
a go? It isn't likely to break anything, and the existing gadgets aren't 
impacted (it'll just give a separate button, which could be confusing, 
but doesn't interfere with the existing ones).


You can try it out on Beta now: 
https://en.wikisource.beta.wmflabs.org/w/index.php?title=Page:War_and_Peace.djvu/55=edit 



Note that the engine selection is saved in your browser's LocalStorage, 
so will not be saved between browsers/devices but will be saved between 
sessions on the same browser.


Thanks,
Sam.

___
Wikisource-l mailing list -- wikisource-l@lists.wikimedia.org
To unsubscribe send an email to wikisource-l-le...@lists.wikimedia.org

[Wikisource-l] Logos on Wikidata

[Sam Wilson]

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.


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] WS Export sidebar links

[Sam Wilson]

Hi everyone!

This week we (the Community Tech 
 team, of which I'm a 
part) are going to roll out phab:T256392 
 which will move the 
functionality of the MediaWiki:Gadget-WSexport.js 
 gadget 
into the Wikisource extension 
. 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 
 
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 
 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 
.



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Welcoming GSoC student Sohom Datta

[Sam Wilson]

Yes I reckon so! Not quite yet, but at some point we'll definitely have 
something to test and will be wanting users to explore it on Beta 
Wikisource and give feedback. My feeling is that there are a bunch of 
different workflows that people use to construct pagelists, and the new 
widget is going to hopefully help with the most normal ~70% of those — 
it won't do everything, but that common task of looking up a scan's page 
number will be front and centre and accessible right in the Index 
editing form. :)


—Sam.

On 19/5/20 12:56 am, Nicolas VIGNERON wrote:

Hi all,

This is indeed an excellent news that brightens my day. WelcomeSohom 
Datta!


I totally trust the co-mentors to help him but is there something that 
we - the community - can do to help?


Cheers, ~nicolas

Le lun. 18 mai 2020 à 18:29, Satdeep Gill <mailto:sg...@wikimedia.org>> a écrit :


Hello everyone,

*
*

I hope you are all healthy and safe during these difficult times.
I expect that this news might cheer all Wikisource enthusiasts out
there!

*
*

I am happy to introduce Sohom Datta
<https://phabricator.wikimedia.org/p/Soda/>! He is one of the
students that the Wikimedia Foundation has selected for the
current round of Google Summer of Code. He is a first year student
of Bachelor’s in Computer Science and Engineering. He will be
working on creating a widget to easily create pagelists on
    Wikisource. Sam Wilson (primary mentor) and I (co-mentor) will be
mentoring this project.

*
*

This project was prioritized because Index creation wizard

<https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020/Wikisource/Index_creation_wizard>was
one of the highly voted proposals inCommunity Wishlist Survey 2020
<https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2020>,
coming at 6th spot, but couldn’t make it to the Top 5. More
updates on the next steps related to the Wishlist process will
follow shortly.

*
*

Further details and progress related to this project can tracked
on the related phabricator ticket:

 *

https://phabricator.wikimedia.org/T247157

*
*

Feel free to provide any feedback that you might have related to
the project on the phabricator ticket. We will be regularly
providing updates to the community as well.

*
*

P.S. Sohom also contributes to English Wikipedia and English
Wikisource in his free time under the username: Sohom data
<https://www.mediawiki.org/wiki/User:Sohom_data>.

*
*

Stay Safe!

Satdeep



-- 




Satdeep Gill (pronouns - he, him)

Program Officer

GLAM and Underrepresented Knowledge

Wikimedia Foundation <https://wikimediafoundation.org/>



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
<mailto:Wikisource-l@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Takedown of BUB book on Internet Archive

[Sam Wilson]

On 3/7/19 7:09 PM, Jane Darnell wrote:

Next, how do you use ABBY to convert a .PDF to .djvu?


I must admit I'm guilty of suggesting people just use PDFs, as it's so 
much easier to explain! Does anyone have any suggestions about how to 
convince people to prefer DjVu over PDF? It seems from the outside of 
the proofreading process that there's no problem with PDF.


— Sam.

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Category loop in vi.wikisource.org

[Sam Wilson]

Is there anyone here from Vietnamese Wikisource? There seems to be a 
category loop:


"Việt_Nam_sử_lược" -> "Thể loại:Sách_sử"
"Thể loại:Sách_sử" -> "Thể loại:Lịch_sử"
"Thể loại:Sách_sử" -> "Thể loại:Sách"
"Thể loại:Sách" -> "Thể loại:Tác_phẩm_theo_loại"
"Thể loại:Tác_phẩm_theo_loại" -> "Thể loại:Tác_phẩm"
"Thể loại:Tác_phẩm" -> "Thể loại:Tất_cả"
"Thể loại:Tất_cả" -> "Thể loại:Thể_loại_ẩn"
"Thể loại:Thể_loại_ẩn" -> "Thể loại:Thể_loại_theo_dõi_thể_loại"
"Thể loại:Thể_loại_theo_dõi_thể_loại" -> "Thể loại:Thể_loại_theo_dõi"
"Thể loại:Thể_loại_theo_dõi" -> "Thể loại:Bảo_quản_Wikisource"
"Thể loại:Bảo_quản_Wikisource" -> "Thể loại:Wikisource"
"Thể loại:Wikisource" -> "Thể loại:Tất_cả"

As a graph: https://imgur.com/GLvtxSW

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Everything will be Wikipedia

[Sam Wilson]

It'd be worth making a note about your concerns at 
https://meta.wikimedia.org/wiki/Communications/Wikimedia_brands/2030_research_and_planning/community_review


As far as I can see, there's no plan to change Wikisource's name. It's 
more about making 'Wikipedia' more prominent than 'Wikimedia' (which it 
already is in most people's eyes). 'Wikisource' doesn't come into it.


(I'm saying this as myself, not as WMF staff.)

It's encouraging that Wikisource has relatively high awareness (p.38 of 
the report 
https://upload.wikimedia.org/wikipedia/commons/3/37/Global_Wikipedia_and_Wikimedia_Brand_Research_Report.pdf 
), ahead of Wikidata and Commons. They do note that the high awareness 
of Wikinews and Wikibooks is likely to be because they sound like 
generic names of things.


—Sam.

On 2/8/19 11:19 AM, Bodhisattwa Mandal wrote:

Hi,

I have heard from a trusted source few months back that there are talks 
in WMF to rebrand all sister projects under the name Wikipedia. If that 
happens some day, Wikisource will be no more as it is and it will be 
called something like Wikipedia-source etc. The logic for this kind of 
step is that people doesn't know or understand Wikimedia, but everyone 
knows only about Wikipedia.


I think, the recent blog in the Foundation site is the first step to do 
such things.

https://wikimediafoundation.org/2019/02/07/how-does-the-world-see-wikimedia-brands/

IMHO, very few people know about sister projects, because they didn't 
get the love they needed from WMF or other affiliates. Everything is so 
Wikipedia centric. But that can't be the fault of the sister projects.


I hope this rebranding doesnt become true someday.

Regards,
Bodhisattwa




___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Last days to vote Wikisource tech proposals

[Sam Wilson]

It's super exciting! I'm very glad Wikisource made it to the top 10 this 
year. Now hopefully I get to work on Wikisource stuff! (For those who 
don't know, I'm on the CommTech team and will be working on this.)


CommTech is meeting this week and we'll be talking about the survey 
results and figuring out some initial things. The proposal page will be 
updated with any news, and I'll try to keep this mailing list in the 
loop too.


Personally, I use epubs from wsexport all the time, and so have a random 
assortment of annoyances that I know about, but we'll want to make sure 
everything is documented in Phabricator.


--Sam

On 4/12/18 3:07 am, balaji wrote:
Wow.. thats wonderful news. Thanks for the initiative and all who have 
voted for that. Now what's next ? The community tech tech team LL take 
forward by itself ? How to involve more deeply with the project ?


On Tue, Dec 4, 2018, 4:36 PM David Cuenca Tudela > wrote:


We got one proposal in! " Improve export of electronic books

"

Thanks to everyone who voted. Here there are the complete results:
https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Results

On Thu, Nov 29, 2018 at 6:50 PM Orbilius Magister mailto:edow...@gmail.com>> wrote:

Done!

Il giorno mar 27 nov 2018 alle ore 22:55 David Cuenca Tudela
mailto:dacu...@gmail.com>> ha scritto:

The Community Wishlist Survey 2019 period for voting
proposals will end on November 30th at 18:00 UTC. If you
haven't voted yet, you can do so here:

https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Wikisource

Regards,
Micru
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org

https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org

https://lists.wikimedia.org/mailman/listinfo/wikisource-l



-- 
Etiamsi omnes, ego non

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org

https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Telegram group for Wikisource

[Sam Wilson]

There's a new Telegram group:
tg://join?invite=FeIIHRKgyed-ODRYi0JzoQ

Currently got 50 of us in it. Just thought I'd spread the word here. I 
know Telegram isn't super great for various reasons and some people 
can't use it, but it seems to be growingly popular in the Wikimedia 
universe.


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Google OCR button to override language?

[Sam Wilson]

Just wondering if anyone else has an opinion on this:
https://phabricator.wikimedia.org/T198040

It might even be nice to extend the OCR gadget to be able to be used for 
single-image transcriptions on Commons.


—Sam

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] wscontest tool

[Sam Wilson]

This is a good point, and we certainly don't want contests to encourage 
people to mark pages as proofread or validated too hastily.


I think the main guard against this is that scores will not be exposed 
until contest admin chooses to, and after they have had a chance to go 
through a sample of each person's edits to make sure they're not 
cheating. And of course, the normal on-wiki processes still apply, to 
catch edits that are not good.


As far as not scoring for e.g. template reorganising etc. I'm not sure 
that's going to be very easy at all! :) But if anyone's got any ideas, 
let us know. But we could do something about counting edit size maybe? 
Although, especially in validating, larger edits don't necessarily mean 
they should be worth more points.


We could subtract points for any edits post-validatation, rather than 
(as it is now) just for demotions (I'm not sure how many people demote 
pages from validated, compared to how many just fix them and leave them 
as validated).


On 22/06/18 20:00, ankry.wiki wrote:
Maybe a bit OT, but did anybody consider to analyze how many corrections 
/ how much content a user changes his/her edits?
As we (in pl.ws) focus on text quality, it would be appreciated to score 
higher the edits with corrections than edits with no correction ("no 
errors found").
I understand that it is hard to create such tool, especially if 
automatic corrections (eg.  ->  or template parameter 
reorganization should be ignored), but maybe, somebody has an idea how 
to to do this?

Ankry
PS. We do not participate in this contest in its current form because 
some of our users are afraid that this will lower the text quality 
(users might prefer just to update the status without careful checking 
the content, just declaring that "no errors found"; and it is hard to 
identify such users/edits).
W dniu 2018-06-22 09:29:45 użytkownik Rachmat W. 
 napisał:


Thank you, Sam!
We would like to utilize this tool in the Wikisource contest later. :)
Kind regards,
Rachmat
On Jun 22, 2018, 07:08 +0700, Sam Wilson , wrote:

Hi all,

After chatting with User:CristianCantoro at the Barcelona
hackathon, I
had a crack at a web frontend for the wscontest tool. It is now
online
at https://tools.wmflabs.org/wscontest/

It's not quite done, there's a bunch of things to be fixed, but is
functioning to some extent. I've started a list of its issues at
https://phabricator.wikimedia.org/tag/tool-wscontest/

--sam


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] 500 Internal Server Error for Google OCR button

[Sam Wilson]

The error message could be more helpful, but basically this is because
there's a limit on the size of images that can be sent to the Cloud
Vision API.
With a smaller version of the same image, it is working:

https://tools.wmflabs.org/ws-google-ocr/index.php?image=https%3A%2F%2Fupload.wikimedia.org%2Fwikipedia%2Fcommons%2Fthumb%2F8%2F89%2FBengaliOCRtest.jpg%2F424px-BengaliOCRtest.jpg=bn
I think this is a different error to the one in
https://phabricator.wikimedia.org/T190216

On Wed, 21 Mar 2018, at 4:50 AM, Jayanta Nath wrote:
> Please check it with one test file.
> 
> https://tools.wmflabs.org/ws-google-ocr/index.php?image=https%3A%2F%2Fupload.wikimedia.org%2Fwikipedia%2Fcommons%2F8%2F89%2FBengaliOCRtest.jpg=bn>
>  
> On Wed, Mar 21, 2018 at 2:16 AM, Bodhisattwa Mandal
>  wrote:>> Hi Sam,
>> The Google OCR button and the tool[1] is giving 500 internal server
>> error output from today, although the Cloud Vision API is working
>> fine[2].>> 
>> We have reported in phabricator here[3]. It would be great for us if
>> you please look into this matter urgently as all our options are
>> suddenly ceasing to work.>> 
>> -- 
>> Bodhisattwa
>> 
>> 
>> ___
>>  Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>> 
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


Links:

  1. https://tools.wmflabs.org/ws-google-ocr/
  2. https://cloud.google.com/vision/docs/drag-and-drop
  3. https://phabricator.wikimedia.org/T190216
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Zero output for OCR using Google Drive API

[Sam Wilson]

Sorry, I just realised you were all talking about the *Drive* API, not the 
*Vision* Api! :-) I dunno anything about that.

On Fri, 16 Mar 2018, at 9:45 AM, Sam Wilson wrote:
> They do all use the same API key, yes.
> 
> There doesn't seem to be anything obvious on the API end. Request 
> numbers are pretty low under 1 request/minute and our quota is 600 r/m.
> 
> The tool seems to be working:
> 
> https://tools.wmflabs.org/ws-google-ocr/index.php?image=https%3A%2F%2Fupload.wikimedia.org%2Fwikipedia%2Fcommons%2Fthumb%2Fb%2Fbf%2FNandeesha_a.jpg%2F425px-Nandeesha_a.jpg=bn
> 
> https://tools.wmflabs.org/ws-google-ocr/index.php?image=https%3A%2F%2Fupload.wikimedia.org%2Fwikipedia%2Fcommons%2Fthumb%2Fa%2Fa2%2F07174-Mei%25C3%259Fen-1906-Baarmanns_Bierk%25C3%25BChler-Br%25C3%25BCck_%2526_Sohn_Kunstverlag.jpg%2F394px-07174-Mei%25C3%259Fen-1906-Baarmanns_Bierk%25C3%25BChler-Br%25C3%25BCck_%2526_Sohn_Kunstverlag.jpg=
> 
> Maybe it's a problem with the gadget?
> 
> 
> On Fri, 16 Mar 2018, at 4:11 AM, Federico Leva (Nemo) wrote:
> > Just to eliminate a potential silly cause: do all those languages use 
> > the same API key, and are you able to verify what's the quota usage?
> > 
> > Federico
> > 
> > ___
> > Wikisource-l mailing list
> > Wikisource-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> 
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Zero output for OCR using Google Drive API

[Sam Wilson]

They do all use the same API key, yes.

There doesn't seem to be anything obvious on the API end. Request numbers are 
pretty low under 1 request/minute and our quota is 600 r/m.

The tool seems to be working:

https://tools.wmflabs.org/ws-google-ocr/index.php?image=https%3A%2F%2Fupload.wikimedia.org%2Fwikipedia%2Fcommons%2Fthumb%2Fb%2Fbf%2FNandeesha_a.jpg%2F425px-Nandeesha_a.jpg=bn

https://tools.wmflabs.org/ws-google-ocr/index.php?image=https%3A%2F%2Fupload.wikimedia.org%2Fwikipedia%2Fcommons%2Fthumb%2Fa%2Fa2%2F07174-Mei%25C3%259Fen-1906-Baarmanns_Bierk%25C3%25BChler-Br%25C3%25BCck_%2526_Sohn_Kunstverlag.jpg%2F394px-07174-Mei%25C3%259Fen-1906-Baarmanns_Bierk%25C3%25BChler-Br%25C3%25BCck_%2526_Sohn_Kunstverlag.jpg=

Maybe it's a problem with the gadget?


On Fri, 16 Mar 2018, at 4:11 AM, Federico Leva (Nemo) wrote:
> Just to eliminate a potential silly cause: do all those languages use 
> the same API key, and are you able to verify what's the quota usage?
> 
> Federico
> 
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Twitter

[Sam Wilson]

Cool!

There are now seven Wikisources on Twitter:
https://twitter.com/wikisource/lists/wikisources/members

If anyone wants to help curate the main @wikisource account, do put your
hand up. :-)

On Wed, 14 Feb 2018, at 2:32 PM, balaji wrote:
> Hi,
> 
> There is a twitter account for Tamil wikisource. its username is
> tawikisource> 
> https://twitter.com/tawikisource
> 
> Please add this in the twitter list.
> 
> Cheers
> J. Balaji
> [[User:Balajijagadesh]]
> 
> On Tue, Aug 22, 2017 at 5:48 AM, Sam Wilson
> <s...@samwilson.id.au> wrote:>> Hi all,
>> 
>>  There's been some discussion at
>> https://en.wikisource.org/wiki/Wikisource_talk:WikiProject_Social_media#Twitter>>
>>   about the @wikisource Twitter account (and others).
>> 
>>  I've just been made a team member of @wikisource, and we should
>>  add some>>  more people too.
>> 
>>  The idea is that @wikisource is the cross-Wikisource account,
>>  and each>>  language Wikisource can also have its own account (e.g.
>>  @wikisource_fr>>  @wikisource_de, etc. ­here's a list I started this 
>> morning:
>> https://twitter.com/wikisource/lists/wikisources/members are
>> there any>>  others?)
>> 
>>  So, who wants to be added, and what are your Twitter usernames?
>> 
>>  We'll also have @wikisource_en later today or tomorrow; same deal.
>> 
>>  The passwords for these accounts are held by Aubrie Johnson, the WMF>>  
>> social media person.
>> 
>>  Thanks,
>>  Sam.
>> 
>>  ___
>>  Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] IA Upload fixes

[Sam Wilson]

I agree there might be some work to do at some future point when
we're trying to import mixed-media works into Wikisource, but I'm
afraid for now the sole purpose of ia-upload is to convert IA scans
of books into DjVus. MP3s or any other non-text work cannot be
converted with this tool.
Have you tried using it? Did you notice any problems?

— Sam.


On Sun, 3 Dec 2017, at 06:03 AM, mathieu stumpf guntz wrote:
> Le 29/11/2017 à 08:47, Sam Wilson a écrit :
>> * Attempts to use the tool on items that don't have DjVu, PDF, or JP2
>>   Zip files will now fail. I'm not sure what people who were
>>   attempting to make DjVus of MP3s were thinking, but they'll get a
>>   nicer error message now.> Apart from the file format, which was under some 
>> patent issues until
> last year and should be soon be available to Commons (if not yet),
> what would be the problem with uploading the file to Commons? All the
> more, some books might have sound component. My daughter have a whole
> library of that kind. She also have plenty of book with tactile data
> which often make me wonder how we would integrate such a book in
> Wikisource, as I'm not aware of any technology to render that kind of
> data linked to the material texture. Defining a file format to store
> that kind of data would be surely the easy part, all the more when
> "digital texture" is a topic already extensively covered in the
> literature for 3D rendering purpose.> 
>  Just sharing some thoughts…
>
>> I dare say I'm broken something along the way, so do keep an eye out
>> for weirdnesses and let me know.  Thanks, sam.
>> ___ Wikisource-l mailing
>> list Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] IA Upload fixes

[Sam Wilson]

Hi all,

I've fixed a couple of issues with IA Upload:

* Some uploads, probably mostly from BUB, were running foul of the abuse
filter because they included a link to books.google.com. This link is
now being replaced prior to upload by the {{Google Book Search link}}
template (which is an ID template, not so much a search template).

* The attempt to find a creator template on Commons now discards date
ranges.

* Attempts to use the tool on items that don't have DjVu, PDF, or JP2
Zip files will now fail. I'm not sure what people who were attempting to
make DjVus of MP3s were thinking, but they'll get a nicer error message
now.

I dare say I'm broken something along the way, so do keep an eye out for
weirdnesses and let me know.

Thanks,
sam.

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Hangout session

[Sam Wilson]

The notes from yesterdays hangout are now online:
https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/November_2017_Hangout
Please tweak as required.


Would Saturday December 16 at 1400UTC be a good time for the next
hangout?

On Sat, 4 Nov 2017, at 09:38 PM, Nicolas VIGNERON wrote:
> Hi,
> Reminder, the meeting is in half an hour on
> https://hangouts.google.com/hangouts/_/wikimedia.org/wikisource> 
> Notes will be taken on
> https://etherpad.wikimedia.org/p/wikisource-hangout and the meta page
> to gather all these informations is
> https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/November_2017_Hangout>
>  
> Cdlt,
> ~nicolas
> 
> 2017-10-31 20:03 GMT+01:00 Nicolas VIGNERON
> :>> Hi everyone,
>> From January to April of this year, we had hangout session to talk
>> more directly about Wikisource (see
>> https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group#2017
>> for the notes of these sessions).>> 
>> Among subjects that can be discuss:
>> - Wikisource and Wikidata (and some infos about the WikidataCon in
>>   Berlin last weekend)>> - a second Wikisource conference in 2018 ?
>> - various issues or accomplishments you want to share or need help
>>   from others>> - the Wikisource Community User Group
>> 
>> What do you think of doing this again? Who would be interested to
>> join? (it was during week-end - Saturday or Sunday - afternoon to
>> allow people from all other the globe to join in, I suggest Saturday
>> 4 from 14:00 UTC to 15:00 UTC
>> https://www.timeanddate.com/worldclock/fixedtime.html?msg=November+Wikisource+Hangout=2017-11-04T14:00:00).>>
>>  
>> Cdlt, ~nicolas
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] quickstatements for missing editions

[Sam Wilson]

I've been experimenting with pulling editions' author information in
from Wikidata, and it's reasonably easy if wea) look at the immediate page's WD 
item, and see if it's got an author;b if it doesn't, traverse up via P629 to 
the work, and see if it's got
an author.If neither of those things exist, give up.
If an author was found somewhere, see if it's got a sitelink to
Wikisource andthen display it either with or without a link.
The list of authors is then joined together with commas or
whatever you want.
That seems to work for a good chunk of cases on English Wikisource. Is
that sort of thing universal amongst Wikisources?
It fails on things like organisational authors, and doesn't do anything
with translators (although the same process could be followed for
them... sort of).
I'd love to develop a cross-Wikisource lua module that could display a
list of authors, if it's possible.
Small steps! :-)


On Wed, 1 Nov 2017, at 05:58 PM, Andrea Zanni wrote:
> Authors from Italian Wikisource have already a lot (if not all)
> metadata on Wikidata:> authors are *easy* compared to books (don't have the 
> whole work-
> edition issue),> so I think that users Candalua, Alex brollo and others 
> solved this
> problem long ago.> When you've copied all the metadata from WS authors to WD 
> items
> (phase 1),> you then need a system in place to 
> * pull the data from WD and put it in WS (Lua templates or something)> * 
> maintain it (the templates need to remind the user to go to WD and
>   update the information)> This is phase 2. 
> 
> Unfortunately, for books we're always pre-phase 1 :-(
> 
> Aubrey
> 
> 
> On Wed, Nov 1, 2017 at 10:15 AM, Jane Darnell
> <jane...@gmail.com> wrote:>> Yes you definitely need this flow of 
> useful interproject
>> links both ways: as a trigger for Wikidatans to do more with
>> Wikisource pages, and as a trigger to Wikisourcerers to do more with
>> Wikidata items>> 
>> On Wed, Nov 1, 2017 at 10:01 AM, Sam Wilson
>> <s...@samwilson.id.au> wrote:>>> __
>>> Yup, still true. We do at least have a common goal of structured
>>> HTML, as defined by http://schema.org/CreativeWork>>> 
>>> It sounds like Tpt's scraper will do wonders, if a Wikisource
>>> just complies to that. I think that's one of the next steps we
>>> need to take.>>> 
>>> I sort of figure from the English Wikisource point of view that we
>>> should do more on bringing data *in* from Wikidata, in our
>>> {{header}}, rather than working on making it easier to extract data
>>> *out* with microformats/structured-HTML. Well, we should do both, of
>>> course! :-) But my feeling from the process of getting Author data
>>> in from Wikidata is that the whole Wikidata integration becomes so
>>> much more worthwhile and clearer (and we sort out the various edge
>>> cases) when we're actively using it for real.>>> 
>>> But of course, each Wikisource is in a similar position. :-( And are
>>> we to all be developing the Lua scripts and templates in isolation?
>>> Indeed no! :-) We shall put them all toegther in our brave new
>>> Wikisource extension! :)>>> 
>>> —sam
>>> 
>>> 
>>> 
>>> On Wed, 1 Nov 2017, at 04:03 PM, Andrea Zanni wrote:
>>>> @Sam, Tpt, 
>>>> my personal experience is too that HTML is the way to pull out the
>>>> Wikisource important metadata,>>>> but it's also that every Wikisource has 
>>>> sort of a different way to
>>>> show them,>>>> meaning that you need to tweak your scraper for each 
>>>> Wikisource. 
>>>> Is that still true? Last time I did it was more than one year ago,
>>>> but I need to try it again soon.>>>> Aubrey
>>>> 
>>>> On Wed, Nov 1, 2017 at 1:00 AM, Sam Wilson <s...@samwilson.id.au>
>>>> wrote:>>>>> Yes I think you're definitely right! The easier way to send
>>>>> Wikisource>>>>> data to Wikidata is going to be a clever gadget that 
>>>>> reads the
>>>>> microformat or schema'd info in each page. My hack was just a
>>>>> quick and>>>>> easy test at getting some things added. :)
>>>>> 
>>>>> Ultimately, I'm actually not that excited about working on the
>>>>> tools>>>>> that we need to transfer the data. No no I don't mean that! 
>>>>> Well,
>>>>> just>>>>> that the end point we're aiming at is that a bunch of info 
>>>>> *won't

Re: [Wikisource-l] wikisource "work" pages or "multiple editions" pages

[Sam Wilson]

I must admit, I'm not a huge fan of multiple namespaces in wikis.
They're mostly not necessary! :-) (Don't worry, I'm not suggesting
getting rid of any either.)
And certainly, from the point of view of integrating Wikidata and moving
towards better metadata and searchability, I don't think we need all
Wikisources to unify on any particular set of namespaces. I think any
future metadata system must just work with all the different current set-
ups (and I think it can, quite well).
—Sam.

On Thu, 2 Nov 2017, at 05:21 PM, Anika Born wrote:
> Billinghurst, 
> 
> That might work for me, with a Login. 
> 
> But does this also work for random readers, who don't have a login?
> Who don't know, that there are preferences (and especially what can be
> done with them?)> 
> But more important: please don't (just) focus in namespaces for every
> Wikisource-Project. You might loose at least de.WS. I can't see
> changing something, that works fine for this project...  Especially
> not to change a system, that is quite different, from what they have
> now. That is all I am asking for. de.ws is working with templates to
> differ, not with namespaces.> 
> for instance Johann Wolfgang von Goethe: [1]
> 
> Goethe was an author, but there are also works about Goethe. In de.ws
> portal-page and author-page about Geothe are merged in one. There is
> no difference. Don't expect something else.> 
> Best, Anika
> 
> 2017-11-02 9:07 GMT+01:00 billinghurst :
>> __
>> Anika,
>> 
>> That is matter long resolved in my opinion with the change in the
>> default search namespaces that the communities made, and similarly
>> with our redefining content namespaces. While main namespace will
>> always take preference to the other nss in results, they show up
>> pretty quickly where you have an intitle: match.>> 
>> At enWS I would say that we lost more searches to subpages, so with
>> the ability to change your search preferences with subphrase matches,
>> much of that is addressed (though it is not the default search
>> configuration at this point).>> 
>> The completion suggester[2] is an algorithm for search suggestions
>> with better typo correction and search relevance.>> 
>> Default (recommended)
>> Corrects up to two typos. Resolves close redirects.
>> 
>> Subphrase matching (recommended for longer page titles)
>> Corrects up to two typos. Resolves close redirects. Matches subphrase
>> in titles.>> 
>> Strict mode (advanced)
>> No typo correction. No accent folding. Strict matching.
>> 
>> Redirect mode (advanced)
>> No typo correction. Resolves close redirects.
>> 
>> Redirect mode with subphrase matching (advanced)
>> No typo correction. Resolves close redirects. Matches subphrase in
>> titles.>> 
>> Regards, Billinghurst
>> 
>> 
>> 
>> -- Original Message --
>> From: "Anika Born" 
>> To: "discussion list for Wikisource, the free library" > l...@lists.wikimedia.org>>> 
>> Sent: 2/11/2017 6:37:29 PM
>> Subject: Re: [Wikisource-l] wikisource "work" pages or "multiple
>> editions" pages>> 
>>> 2017-11-01 16:40 GMT+01:00 Nicolas VIGNERON
>>> : 
 
 
 From afar, the Opera: pages on it.ws are very close to the pages
 with the template {{Éditions}} on fr.ws or the template
 {{Versions}} on en.ws (and similar system elsewhere). 
 The main difference is having a separate namespace A second major
 difference is that the templates on fr.ws and en.ws are very light
 while the {{Opera}} template took data from Wikidata (but that's an
 independent problem, it's possible to change the  {{Éditions}} or
 {{Versions}} templates to do exactly the same thing without having
 a specific namespace). 
 I'm almost convinced too, but in order to create a new namespace on
 a project you have to convinced the local community. That's why I'm
 still playing the Devil's advocate role and want to learn about the
 inconvenients of this system>>> 
>>> A reason why there are no different namespaces for work-, edition-,
>>> author-, list- and other portal pages in de.ws is the ws-search.
>>> When you are looking for "Goethe" in the (simple) search (as readers
>>> may do) on WS, you might get to>>> * 
>>> https://de.wikisource.org/wiki/Tafellied,_zu_Goethe%E2%80%99s_Geburtstage
>>>   but not to>>> * 
>>> https://de.wikisource.org/wiki/Johann_Wolfgang_von_Goethe[3] with
>>>   all the interesting stuff, if that page was in another
>>>   namespace...>>> 
>>> So there was the desition to use templates (and categories) for
>>> these different kind of pages:
>>> https://de.wikisource.org/wiki/Wikisource:Seiten_zu_Autoren,_Texten,_Themen,_Listen>>>
>>>  
>>> I think German Wikisource Community won't give this up and switch to
>>> using multiple namespaces (besides Wikisource: and Page:namespace).>>> 
>>> Best 
>>> Anika
>> 
>> ___
>>  Wikisource-l mailing list
>> 

Re: [Wikisource-l] quickstatements for missing editions

[Sam Wilson]

Yup, still true. We do at least have a common goal of structured HTML,
as defined by http://schema.org/CreativeWork
It sounds like Tpt's scraper will do wonders, if a Wikisource just
complies to that. I think that's one of the next steps we need to take.
I sort of figure from the English Wikisource point of view that we
should do more on bringing data *in* from Wikidata, in our {{header}},
rather than working on making it easier to extract data *out* with 
microformats/structured-
HTML. Well, we should do both, of course! :-) But my feeling from the
process of getting Author data in from Wikidata is that the whole
Wikidata integration becomes so much more worthwhile and clearer (and we
sort out the various edge cases) when we're actively using it for real.
But of course, each Wikisource is in a similar position. :-( And are we
to all be developing the Lua scripts and templates in isolation? Indeed
no! :-) We shall put them all toegther in our brave new Wikisource
extension! :)
—sam



On Wed, 1 Nov 2017, at 04:03 PM, Andrea Zanni wrote:
> @Sam, Tpt, 
> my personal experience is too that HTML is the way to pull out the
> Wikisource important metadata,> but it's also that every Wikisource has sort 
> of a different way to
> show them,> meaning that you need to tweak your scraper for each Wikisource. 
> Is that still true? Last time I did it was more than one year ago, but
> I need to try it again soon.> Aubrey
> 
> On Wed, Nov 1, 2017 at 1:00 AM, Sam Wilson
> <s...@samwilson.id.au> wrote:>> Yes I think you're definitely right! The 
> easier way to send
>> Wikisource>>  data to Wikidata is going to be a clever gadget that reads the
>>  microformat or schema'd info in each page. My hack was just a
>>  quick and>>  easy test at getting some things added. :)
>> 
>>  Ultimately, I'm actually not that excited about working on the tools>>  
>> that we need to transfer the data. No no I don't mean that!
>>  Well, just>>  that the end point we're aiming at is that a bunch of info 
>> *won't
>>  be* at>>  all in Wikisource, but will be pulled from Wikidata, and so I
>>  am much>>  more interested in making better tools for working with the data 
>> in>>  Wikidata. :-) If you see what I mean.
>> 
>>  My idea with ws-search is that it will progressively pull more
>>  and more>>  data from Wikidata, and only resort to HTML scraping where the
>>  data is>>  missing from Wikidata. I'm attempting to encapsulate this logic
>>  in the>>  `wikisource/api` PHP library.
>> 
>> 
>> 
>> On Tue, 31 Oct 2017, at 11:14 PM, Thomas Pellissier Tanon wrote:
>>  > Hello Sam,
>>  >
>>  > Thank you for this nice feature!
>>  >
>>  > I have created a few months ago a prototype of Wikisource to
>>  > Wikidata>>  > importation tool for the French Wikisource based on the 
>> schema.org>>  > annotation I have added to the main header template (I 
>> definitely
>>  > think>>  > we should move from our custom microformat to this schema.org
>>  > markup that>>  > could be much more structured). It's not yet ready but I 
>> plan to
>>  > move it>>  > forward in the coming weeks. A beginning of frontend to add 
>> to
>>  > your>>  > Wikidata common.js is here:
>>  > https://www.wikidata.org/wiki/User:Tpt/ws2wd.js
>>  > We should probably find a way to merge the two projects.
>>  >
>>  > Cheers,
>>  >
>>  > Thomas
>>  >
>>  > > Le 31 oct. 2017 à 15:10, Nicolas VIGNERON
>>  > > <vigneron.nico...@gmail.com> a écrit :>>  > >
>>  > > 2017-10-31 13:16 GMT+01:00 Jane Darnell <jane...@gmail.com>:
>>  > > Sorry, I am much more of a Wikidatan than a Wikisourcerer! I was
>>  > > referring to items like this one>>  > > 
>> https://www.wikidata.org/wiki/Q21125368
>>  > >
>>  > > No need to be sorry, that is actually a good question and this
>>  > > example is even better (I totally forgot this kind of case).>>  > >
>>  > > For now, this is probably better to deal with it by hands (and
>>  > > I'm not sure what this tools can even do for this).>>  > >
>>  > > Cdlt, ~nicolas
>>  > > ___
>>  > > Wikisource-l mailing list
>>  > > Wikisource-l@lists.wikimedia.org
>>  > > https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>  >
>>  > ___
>>  > Wikisource-l mailing list
>>  > Wikisource-l@lists.wikimedia.org
>>  > https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>> > Email had 1 attachment:
>>  > + signature.asc
>>  >   1k (application/pgp-signature)
>> 
>> 
>> ___
>>  Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Hangout session

[Sam Wilson]

Great idea! I'm up for this Saturday.


On Wed, 1 Nov 2017, at 03:03 AM, Nicolas VIGNERON wrote:
> Hi everyone,
> From January to April of this year, we had hangout session to talk
> more directly about Wikisource (see
> https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group#2017
> for the notes of these sessions).> 
> Among subjects that can be discuss:
> - Wikisource and Wikidata (and some infos about the WikidataCon in
>   Berlin last weekend)> - a second Wikisource conference in 2018 ?
> - various issues or accomplishments you want to share or need help
>   from others> - the Wikisource Community User Group
> 
> What do you think of doing this again? Who would be interested to
> join? (it was during week-end - Saturday or Sunday - afternoon to
> allow people from all other the globe to join in, I suggest Saturday 4
> from 14:00 UTC to 15:00 UTC
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=November+Wikisource+Hangout=2017-11-04T14:00:00).>
>  
> Cdlt, ~nicolas
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] quickstatements for missing editions

[Sam Wilson]

And I guess that's independent of the actual titles of the editions? I
mean, different editions could have different titles, but you'd still
list them all on the same Opera page?
So, if we were focusing only on pages that are not yet linked to
Wikidata, for Italian it'd be easy in that anything in mainspace is an
edition, is that right?
Does Italian have a Category:Mainspace disambiguation pages (Q26961321)?

On Wed, 1 Nov 2017, at 01:45 AM, Andrea Zanni wrote:
> For the "work" concept, Italian Wikisource decided to create a real
> and new namespace, "Opera" (which means work).> It's the one page where we 
> store the links to multiple editions of a
> certain book we have.> 
> It's not a disambiguation page in the sense that a disambiguation page
> works with different books from different authors with the same title> e.g. 
> "Poems"...
> Aubrey
> 
> On Tue, Oct 31, 2017 at 4:17 PM, Thomas Pellissier Tanon  tanon.fr> wrote:>> An other point: here is a link to your 'Wikidata project" 
> on the
>> french Wikisource. We plan to build here to document what we do
>> around Wikisource:
>> https://fr.wikisource.org/wiki/Wikisource:Projet_Wikidata>> 
>> Sorry for the spam,
>> 
>> Cheers,
>> 
>> Thomas
>> 
>> 
>> > Le 31 oct. 2017 à 16:14, Thomas Pellissier Tanon > > tanon.fr> a écrit :>> >
>> > Hello Sam,
>> >
>> > Thank you for this nice feature!
>> >
>> > I have created a few months ago a prototype of Wikisource to
>> > Wikidata importation tool for the French Wikisource based on the
>> > schema.org annotation I have added to the main header template (I
>> > definitely think we should move from our custom microformat to this
>> > schema.org markup that could be much more structured). It's not yet
>> > ready but I plan to move it forward in the coming weeks. A
>> > beginning of frontend to add to your Wikidata common.js is here:
>> > https://www.wikidata.org/wiki/User:Tpt/ws2wd.js>> > We should probably 
>> > find a way to merge the two projects.
>> >
>> > Cheers,
>> >
>> > Thomas
>> >
>> >> Le 31 oct. 2017 à 15:10, Nicolas VIGNERON
>> >>  a écrit :>> >>
>> >> 2017-10-31 13:16 GMT+01:00 Jane Darnell :
>> >> Sorry, I am much more of a Wikidatan than a Wikisourcerer! I was
>> >> referring to items like this one>> >> 
>> >> https://www.wikidata.org/wiki/Q21125368
>> >>
>> >> No need to be sorry, that is actually a good question and this
>> >> example is even better (I totally forgot this kind of case).>> >>
>> >> For now, this is probably better to deal with it by hands (and I'm
>> >> not sure what this tools can even do for this).>> >>
>> >> Cdlt, ~nicolas
>> >> ___
>> >> Wikisource-l mailing list
>> >> Wikisource-l@lists.wikimedia.org
>> >> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>> >
>> > ___
>> > Wikisource-l mailing list
>> > Wikisource-l@lists.wikimedia.org
>> > https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>> 
>> 
>> ___
>> Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>> 
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] quickstatements for missing editions

[Sam Wilson]

On Tue, 31 Oct 2017, at 04:04 PM, Nicolas VIGNERON wrote:
> 2017-10-31 5:21 GMT+01:00 Sam Wilson <s...@samwilson.id.au>:
>> I've just been experimenting with adding a quick-statements generator to
>>  https://tools.wmflabs.org/ws-search — search for something, with 'linked
>>  to wikidata = no', and then each row of the results has a popup with
>>  code you can copy and paste into quickstatements.
>>  
>>  I don't know if that sort of thing is useful. It's not working with many
>>  fields yet, but I'm finding it faster than entering the basics manually.
>>  
>>  —sam.
> 
> Interesting.
> 
> It's a good start but I see a lot of things that need heavy improvements. I 
> tried for br and fr Wikisources.
> 
> Most importantly not everything on Wikisource is an edition (there is 
> disambig page and editions pages, for instance fr:s:Accroupissements a a work 
> not an edition, it should detect that and change the P31 accordingly)
> Then the description is put on « Dfr  "edition of Accroupissements by , 
> Arthur Rimbaud" », it should be Den not Dfr, there shouldn't be a comma here, 
> and ideally we should add description in multiple languages (maybe with an 
> external bot ?).
> Some others data could probably easily be added 
> (P996[https://www.wikidata.org/wiki/Property:P996] and 
> P1957[https://www.wikidata.org/wiki/Property:P1957] at least and maybe 
> P1476[https://www.wikidata.org/wiki/Property:P1476] too)
> 

Yes it's certainly a first draft!! :-) Thanks for trying it out.

With the disambig pages, can you suggest how to detect them?

Ah, there's a couple of other bugs here:

The page https://fr.wikisource.org/wiki/Accroupissements actually
already has a WIkidata ID, but the ws-search database didn't know about
it :-( probably because it was failing for a while on some weird
problems. I've re-run the scraper, and now that work is showing up with
it's proper Q-number:
https://tools.wmflabs.org/ws-search/?title=Accroupissements==fr

The idea with the quickstatements is that it'll only show it for works
that are *not yet* linked to wikidata. This is where the disambig
problem comes in, because there doesn't seem to be a simple way to
determine what's an edition and what's a work without resorting to
Wikidata. We could look at categories? Is it a truth universally
acknowledged that pages in the categories defined as
https://www.wikidata.org/wiki/Q15939659 are all disambiguation pages?
That could work... 

:-) Thanks again! I'll fix up the i18n stuff. The tool isn't doing
anything at all yet, but I could register it on translatewiki if it's
thought to be useful enough?

—sam

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] quickstatements for missing editions

[Sam Wilson]

I've just been experimenting with adding a quick-statements generator to
https://tools.wmflabs.org/ws-search — search for something, with 'linked
to wikidata = no', and then each row of the results has a popup with
code you can copy and paste into quickstatements.

I don't know if that sort of thing is useful. It's not working with many
fields yet, but I'm finding it faster than entering the basics manually.

—sam.

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] IA Upload download feature

[Sam Wilson]

There's a new column on the IA Upload
https://tools.wmflabs.org/ia-upload/ log to permit the download of the
DjVu files, for those files that are failing to upload to Commons. This
is just a work-around until we have larger-file uploading fixed (which
should be soon, see https://phabricator.wikimedia.org/T175680 for more
info).

—Sam


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Proposal

[Sam Wilson]

Sorry, Sam, the other thing I meant to say was: that's a brilliant idea!
:-) I'd love to help make it happen, if I can be of any use. :)

On Thu, 12 Oct 2017, at 08:51 PM, Sam Wilson wrote:
> It's slightly tricky at the moment to extract data for validated
> works, for one because we don't have solid data linking Index pages to
> their corresponding main namespace (i.e. "work") pages. The Index
> pages have the status, but the mainspace pages are what we think of as
> the work. There's P1957 now, which is the connextion we need, but the
> data for that isn't complete.> 
> We've also got (incomplete) support for OPDS in the wsexport tool,
> which I think is probably a brilliant way forward for sharing the
> Wikisource catalogue with other systems. Once we have better
> structural support in Wikisource itself (e.g. structured data for
> querying validation status) then we'll much more efficiently and
> easily be able to produce all sorts of output for sharing.> 
> 
> On Thu, 12 Oct 2017, at 08:37 PM, Sam Walton wrote:
>> Hi all,
>> 
>> I work on the Wikipedia Library program, and wanted to jump in with a
>> passing thought I'd had about Wikisource and TWL. We'll be building
>> search and discovery tools into the library card platform
>> (https://wikipedialibrary.wmflabs.org/) that's currently under
>> ongoing development. They'll index all the usually-paywalled
>> resources we have access to, but also open access content. As part of
>> that process it's a desire of mine to index completed Wikisource
>> works, though I haven't given it much thought beyond 'that would be
>> nice'. This might be able to function as a kind of centralised search
>> for all completed Wikisource works, if implemented.>> 
>> If you're interested, the relevant Phab task is
>> https://phabricator.wikimedia.org/T169875, where your thoughts are
>> very welcome. It won't be worked on for a while and I can't guarantee
>> that it will definitely happen, but if it's something the Wikisource
>> community would benefit from, then that would absolutely increase the
>> likelihood we'll work on it.>> 
>> Best,
>> Sam
>> 
>> On 12 October 2017 at 13:07, Federico Leva (Nemo)
>> <nemow...@gmail.com> wrote:>>> Gerard Meijssen, 12/10/2017 15:04:
>>>> Given the discussion about finished books on the Korean Wikisource,
>>>> I this demonstrates that we really need to advertise the finished
>>>> books to a reading public.>>>
>>> In Italy, after many years of talk with local libraries, the
>>> Wikisource books are included in the catalogs of many libraries
>>> (also via a local ebook provider, MLOL, who hired some wikimedians
>>> to work on the "open collection", big kudos to them).>>> 
>>> Nemo
>>> 
>>> ___
>>> Wikisource-l mailing list
>>> Wikisource-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>> 
>> 
>> 
>> -- 
>> Sam Walton
>> Partnerships Coordinator
>> The Wikipedia Library
>> 
>> s...@wikipedialibrary.org / swal...@wikimedia.org
>> _
>> Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> 
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Proposal

[Sam Wilson]

It's slightly tricky at the moment to extract data for validated works,
for one because we don't have solid data linking Index pages to their
corresponding main namespace (i.e. "work") pages. The Index pages have
the status, but the mainspace pages are what we think of as the work.
There's P1957 now, which is the connextion we need, but the data for
that isn't complete.
We've also got (incomplete) support for OPDS in the wsexport tool, which
I think is probably a brilliant way forward for sharing the Wikisource
catalogue with other systems. Once we have better structural support in
Wikisource itself (e.g. structured data for querying validation status)
then we'll much more efficiently and easily be able to produce all sorts
of output for sharing.

On Thu, 12 Oct 2017, at 08:37 PM, Sam Walton wrote:
> Hi all,
> 
> I work on the Wikipedia Library program, and wanted to jump in with a
> passing thought I'd had about Wikisource and TWL. We'll be building
> search and discovery tools into the library card platform
> (https://wikipedialibrary.wmflabs.org/) that's currently under ongoing
> development. They'll index all the usually-paywalled resources we have
> access to, but also open access content. As part of that process it's
> a desire of mine to index completed Wikisource works, though I haven't
> given it much thought beyond 'that would be nice'. This might be able
> to function as a kind of centralised search for all completed
> Wikisource works, if implemented.> 
> If you're interested, the relevant Phab task is
> https://phabricator.wikimedia.org/T169875, where your thoughts are
> very welcome. It won't be worked on for a while and I can't guarantee
> that it will definitely happen, but if it's something the Wikisource
> community would benefit from, then that would absolutely increase the
> likelihood we'll work on it.> 
> Best,
> Sam
> 
> On 12 October 2017 at 13:07, Federico Leva (Nemo)
>  wrote:>> Gerard Meijssen, 12/10/2017 15:04:
>>> Given the discussion about finished books on the Korean Wikisource,
>>> I this demonstrates that we really need to advertise the finished
>>> books to a reading public.>>
>> In Italy, after many years of talk with local libraries, the
>> Wikisource books are included in the catalogs of many libraries (also
>> via a local ebook provider, MLOL, who hired some wikimedians to work
>> on the "open collection", big kudos to them).>> 
>>  Nemo
>> 
>>  ___
>>  Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> 
> 
> 
> -- 
> Sam Walton
> Partnerships Coordinator
> The Wikipedia Library
> 
> s...@wikipedialibrary.org / swal...@wikimedia.org
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Validated works on kowikisource?

[Sam Wilson]

Nope. The validation-status data is unlikely to ever be in Wikidata.
The tool below gets this information from category-membership of
Index pages.

On Thu, 12 Oct 2017, at 01:18 PM, Gerard Meijssen wrote:
> Hoi,
> Is there a query in Wikidata for all the validated and complete books
> in Wikisource?> Thanks,
>   GerardM
> 
> On 12 October 2017 at 06:14, Sam Wilson <s...@samwilson.id.au> wrote:
>> > No validated works found for ko
>> 
>>  The ws-cat-browser is saying it can't find any validated and
>>  categorized>>  mainspace works on kowikisource.
>> 
>>  Is this correct? Is there any meant to be anything in the
>>  validated-index category?
>> https://ko.wikisource.org/wiki/%EB%B6%84%EB%A5%98:%EA%B2%80%EC%A6%9D%EB%90%9C_%EC%83%89%EC%9D%B8>>
>>  
>>  Thanks,
>>  Sam.
>> 
>>  ___
>>  Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Validated works on kowikisource?

[Sam Wilson]

> No validated works found for ko

The ws-cat-browser is saying it can't find any validated and categorized
mainspace works on kowikisource.

Is this correct? Is there any meant to be anything in the
validated-index category?
https://ko.wikisource.org/wiki/%EB%B6%84%EB%A5%98:%EA%B2%80%EC%A6%9D%EB%90%9C_%EC%83%89%EC%9D%B8

Thanks,
Sam.

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] [Offline-l] FYI - WMF pausing and deprecating some functionality

[Sam Wilson]

Yes, I think Nicolas is right. OCG has never really done what Wikisource
needed, and WsExport has (wonderfully). It would of course be brilliant
if the new PDF & epub generation could support Wikisource, but it not
doing so is no different from the existing situation.
On Wed, 11 Oct 2017, at 05:01 PM, Nicolas VIGNERON wrote:
> Hi everyone, 
> Maybe I'm misunderstood the situation but I'm not sure to understand
> the problem: does anyone use OCG?> I thought that not one use it anymore (if 
> it was ever used... at least
> onf the French wikisource it never really worked well as it didn't
> understand the 'pages' tag we use on almost all pages) and we have our
> own PDF/ePub/mobi generator
> (https://tools.wmflabs.org/wsexport/tool/book.php). SO don't we all
> use WSexport?> 
> I see very few pages on
> https://en.wikisource.org/w/index.php?title=Special:PrefixIndex=Wikisource:Books/
> , most of them generated a long time ago, so I don't think that this
> will have any impact on Wikisource.> 
> Cdlt, ~nicolas
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] IA Upload queue

[Sam Wilson]

Ah yes!

So I think we just need to make ia-upload be better. :-)

https://www.mediawiki.org/wiki/API:Upload#Chunked_uploading


On Tue, 12 Sep 2017, at 08:17 PM, Nicolas VIGNERON wrote:
> 2017-09-12 14:07 GMT+02:00 Yann Forget :
>> Hi,
>> 
>> The upload limit on Commons is 4 GB, so there should be any issue.
>> If the script can't upload files bigger than 100 MB, it should
>> be fixed.>> See how other tools work, as an example (i.e. video2commons).
> 
> 100 MB is the « regular » limit.
> 4 GB is the limit for chunked upload :
> https://commons.wikimedia.org/wiki/Commons:Chunked_uploads (it's end
> on the same place but it's not the same system)> 
> Cdlt, ~nicolas
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] IA Upload queue

[Sam Wilson]

Oh right! I'm behind the times for sure. :-)

I guess it's because we don't support multi-part uploads then? Each
chunk must be smaller than some amount?
New bug now at: https://phabricator.wikimedia.org/T175680


On Tue, 12 Sep 2017, at 08:07 PM, Yann Forget wrote:
> Hi,
> 
> The upload limit on Commons is 4 GB, so there should be any issue.
> If the script can't upload files bigger than 100 MB, it should
> be fixed.> See how other tools work, as an example (i.e. video2commons).
> 
> Regards,
> 
> Yann
> 
> 
> 2017-09-12 14:03 GMT+02:00 Sam Wilson <s...@samwilson.id.au>:
>> __
>> Yes, this happens when the resultant DjVu file is larger than Commons
>> will allow. I think 100 MB is the limit?>> 
>> I'm not sure how to get around this. Perhaps we resize the images
>> smaller? But we don't want to do that every time, so perhaps we have
>> to generate the DjVu, see how big it is, and if it's too big resize
>> and build it again? Would that work?>> 
>> We could make the over-size DjVu available for download, and then the
>> user could use a different method to upload to Commons (is there such
>> a method?).>> 
>> Suggestions welcome!
>> 
>> A related issue is https://phabricator.wikimedia.org/T161396
>> I can't find a ticket yet for the request-too-large problem, but I
>> remember seeing one; anyway, I'll create it again, and perhaps
>> Community Tech can look into it.>> 
>> There's also the slight possibility that IA can start creating DjVus
>> again! Which would be brilliant, but I haven't heard anything about
>> that since Wikimania.>> 
>> —Sam.
>> 
>> 
>> On Tue, 12 Sep 2017, at 04:47 PM, Ilario Valdelli wrote:
>>> [2017-08-02 08:00:49] LOG.CRITICAL: Client error: `POST
>>> https://commons.wikimedia.org/w/api.php` resulted in a `413 Request
>>> Entity Too Large` response:  413 Request Entity
>>> Too Large  413
>>> Request Entity (truncated...)  [] []>>>  


>>> Or the program is not able to process huge files or, simply, the
>>> disk space is finished.>>>  


>>> Kind regards


>>>  


>>> Sent from Mail[1] for Windows 10


>>>  


>>> *From: *Andrea Zanni[2] *Sent: *12 September 2017 10:37 *To:
>>> *discussion list for Wikisource, the free library[3] *Subject: *[Wikisource-
>>> l] IA Upload queue>>>  


>>> Dear all,


>>> someone could help understand if we have an issue here?
>>> https://tools.wmflabs.org/ia-upload/commons/init>>> Some librarians 
>>> uploaded books months ago,


>>> but they were never processed.


>>> Is the tool working, or it simply never signals when it fails?


>>>  


>>> 
>>>  
>>> Mail priva di virus. www.avast.com[4]
>>> 
>>> _
>>> Wikisource-l mailing list
>>> Wikisource-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>> 
>> 
>> ___
>>  Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>> 
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


Links:

  1. https://go.microsoft.com/fwlink/?LinkId=550986
  2. mailto:zanni.andre...@gmail.com
  3. mailto:wikisource-l@lists.wikimedia.org
  4. 
https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] IA Upload queue

[Sam Wilson]

Yes, this happens when the resultant DjVu file is larger than Commons
will allow. I think 100 MB is the limit?
I'm not sure how to get around this. Perhaps we resize the images
smaller? But we don't want to do that every time, so perhaps we have to
generate the DjVu, see how big it is, and if it's too big resize and
build it again? Would that work?
We could make the over-size DjVu available for download, and then the
user could use a different method to upload to Commons (is there such
a method?).
Suggestions welcome!

A related issue is https://phabricator.wikimedia.org/T161396
I can't find a ticket yet for the request-too-large problem, but I
remember seeing one; anyway, I'll create it again, and perhaps Community
Tech can look into it.
There's also the slight possibility that IA can start creating DjVus
again! Which would be brilliant, but I haven't heard anything about that
since Wikimania.
—Sam.


On Tue, 12 Sep 2017, at 04:47 PM, Ilario Valdelli wrote:
> [2017-08-02 08:00:49] LOG.CRITICAL: Client error: `POST
> https://commons.wikimedia.org/w/api.php` resulted in a `413 Request
> Entity Too Large` response:  413 Request Entity Too
> Large  413 Request
> Entity (truncated...)  [] []>  


> Or the program is not able to process huge files or, simply, the disk
> space is finished.>  


> Kind regards


>  


> Sent from Mail[1] for Windows 10


>  


> *From: *Andrea Zanni[2] *Sent: *12 September 2017 10:37 *To:
> *discussion list for Wikisource, the free library[3] *Subject: *[Wikisource-
> l] IA Upload queue>  


> Dear all,


> someone could help understand if we have an issue here?
> https://tools.wmflabs.org/ia-upload/commons/init> Some librarians uploaded 
> books months ago,


> but they were never processed.


> Is the tool working, or it simply never signals when it fails?


>  


> 
>  
> Mail priva di virus. www.avast.com[4]
> 
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


Links:

  1. https://go.microsoft.com/fwlink/?LinkId=550986
  2. mailto:zanni.andre...@gmail.com
  3. mailto:wikisource-l@lists.wikimedia.org
  4. 
https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Proofread status colour buttons

[Sam Wilson]

Seems like it's a widespread problem! :-(

The bug is being tracked here: https://phabricator.wikimedia.org/T175304

On Fri, 8 Sep 2017, at 07:10 AM, Bodhisattwa Mandal wrote:
> Hi,
> 
> The proofread status colour buttons in normal edit mode are not
> appearing in Wikisource projects for last few hours.> 
> Any idea, what's happening?
> 
>  
> 
> 
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Twitter

[Sam Wilson]

Hi all,

There's been some discussion at
https://en.wikisource.org/wiki/Wikisource_talk:WikiProject_Social_media#Twitter
about the @wikisource Twitter account (and others).

I've just been made a team member of @wikisource, and we should add some
more people too.

The idea is that @wikisource is the cross-Wikisource account, and each
language Wikisource can also have its own account (e.g. @wikisource_fr
@wikisource_de, etc. ­here's a list I started this morning:
https://twitter.com/wikisource/lists/wikisources/members are there any
others?)

So, who wants to be added, and what are your Twitter usernames?

We'll also have @wikisource_en later today or tomorrow; same deal.

The passwords for these accounts are held by Aubrie Johnson, the WMF
social media person.

Thanks,
Sam.

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] QR Codes for Wikisource texts

[Sam Wilson]

I have done this sort of thing (once only, but it was useful I think). It was a 
report in the local library, that is now on Wikisource, and I slipped a single 
loose leaf into the front of it that explained that a digital version was 
available on Wikisource and what address to find it at. That would have been a 
good place to have a QR code. (Although, it's also a use case that would is 
served by those library catalogues that permit user annotations, such as 
http://trove.nla.gov.au/newspaper/article/27433064 .)
As for redirecting to Wikisource based on a QR code, I have an inkling that 
User:Pigsonthewing and User:Gnangarra were talking recently about a 
Wikidata-based QRpedia system, that would embed the Wikidata ID into the QR 
code rather than the Wikipedia page name. Then, the qrpedia software would 
redirect to the relevant language Wikipedia based on the sitelinks. I imagine 
that this software (and I'm not sure it exists beyond planning stage yet) would 
pretty easily be able to instead redirect to Wikisource or any other project.
—Sam

On Fri, 7 Jul 2017, at 01:38 PM, Ilario Valdelli wrote:
> In all of your discussion I have not undertood why someone should go to the 
> library to have a qrcode while it is available online.> 
> Kind regards
> 
> On 7 Jul 2017 07:22, "Bodhisattwa Mandal"  
> wrote:>> Hi,


>> There has been significant decline in library readerships in India. 
>> Libraries are remaining almost empty throughout the day. I believe, that is 
>> because, with the increasing usage of internet, there has been a change in 
>> behaviour about reading physical books. People are preferring to remain 
>> online and get information from the internet, rather than to stay in a 
>> library and study there. The libraries are not also coping with this 
>> scenario and not upgrading themselves, and losing readers.>> Also, the smart 
>> phone penetration in India is also increasing. It has been estimated almost 
>> one third of Indian citizens will use smart phone by 2019 and that's a huge 
>> number. Nowadays, many people who do not have computers, have smartphones 
>> with cheaper internet than before. But many of them doesn't know how to 
>> search a book in internet, even if does find some book, tends to forget the 
>> urls, and unfortunately almost nobody knows anything about Wikisource, even 
>> from the academy.>> Now, if we have a QR code generation system for 
>> Wikisource, we can collaborate with the town libraries or college libraries, 
>> send them the codes and help them build a QR code library of books. They can 
>> give the codes to readers according to their demands, which will redirect 
>> them to Wikisource. We can also generate QR codes for every book we work on 
>> and upload them to Commons with a suitable title, creating a QR code library 
>> ourselves, thus making the codes google searchable and accessible to the 
>> readers. In every case, the viewership of the site will increase.>> Regards,


>> On Jul 7, 2017 7:52 AM, "Asaf Bartov"  wrote:>>> 
>> Certainly, this can be done.
>>> 
>>> Could you elaborate a little more about the use scenarios you are 
>>> imagining?>>> 
>>> A.
>>> 
>>> On Thu, Jul 6, 2017 at 5:32 AM Bodhisattwa Mandal 
>>>  wrote: Hi all,


 Can we create a Wikisource specific QR code generator tool for the NS0 
 pages? People often forget the urls or sometimes doesn't know the way 
 to search texts in Wikisource. If we can generate qr codes, that would 
 also benefit libraries from remote places or readers who don't have 
 computers in their possession . I think it will definitely increase 
 the viewership of the site to a significant amount.  What's your opinion 
 regarding this? Regards,
  Bodhisattwa


 ___
  Wikisource-l mailing list
 Wikisource-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>> 
>>> ___
>>>  Wikisource-l mailing list
>>> Wikisource-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>> 
>> 
>> ___
>>  Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>> 
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Budget for Wikisource

[Sam Wilson]

This is indeed a bug! I can't replicate it though. Does it happen for
every book for you? Or only sometimes? Do you know what is different
about the ones that fail? Is it related to removing (or not) the Google
cover page?
I can find time this weekend I think, to work on this.


On Fri, 30 Jun 2017, at 03:23 PM, Andrea Zanni wrote:
> Hello everyone, before talking again about this let me say that I
> think we have a "major" bug in the IA-upload:> sometimes, the OCR is not 
> aligned between the pages, meaning you have
> the right OCR but it's shown for the following page...> Aubrey
> 
> On Thu, May 11, 2017 at 1:30 AM, Sam Wilson
> <s...@samwilson.id.au> wrote:>> __
>> This is very cool news. :)
>> 
>> One possibly not-too-onerous feature would be to permit upload of
>> other file types other than DjVu (e.g. PDF). Or there's the whole
>> topic of creating/finding Wikidata items for the books uploaded, and
>> updating them with the IA identifier. That'd probably require the
>> uploading user to specify a Wikidata ID though — which is what the
>> {{book}} template on Commons should work from anyway, in my opinion
>> (because it can't be done via a sitelink).>> 
>> I'm very happy to help with whatever I can!
>> 
>> —sam
>> 
>> On Wed, 10 May 2017, at 09:38 PM, Andrea Zanni wrote:
>>> Dear all, 
>>> Wikimedia Italia put in its budget 3000€ for Wikisource-
>>> related work.>>> When we discussed this, months ago, we thought about 
>>> paying a
>>> developer for>>> the DJVU issue of the IA-Upload tool, 
>>> which then has been resolved by our beloved Sam Wilson. 
>>> 
>>> The tool is still not perfect (I often get errors), so maybe some
>>> development is still needed, but I'd ask you (especially technically
>>> skilled people like Tpt, Sam, Philippe, etc.) if you think there is
>>> some low-hanging fruit that could be reached with that kind of
>>> budget.>>> Of course, we will be looking for developers, so if you want to
>>> propose yourself for something, please do! ;-)>>> 
>>> Aubrey
>>> 
>>> _
>>> Wikisource-l mailing list
>>> Wikisource-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>> 
>> 
>> ___
>>  Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>> 
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Move IA Upload issue tracking to Phabricator

[Sam Wilson]

Hi all,

Does anyone mind if I copy all outstanding issues from
https://github.com/wikisource/ia-upload/issues to the IA Upload column
on the Wikisource Phabricator board
https://phabricator.wikimedia.org/tag/wikisource/ ?

It just seems nicer to have everything on one place, and Phab seems
better for that because then I can get things seen to within Community
Tech.

@Tpt, I know we spoke about this once, but I can't remember what we
decided.

Thanks,
Sam.

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Budget for Wikisource

[Sam Wilson]

This is very cool news. :)

One possibly not-too-onerous feature would be to permit upload of other
file types other than DjVu (e.g. PDF). Or there's the whole topic of
creating/finding Wikidata items for the books uploaded, and updating
them with the IA identifier. That'd probably require the uploading user
to specify a Wikidata ID though — which is what the {{book}} template on
Commons should work from anyway, in my opinion (because it can't be done
via a sitelink).
I'm very happy to help with whatever I can!

—sam

On Wed, 10 May 2017, at 09:38 PM, Andrea Zanni wrote:
> Dear all, 
> Wikimedia Italia put in its budget 3000€ for Wikisource-related work.> When 
> we discussed this, months ago, we thought about paying a
> developer for> the DJVU issue of the IA-Upload tool, 
> which then has been resolved by our beloved Sam Wilson. 
> 
> The tool is still not perfect (I often get errors), so maybe some
> development is still needed, but I'd ask you (especially technically
> skilled people like Tpt, Sam, Philippe, etc.) if you think there is
> some low-hanging fruit that could be reached with that kind of budget.> Of 
> course, we will be looking for developers, so if you want to
> propose yourself for something, please do! ;-)> 
> Aubrey
> 
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] IA-Upload (was: Budget for Wikisource)

[Sam Wilson]

Yeah, it's still not fixed for books of more than about 500 pages. :-(

But it's on my list to work on! Along with
https://phabricator.wikimedia.org/T159796, which hopefully will be
before the hackathon next week. I've been having some dramas with
getting JP2 things working on my new computer...

Unfortunately, at the moment, xtools is taking priority.

—sam

PS For and IA Upload bugs, feel free to add the community-tech tag in
Phabricator, so they get a bit more visibility.


On Thu, 11 May 2017, at 12:07 AM, Thomas PT wrote:
> Changing the topic as the conversation has diverged.
> 
> > Not sure how Sam and Tpt solved that issue.
> 
> It's not solved yet at my knowledge.
> 
> Thomas
> 
> > Le 10 mai 2017 à 18:03, Andrea Zanni  a écrit :
> > 
> > It may be.
> > Not sure how Sam and Tpt solved that issue.
> > 
> > Aubrey
> > 
> > On Wed, May 10, 2017 at 6:01 PM, Philippe Elie  wrote:
> > On Wed, 10 May 2017 at 18:00 +0200, Andrea Zanni wrote:
> > 
> > > >
> > > > There isn't also a trend when converting from jp2 --> pdf to produce
> > > > too big djvu?
> > > >
> > >
> > > May you please explain it better? I don't understand.
> > >
> > 
> > Aren't djvu produced often too big?
> > 
> > --
> > Phe
> > 
> > ___
> > Wikisource-l mailing list
> > Wikisource-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> 
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Scanner for you?

[Sam Wilson]

Wikimedia Australia (the western branch of it anyway) is about to start
a three-month residency at the State Library of Western Australia, and
we've got an office (which I'll be working from pretty much full time).
If it's a success, perhaps in a few months' time I'd love to be able to
put my hand up for WMAU to be custodians of a book scanner!
But probably postage to Australia would be too much. :-)

—Sam


On Mon, 8 May 2017, at 02:18 AM, Carles Paredes Lanau wrote:
> I'm writing to this list because we have got an scanner to share with
> any European chapter interested in working with institutions or for
> internal use of Wikimedia communities.> Amical Wikimedia purchased and 
> assembled The Archivist, DIY Book
> Scanner (http://diybookscanner.org/archivist/) in March 2015. We
> wanted to work with several partners from our GLAM network, to help
> them to free resources and scan documents previously not avaliable for
> general public. We began a pilot project in Maritime Museum of
> Barcelona, a museum with whom we had already worked in the past and
> with the proper mindset. We had a member from Amical working there as
> professional librarian, too, so it was easier to implement the
> project. We provided a volunteer to assist the museum in tech issues.
> You can check the books scanned in the following link:
> https://archive.org/details/bibliotecammb586. It was an interesting
> project with relevant results. However, we decided to discontinue it
> because it needed a close assistant we could no longer offer and
> people from the museum weren't comfortable working with it, since it
> was very different from the scanners they used in the past.> 
> That's why we want to offer the scanner to other Wikisource
> communities or to some chapter with volunteers wanting to continue
> digitalisation projects. If there's anyone interested in having a The
> Archivist model, please answer back this mail so we can discuss how to
> handle it.> 
> Thanks in advanced.
> 
> Carles Paredes (KRLS)
> Amical Wikimedia
>  
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] CREDIT showcase

[Sam Wilson]

That's a great idea! It needn't be too hard: if a bunch of us had a
current project to talk about for five minutes apiece, and we sent an
invite to wikimedia-l or somewhere big, it could be done don't you
think? Or maybe we just advertise our monthly hangouts more widely?


There's certainly  a lack of awareness about Wikisource within the
WMF, I think.


—Sam





On Thu, 30 Mar 2017, at 03:09 PM, Andrea Zanni wrote:

> Not sure if I can on Wednesday, but I'll think about it. 

> Also, a whole session about Wikisource would be very informative,
> I think,
> for a lot of people in WMF and inside our movement. 

> But it's much more difficult to do it, and get a whole session
> for you.
> Aubrey

> 

> On Thu, Mar 30, 2017 at 9:06 AM, Sam Wilson
> <s...@samwilson.id.au> wrote:
>> __

>> Good point, hmm. :) But yeah, I think it's worth it even if it's just
>> so people can see how much more work needs to be done. Unless it
>> fails... although, come to think of it: the demonstration could just
>> end with "see, it's in the queue, and it'll be processed later!" ;-)
>> Or is that cheating?
>> 

>> It's just meant to be a showcase of whatever's going on, not
>> necessarily finished polished things. (I think; I've only ever
>> watched one on youtube.)
>> 

>> If you don't feel like it, I think Kaldari will do it. But you'd be
>> great! :-)
>> 

>> 

>> —Sam

>> 

>> 

>> 

>> On Thu, 30 Mar 2017, at 02:58 PM, Andrea Zanni wrote:

>>> I can think about it, 

>>> but we should really "check" that IA Upload tool is failproof:

>>> last time I used it it failed quite a few times.

>>> Not a big deal, but not in a showcase ;-)

>>> On the other hand, this is maybe what we should show them:

>>> how much the Wikisource community relies on volunteer-developed 

>>> infrastructure (IA-upload, Proofread extension, Phe graphs)...

>>> Or it's a showcase of "the best" things in our community?

>>> Aubrey

>>> 

>>> 

>>> On Thu, Mar 30, 2017 at 6:20 AM, Sam Wilson <s...@samwilson.id.au>
>>> wrote:
>>>> Hi all,

>>>> 

>>>> Is anyone interested in presenting at the next CREDIT showcase
>>>> (next
>>>> week) https://www.mediawiki.org/wiki/CREDIT_showcase and
>>>> demonstrating
>>>> the IA Upload tool? It's a good opportunity to get some more
>>>> visibility
>>>> for Wikisource tools.

>>>> 

>>>> I'd do it, but it happens at 2 am my time.

>>>> 

>>>> If you're keen, put your name down at

>>>> https://etherpad.wikimedia.org/p/CREDIT

>>>> 

>>>> Thanks!

>>>> 

>>>> —Sam

>>>> 

>>>> ___

>>>> Wikisource-l mailing list

>>>> Wikisource-l@lists.wikimedia.org

>>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

>>> _

>>> Wikisource-l mailing list

>>> Wikisource-l@lists.wikimedia.org

>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

>> 

>> 

>> ___

>>  Wikisource-l mailing list

>> Wikisource-l@lists.wikimedia.org

>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

>> 

> _

> Wikisource-l mailing list

> Wikisource-l@lists.wikimedia.org

> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] CREDIT showcase

[Sam Wilson]

Good point, hmm. :) But yeah, I think it's worth it even if it's just
so people can see how much more work needs to be done. Unless it
fails... although, come to think of it: the demonstration could just
end with "see, it's in the queue, and it'll be processed later!" ;-) Or
is that cheating?


It's just meant to be a showcase of whatever's going on, not
necessarily finished polished things. (I think; I've only ever watched
one on youtube.)


If you don't feel like it, I think Kaldari will do it. But you'd be
great! :-)


—Sam





On Thu, 30 Mar 2017, at 02:58 PM, Andrea Zanni wrote:

> I can think about it, 

> but we should really "check" that IA Upload tool is failproof:

> last time I used it it failed quite a few times.

> Not a big deal, but not in a showcase ;-)

> On the other hand, this is maybe what we should show them:

> how much the Wikisource community relies on volunteer-developed 

> infrastructure (IA-upload, Proofread extension, Phe graphs)...

> Or it's a showcase of "the best" things in our community?

> Aubrey

> 

> 

> On Thu, Mar 30, 2017 at 6:20 AM, Sam Wilson
> <s...@samwilson.id.au> wrote:
>> Hi all,

>> 

>>  Is anyone interested in presenting at the next CREDIT showcase (next
>>  week) https://www.mediawiki.org/wiki/CREDIT_showcase and
>>  demonstrating
>>  the IA Upload tool? It's a good opportunity to get some more
>>  visibility
>>  for Wikisource tools.

>> 

>>  I'd do it, but it happens at 2 am my time.

>> 

>>  If you're keen, put your name down at

>> https://etherpad.wikimedia.org/p/CREDIT

>> 

>>  Thanks!

>> 

>>  —Sam

>> 

>>  ___

>>  Wikisource-l mailing list

>> Wikisource-l@lists.wikimedia.org

>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

> _

> Wikisource-l mailing list

> Wikisource-l@lists.wikimedia.org

> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] CREDIT showcase

[Sam Wilson]

Hi all,

Is anyone interested in presenting at the next CREDIT showcase (next
week) https://www.mediawiki.org/wiki/CREDIT_showcase and demonstrating
the IA Upload tool? It's a good opportunity to get some more visibility
for Wikisource tools.

I'd do it, but it happens at 2 am my time.

If you're keen, put your name down at
https://etherpad.wikimedia.org/p/CREDIT

Thanks!

—Sam

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] March hangout

[Sam Wilson]

Some notes from the hangout are now on:

https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/March_2017_Hangout
Tpt and Yann, can you add anything I've missed? :)



Next meeting scheduled for the same time Sunday April 30th, but if
anyone has a better time suggestion then feel free to raise it (it'd be
nice to include other timezones who maybe miss out because they don't
want to get up too early on a Sunday morning).


—sam



On Sat, 25 Mar 2017, at 12:08 AM, Nicolas VIGNERON wrote:

> 2017-03-24 17:01 GMT+01:00 Yann Forget :

>> Hi, Is there a log or a summary of last meeting?

>> 

>> Regards,

>> 

>> Yann

> 

> Here it is :
> https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/February_2017_Hangout
> Cdlt, ~nicolas

> PS: I'll try to be there but not 100% sure.

> _

> Wikisource-l mailing list

> Wikisource-l@lists.wikimedia.org

> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] March hangout

[Sam Wilson]

Sunday, 26 March 2017 at 12:00 (UTC) to 13:00 (UTC)
https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/March_2017_Hangout

Add things to to the list of things-to-talk-about, if you want to talk
about things. Or just come and talk about things.

:-)

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Feburary hangout

[Sam Wilson]

Just a reminder that this is in 4 hours.



:)





On Thu, 9 Feb 2017, at 03:16 PM, Sam Wilson wrote:

> 

> On Tue, 7 Feb 2017, at 03:41 PM, Nicolas VIGNERON wrote:

>> 2017-02-07 1:37 GMT+01:00 Sam Wilson <s...@samwilson.id.au>:

>>> Hi all,

>>> 

>>> Anyone up for another hangout this month?

>>> 

>>> How does Sunday 26 February 2017 at 12:00 UTC sound? Other
>>> suggestions?
>> 

>> Ok for me.

>> Cdlt, ~nicolas

> 

> 

> I've made a page for this:
> https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/February_2017_Hangout
> 

> Feel free everyone to add discussion items.

> 

> Thanks,

> Sam.

> _

> Wikisource-l mailing list

> Wikisource-l@lists.wikimedia.org

> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] IA Upload tool — higher-quality DjVus

[Sam Wilson]

That's a great idea!

I think we can use Wikidata to build the list:
http://tinyurl.com/zwdbzyq


I had been erroneously thinking along the lines that we'd have to be
uploading something to the items before making it part of a Wikisource
collection, but of course that's not necessary. I think your hierarchy
of wikisource collections sounds perfect.


It'd be cool if items with a page on a Wikisource could have a little
footnote like they do for Open Library ones ("[Open Library icon]This
book has an editable web page[1] on Open Library[2].).


—sam



On Sun, 12 Feb 2017, at 08:17 PM, Andrea Zanni wrote:

> Hi everyone, 

> I made this, hopefully is helful:

> https://docs.google.com/spreadsheets/d/158GvBrPBW0KfREHRmLFK7EhuB-FQBkLbm9qxJBaJTUY/edit?usp=sharing
> 

> It's the list of the files on Commons uploaded from Internet Archive.
> The idea, right now, is that every language Wikisource would take care
> of their uploads,
> and when they are more than 50 they create a "Italian/German/Bengali
> Wikisource",
> collection on Internet Archive. 

> The whole set of collections will be inside one "Wikisource" global
> collection.
> Make sense? Do you agree?

> 

> On Thu, Feb 9, 2017 at 8:38 AM, Sam Wilson
> <s...@samwilson.id.au> wrote:
>> __

>> 

>> 

>> On Thu, 9 Feb 2017, at 03:13 PM, Alex Brollo wrote:

>>> Thanks Sam! 

>>> Now we should focus on  help about requisites of a good, wikisource-
>>> oriented IA upload: proper scan quality, good file names and useful
>>> metadata. IMHO it would be great to build a "wikisource collection"
>>> into IA, since collection admins can edit any item detail but its
>>> ID, and fix most mistakes.
>>> 

>> 

>> 

>> That sounds like a great idea! So it sounds like[3] we need to have
>> 50 items already uploaded before they'll create a collection for us.
>> Then, maybe we build it into ia-upload: a way of uploading and
>> setting metadata for a set of scan files? It would upload files to IA
>> and then do the DjVu-creating thing and upload just the DjVu to
>> Commons?
>> 

>> Or do people upload to Commons first? And then our tool takes a file
>> (or category of files), uploads it to IA, and then pulls the DjVu
>> back from there and adds it to the same category?
>> 

>> (I'm sort of thinking aloud...)

>> 

>> 

>> 

>> ___

>>  Wikisource-l mailing list

>> Wikisource-l@lists.wikimedia.org

>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

>> 

> _

> Wikisource-l mailing list

> Wikisource-l@lists.wikimedia.org

> https://lists.wikimedia.org/mailman/listinfo/wikisource-l




Links:

  1. http://openlibrary.org/ia/thatremystre00gaut
  2. https://openlibrary.org/
  3. https://archive.org/about/faqs.php#Collections
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] IA Upload tool — higher-quality DjVus

[Sam Wilson]

On Thu, 9 Feb 2017, at 03:13 PM, Alex Brollo wrote:

> Thanks Sam! 

> Now we should focus on  help about requisites of a good, wikisource-
> oriented IA upload: proper scan quality, good file names and useful
> metadata. IMHO it would be great to build a "wikisource collection"
> into IA, since collection admins can edit any item detail but its ID,
> and fix most mistakes.
> 



That sounds like a great idea! So it sounds like[1] we need to have 50
items already uploaded before they'll create a collection for us. Then,
maybe we build it into ia-upload: a way of uploading and setting
metadata for a set of scan files? It would upload files to IA and then
do the DjVu-creating thing and upload just the DjVu to Commons?


Or do people upload to Commons first? And then our tool takes a file (or
category of files), uploads it to IA, and then pulls the DjVu back from
there and adds it to the same category?


(I'm sort of thinking aloud...)






Links:

  1. https://archive.org/about/faqs.php#Collections
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Feburary hangout?

[Sam Wilson]

On Tue, 7 Feb 2017, at 03:41 PM, Nicolas VIGNERON wrote:

> 2017-02-07 1:37 GMT+01:00 Sam Wilson <s...@samwilson.id.au>:

>> Hi all,

>> 

>>  Anyone up for another hangout this month?

>> 

>>  How does Sunday 26 February 2017 at 12:00 UTC sound? Other
>>  suggestions?
> 

> Ok for me.

> Cdlt, ~nicolas





I've made a page for this:
https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/February_2017_Hangout


Feel free everyone to add discussion items.



Thanks,

Sam.
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] IA Upload tool — higher-quality DjVus

[Sam Wilson]

This new feature is now live on the ia-upload tool:
http://tools.wmflabs.org/ia-upload/
Please raise any issues on Github:
https://github.com/wikisource/ia-upload/issues

The conversion process takes about 15 minutes for most books, it seems
like. (For books that already have DjVus at IA, it uploads them
immediately though.)

Thanks,
Sam.


On Thu, 2 Feb 2017, at 09:33 AM, Sam Wilson wrote:
> I've been tinkering with the ia-upload tool and incorporating Alex
> Brollo's better system of DjVu generation (better than converting from
> PDF, that is; instead it works from the original Jpeg2000 files and
> merges the OCR data in).
> 
> I've set up a test installation of the tool at
> http://tools.wmflabs.org/ia-upload/test/ and would love anyone to have a
> go at it, and to report any bugs at
> https://github.com/wikisource/ia-upload/issues
> 
> Because DjVu generation can take a while (quite a while if you've got a
> crappy slow laptop like me), the tool runs each job on the grid engine,
> starting every 5 minutes. The queue is shown on the homepage of the
> tool, with a status of each job. (Unless you're just re-using an
> existing DjVu file from the IA, in which case it's just uploaded
> directly to Commons while you wait, like the tool's always done.)
> 
> Thanks!

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Feburary hangout?

[Sam Wilson]

Hi all,

Anyone up for another hangout this month?

How does Sunday 26 February 2017 at 12:00 UTC sound? Other suggestions?

—sam

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Fwd: [Wikitech-l] Tech Talk: A Gentle Introduction to Wikidata for Absolute Beginners [including non-techies!]

[Sam Wilson]

This might be of interest to Wikisourcerors. (Apologies for
cross-posting.)

- Original message -
From: Rachel Farrand 
To: Wikimedia developers , Wikimedia
Mailing List 
Subject: [Wikitech-l] Tech Talk: A Gentle Introduction to Wikidata for
Absolute Beginners [including non-techies!]
Date: Fri, 3 Feb 2017 16:35:27 -0800

Please join for the following talk:

*Tech Talk**:* A Gentle Introduction to Wikidata for Absolute Beginners
[including non-techies!]
*Presenter:* Asaf Bartov
*Date:* February 09, 2017
*Time: *19:00 UTC

Link to live YouTube stream

*IRC channel for questions/discussion:* #wikimedia-office

*Summary: *This talk will introduce you to the Wikimedia Movement's
latest
major wiki project: Wikidata. We will cover what Wikidata is, how to
contribute, how to embed Wikidata into articles on other wikis, tools
like
the Wikidata Game, and how to query Wikidata (including SPARQL
examples).


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] IA Upload tool — higher-quality DjVus

[Sam Wilson]

I've been tinkering with the ia-upload tool and incorporating Alex
Brollo's better system of DjVu generation (better than converting from
PDF, that is; instead it works from the original Jpeg2000 files and
merges the OCR data in).

I've set up a test installation of the tool at
http://tools.wmflabs.org/ia-upload/test/ and would love anyone to have a
go at it, and to report any bugs at
https://github.com/wikisource/ia-upload/issues

Because DjVu generation can take a while (quite a while if you've got a
crappy slow laptop like me), the tool runs each job on the grid engine,
starting every 5 minutes. The queue is shown on the homepage of the
tool, with a status of each job. (Unless you're just re-using an
existing DjVu file from the IA, in which case it's just uploaded
directly to Commons while you wait, like the tool's always done.)

Thanks!

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Wikisource hangout next weekend

[Sam Wilson]

Thanks everyone for coming to the hangout!! It was great to talk about
all this. :-) 

I've attempted to clean up the etherpad notes:
https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/January_2017_Hangout#Notes
Please feel free to clarify anything I've mungled.

NEXT HANGOUT:

Shall we aim for some day on or near Sunday February 26th? Anyone got a
good suggestion of a time of day? Did 1400UTC work well enough?

—sam



On Sat, 28 Jan 2017, at 09:57 PM, Sam Wilson wrote:
> This is on now.
> 
> On Mon, 23 Jan 2017, at 11:56 AM, Sam Wilson wrote:
> > So it seems that most interested people can make it next Saturday at
> > 1400UTC, so I've created
> > https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/January_2017_Hangout
> > with some info.
> > 
> > —Sam
> > 
> > ___
> > Wikisource-l mailing list
> > Wikisource-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> 
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Wikisource hangout next weekend

[Sam Wilson]

This is on now.

On Mon, 23 Jan 2017, at 11:56 AM, Sam Wilson wrote:
> So it seems that most interested people can make it next Saturday at
> 1400UTC, so I've created
> https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/January_2017_Hangout
> with some info.
> 
> —Sam
> 
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] The conversion from PDF to DJVU loses too much quality

[Sam Wilson]

It's a pretty cool format. :)



I have got the beginnings of a PHP rewrite of your python script
running https://github.com/Tpt/ia-upload/pull/18 (but it's not at all
finished yet).


What is the best way to decrease the size of the jpgs before creating
the djvu? Just scale them to ~1000 px or something? How do you handle
that? (Sorry, I've read your code, but am confused...) I'm using
imagemagick to do it, so any transformation it can do is easy to
implement.


—Sam



On Fri, 27 Jan 2017, at 03:24 PM, Alex Brollo wrote:

> Yes, presently IA jp2.zip are the source files for all derived ones
> and for OCR. All the derived ones are omologous - t.i. *relative*
> coordinates of any element inside images are identical, even if image
> size varies. This means that mapping of elements (images or text) can
> be exported into any derived file.
> 

> Just an example: when an user crops an image from a djvu file by the
> excellent CropTool by Danmichaelo, coordinated of the cropping  could
> be used to crop high-resolution jp2 or jpg image, or to get
> coordinates of any piece of  text mapped by OCR.
> 

> Alex

> 

> 

> 

> 

> 

> 

> 

> 2017-01-27 0:53 GMT+01:00 Sam Wilson <s...@samwilson.id.au>:

>> __

>> Good to know, thanks!

>> 

>> So, we just stick with jp2.zip

>> 

>> And I love the IA magic :)

>> 

>> 

>> On Fri, 27 Jan 2017, at 07:40 AM, Andrea Zanni wrote:

>>> AFAIK, IA always produce the jp2 files by himself.

>>> I suggest GLAMs to upload zipped folders of jpegs, 

>>> so IA can do his magic and produce a book viewer and a PDF as well
>>> as the jp2.
>>> 

>>> On Fri, Jan 27, 2017 at 12:10 AM, Sam Wilson <s...@samwilson.id.au>
>>> wrote:
>>>> __

>>>> 

>>>> 

>>>> 

>>>> On Thu, 26 Jan 2017, at 06:35 PM, Andrea Zanni wrote:

>>>>> The problem for me is that librarians and other people who are
>>>>> genuinely interested in Wikisource and IA
>>>>> don't understand why

>>>>> * they upload a good scan on IA

>>>>> * see a good book on IA, via the viewer

>>>>> * get an horrible djvu on Wikisource. 

>>>>> 

>>>>> This is the issue we should try to solve, otherwise we will lose a
>>>>> potential important ally, content and new userbase.
>>>>> Aubrey

>>>>> 

>>>> 

>>>> 

>>>> Definitely!

>>>> 

>>>> On a related note: most (all?) IA-scanned books have e.g. *_jp2.zip
>>>> files containing all the original scan images, but is there any
>>>> standard for user-uploaded books? Like your librarians above, I
>>>> assume they're uploading individual jpg/png files? Do these get
>>>> combined into a single zip? I'm thinking that they don't, and that
>>>> ia-upload needs to provide the option of using any of the following
>>>> sources:
>>>>  * .djvu
>>>>  * _jp2.zip (there's also _jpg.zip and _raw_jp2.zip, but I guess we
>>>>don't need to use them?)
>>>>  * *.jpg + *.jp2 + *.png (i.e. use all images in the item, apart
>>>>from _cover_image.jpg)
>>>>  * .pdf
>>>> 

>>>> Sound complete? Or are there other ways?

>>>> 

>>>> ___

>>>> Wikisource-l mailing list

>>>> Wikisource-l@lists.wikimedia.org

>>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

>>>> 

>>> _

>>> Wikisource-l mailing list

>>> Wikisource-l@lists.wikimedia.org

>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

>> 

>> 

>> ___

>> Wikisource-l mailing list

>> Wikisource-l@lists.wikimedia.org

>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

>> 

> _

> Wikisource-l mailing list

> Wikisource-l@lists.wikimedia.org

> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] The conversion from PDF to DJVU loses too much quality

[Sam Wilson]

Good to know, thanks!



So, we just stick with jp2.zip



And I love the IA magic :)





On Fri, 27 Jan 2017, at 07:40 AM, Andrea Zanni wrote:

> AFAIK, IA always produce the jp2 files by himself.

> I suggest GLAMs to upload zipped folders of jpegs, 

> so IA can do his magic and produce a book viewer and a PDF as well as
> the jp2.
> 

> On Fri, Jan 27, 2017 at 12:10 AM, Sam Wilson
> <s...@samwilson.id.au> wrote:
>> __

>> 

>> 

>> 

>> On Thu, 26 Jan 2017, at 06:35 PM, Andrea Zanni wrote:

>>> The problem for me is that librarians and other people who are
>>> genuinely interested in Wikisource and IA
>>> don't understand why

>>> * they upload a good scan on IA

>>> * see a good book on IA, via the viewer

>>> * get an horrible djvu on Wikisource. 

>>> 

>>> This is the issue we should try to solve, otherwise we will lose a
>>> potential important ally, content and new userbase.
>>> Aubrey

>>> 

>> 

>> 

>> Definitely!

>> 

>> On a related note: most (all?) IA-scanned books have e.g. *_jp2.zip
>> files containing all the original scan images, but is there any
>> standard for user-uploaded books? Like your librarians above, I
>> assume they're uploading individual jpg/png files? Do these get
>> combined into a single zip? I'm thinking that they don't, and that
>> ia-upload needs to provide the option of using any of the following
>> sources:
>>  * .djvu
>>  * _jp2.zip (there's also _jpg.zip and _raw_jp2.zip, but I guess we
>>don't need to use them?)
>>  * *.jpg + *.jp2 + *.png (i.e. use all images in the item, apart from
>>_cover_image.jpg)
>>  * .pdf
>> 

>> Sound complete? Or are there other ways?

>> 

>> ___

>>  Wikisource-l mailing list

>> Wikisource-l@lists.wikimedia.org

>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

>> 

> _

> Wikisource-l mailing list

> Wikisource-l@lists.wikimedia.org

> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] The conversion from PDF to DJVU loses too much quality

[Sam Wilson]

On Thu, 26 Jan 2017, at 06:35 PM, Andrea Zanni wrote:

> The problem for me is that librarians and other people who are
> genuinely interested in Wikisource and IA
> don't understand why

> * they upload a good scan on IA

> * see a good book on IA, via the viewer

> * get an horrible djvu on Wikisource. 

> 

> This is the issue we should try to solve, otherwise we will lose a
> potential important ally, content and new userbase.
> Aubrey

> 



Definitely!



On a related note: most (all?) IA-scanned books have e.g. *_jp2.zip
files containing all the original scan images, but is there any standard
for user-uploaded books? Like your librarians above, I assume they're
uploading individual jpg/png files? Do these get combined into a single
zip? I'm thinking that they don't, and that ia-upload needs to provide
the option of using any of the following sources:
 * .djvu
 * _jp2.zip (there's also _jpg.zip and _raw_jp2.zip, but I guess we
   don't need to use them?)
 * *.jpg + *.jp2 + *.png (i.e. use all images in the item, apart from
   _cover_image.jpg)
 * .pdf


Sound complete? Or are there other ways?
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] The conversion from PDF to DJVU loses too much quality

[Sam Wilson]

Yann, do you mean you're getting good quality DjVu generated from the
PDF? Or from the original scan Jpegs?


Aubrey: when you say directly use the PDF, you mean for the tool to copy that 
across to Commons and not create a DjVu?


I can have a look at adding that feature perhaps? (Anyone else
working on this?)


—sam



On Wed, 25 Jan 2017, at 02:05 AM, Yann Forget wrote:

> Hi,

> 

> The quality of the result depends of paramaters.

> I use Abby FineReader, and I use the high quality possible, which
> gives good quality DjVu, but of high volume.
> It is always a trade-off between quality and volume.

> 

> Regards,

> 

> Yann

> 

> 2017-01-24 12:03 GMT+01:00 Andrea Zanni :

>> I added this issue to IA-upload tool on github:

>> https://github.com/Tpt/ia-upload/issues/14

>> Unfortunately, the new PDF > DJVU conversion is useless, as it loses
>> too much quality.
>> Can we find a solution?

>> The IA-Upload tool is a great asset for the whole international
>> community,
>> and it's very simple to teach librarians to upload stuff on IA and
>> then use it to port it on Commons and Wikisource.
>> But when they upload new stuff on IA, we don't have the IA djvu
>> anymore.
>> So the tool converts the original PDF to a new DJVU, and this is the
>> part of the process that is failing.
>> I can think of 2 solutions:

>> * integrate this script from Alex brollo into the tool:
>>   
>> https://it.wikisource.org/wiki/Progetto:Bot/Programmi_in_Python_per_i_bot/jp2todjvu.py
>> the script creates a good quality djvu

>> * have a toggle/top-down menu which allow the user to use directly
>>   the PDF.
>> 

>> 
>> Andrea

>> 

>> 

>> 

>> ___

>>  Wikisource-l mailing list

>> Wikisource-l@lists.wikimedia.org

>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

>> 

> _

> Wikisource-l mailing list

> Wikisource-l@lists.wikimedia.org

> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Wikiconference in Berlin

[Sam Wilson]

Okay, cool! How about the last week of January? Or is that too soon?
We'll know all the interesting things to come out of the MediaWiki Dev
Summit, which will be good to talk about.

Anyway, I made a doodle thing:
https://doodle.com/poll/g3svqgdmekmcy6tx
so at least maybe we can see how many people are interested?

(I've attempted to follow
https://meta.wikimedia.org/wiki/Best_practices_in_scheduling_a_meeting )


On Thu, 5 Jan 2017, at 06:49 PM, Andrea Zanni wrote:
> I really like the idea :-)

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Wikiconference in Berlin

[Sam Wilson]

That sounds brilliant. :-)



And yes, let's schedule a skype or google hangout (or whatever) for
before then. Actually, I reckon it'd be cool for Wikisource to have a
monthly hangout anyway... anyone into that? Some time like UTC1000 on
a weekend?


—sam





On Thu, 5 Jan 2017, at 05:47 PM, Andrea Zanni wrote:

> Hi Sam, 

> In the end, as the time was running out, (sunday is last day)

> I registered for the Strategy track and Ernest for the
> partnership one.
> 

> I really hope to speak with someone from your team, 

> and if you're available we can also discuss things together before the
> conference
> and during it (not sure if a skype call is possibile, but we
> could try).
> Aubrey

> 

> On Thu, Jan 5, 2017 at 1:46 AM, Sam Wilson
> <s...@samwilson.id.au> wrote:
>> __

>> Well I'm keen if there's a spare spot an no one more suitable
>> wants it!
>> 

>> On Wed, 4 Jan 2017, at 01:02 AM, Andrea Zanni wrote:

>>> Hi

>>> everyone. 

>>> I booked for myself one seat for the Strategy track (time is running
>>> out and, as far as I know, nobody proposed for it).
>>> There still available one seat for the "Capacity Building &
>>> Partnerships learning" track.
>>> Who wants it? Ernest? Sam? Nicholas? Others?

>>> 

>>> PS: Tpt will be present too!

>>> Aubrey 

>>> 

>>> On Fri, Dec 23, 2016 at 6:48 PM, Andrea Zanni
>>> <zanni.andre...@gmail.com> wrote:
>>>> Yes, 

>>>> but maybe they will come to the Wikiconf in another capacity, as
>>>> WIkimania organizers... Or not. If not, Ernest is perfect for the
>>>> Wikiconf.
>>>> 

>>>> On Fri, Dec 23, 2016 at 6:13 PM, Nicolas VIGNERON
>>>> <vigneron.nico...@gmail.com> wrote:
>>>>> Hi,

>>>>> Maybe we should ask Benoît or Ernest from WM CA who works on the
>>>>> excellent parternship with the National Library and Archives of
>>>>> Québec (BAnQ) and are always looking for ways to improve it.
>>>>> Cdlt, ~nicolas

>>>>> ___
>>>>>  Wikisource-l mailing list Wikisource-l@lists.wikimedia.org
>>>>>  https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>> _

>>> Wikisource-l mailing list

>>> Wikisource-l@lists.wikimedia.org

>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

>> 

>> 

>> ___

>>  Wikisource-l mailing list

>> Wikisource-l@lists.wikimedia.org

>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

>> 

> _

> Wikisource-l mailing list

> Wikisource-l@lists.wikimedia.org

> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Wikiconference in Berlin

[Sam Wilson]

Well I'm keen if there's a spare spot an no one more suitable wants it!


On Wed, 4 Jan 2017, at 01:02 AM, Andrea Zanni wrote:

> Hi

> everyone. 

> I booked for myself one seat for the Strategy track (time is running
> out and, as far as I know, nobody proposed for it).
> There still available one seat for the "Capacity Building &
> Partnerships learning" track.
> Who wants it? Ernest? Sam? Nicholas? Others?

> 

> PS: Tpt will be present too!

> Aubrey 

> 

> On Fri, Dec 23, 2016 at 6:48 PM, Andrea Zanni
>  wrote:
>> Yes, 

>> but maybe they will come to the Wikiconf in another capacity, as
>> WIkimania organizers... Or not. If not, Ernest is perfect for the
>> Wikiconf.
>> 

>> On Fri, Dec 23, 2016 at 6:13 PM, Nicolas VIGNERON
>>  wrote:
>>> Hi,

>>> Maybe we should ask Benoît or Ernest from WM CA who works on the
>>> excellent parternship with the National Library and Archives of
>>> Québec (BAnQ) and are always looking for ways to improve it.
>>> Cdlt, ~nicolas

>>> ___
>>>  Wikisource-l mailing list Wikisource-l@lists.wikimedia.org
>>>  https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> _

> Wikisource-l mailing list

> Wikisource-l@lists.wikimedia.org

> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Upload/import wizard

[Sam Wilson]

On Mon, 2 Jan 2017, at 05:29 PM, Andrea Zanni wrote:

> 

> Ideally, we should talk to IA about this. 

> Adding a comment on the IA item is a very low-cost solution and I
> think is important, adding the djvu would be much better. We should
> check if a script can edit every kind of item and add files (I
> think not).
> Aubrey
> 



Yes, good idea about talking to them.



I wonder about the workflow too, because what about the situation of
someone uploading a new work with our tool: the script creates a new
IA item then (I assume as the 'wikisource-import-tool' or whatever
user) and then it will have full permissions over that item. So the
update-DjVu scenario will only apply for IA items that already exist
but which don't have DjVu files (i.e. only the last few months'
worth). Which is good...


—sam




___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Wikiconference in Berlin

[Sam Wilson]

Hurrah! Yes, definitely someone should go. Johan Jönsson and Leon Ziemba
will be there from Community Tech, so I *think* that means I won't be
(even though I desperately would love to talk to more people about
Wikisource!). Perhaps that depends on what non-top-10 items from the
Wishlist Survey are to be worked on (and that's not clear quite yet). If
a Wikisource one (i.e. Han characters, or import-wizard; they're they
top-voted) is chosen, then perhaps I could come too.


Anyway, someone should be there representing Wikisource as well!



Would it be good to set up a meeting sometime (IRC or hangouts maybe)
to talk about things? I'm sure timezones etc. will be a problem, but
might be good.


—sam







On Tue, 20 Dec 2016, at 05:22 PM, Andrea Zanni wrote:

> Hello everyone, 

> and happy holidays :-)

> 

> As a User Group, we are eligible to send one member to the Wikimedia
> Conference in Berlin [1].
> I participated last year, and if I'm not mistaken Micru did in 2015.

> The conference is a place where the WMF, chapters and other affiliates
> gather to discuss many topics, and it's a great occasion for advocacy.
> I remember that last year I had the chance to sit with Danny Horn
> (from Community Tech team) for a whole hour to show him Wikisource
> stuff and issues. He told me they needed a new member of the team. Few
> months later, our own Sam Wilson was picked. Of course, that is all to
> Sam's credit (he's really good), but there is much more awareness in
> the WMF about Wikisource, and we are the ones who have to *build* that
> awareness. That conversation I had with Danny )among many others)
> helped, and so we gotta keep talking to people and explaining what
> Wikisource is.
> And our work is not finished. 

> Things are slowly improving, but we want them to improve more
> and faster.
> And we gotta check that there are improving constantly. 

> So this is why I think these gatherings are important.

> We have the chance to send one of us to Berlin: and we should have
> some candidates.
> Not sure how we should do it (maybe a "formal" election?) but the
> first thing is see how many of us are willing to go, so please reply
> to this mail and candidate yourself if you will.
> I'm available, and I'd like to go, but I also went last year, so we
> shall decide all together.
> 

> Aubrey

> 

> [1] 
> https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017/Eligibility_Criteria
> _

> Wikisource-l mailing list

> Wikisource-l@lists.wikimedia.org

> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Community Wishlist Survey 2016 - Voting period opened

[Sam Wilson]

Really good point, Aubrey. It makes lots of sense to build long-term
tools on Wikidata, because that's where Wikisource metadata (most of it)
will end up. The PMH proposal is in the Wikisource category, because we
rock — no I mean, because we need it most. But it should probably be
build with pulling as much data from Wikidata as it can. If an item gets
left out because it's missing some property in Wikidata, it's easy
enough to fix that. :-)


Oh, and the WS search tool[1] is currently still bombing out when it
tries to do full scrapes of some Wikisources (notably French, but that's
probably because of 'f's place in the alphabet rather than anything
else), so at the moment it's just running twice-daily scrapes on recent
changes on all Wikisources. I'm trying to make it more robust.


—sam



PS The current top-voted proposal (a WS upload wizard) is exciting!





On Wed, 30 Nov 2016, at 05:05 PM, Andrea Zanni wrote:

> Thanks for the reminder, just voted and commented. 

> I supported also the OAI-PMH proposal, 

> but I think it's not the solution, as we already have such a tool and
> nobody uses it...
> It's years (for me, an entire decade...) that we advocate and propose
> solutions for metadata workflow in Wikisource, and as far as I
> understand, a big part of it is Wikidata.
> 

> IMHO, we should try to put all our descriptive metadata (author,
> title, etc.) there, with a good, meaningful structure (we should
> understand which metadata are from the ns0 page, which from the Index
> pages, they are often different). Then, we could build APIs or other
> tools on that.
> WS search tool was a step in the right direction, but it's a difficult
> job and it should be a community effort.
> Aubrey

> 

> On Tue, Nov 29, 2016 at 11:30 PM, Sam Wilson
> <s...@samwilson.id.au> wrote:
>> __

>> And don't forget to vote for your own proposals (otherwise your own
>> support won't be counted in the tally).
>> 

>> :-)

>> 

>> The top three Wikisource proposals so far are:

>>
>> Upload Wikisource text wizard[2]
>>
>> 9 Support Open Archives Initiative Protocol for Metadata Harvesting
>> (OAI-PMH)[3]
>>
>> 7 Integrate the CIS-LMU Post Correction Tool[4]
>>
>> 4
>> 

>> (Although, of course it's far to early to draw any conclusions
>> from that.)
>> 

>> 

>> On Tue, 29 Nov 2016, at 12:16 AM, David Cuenca Tudela wrote:

>>> Hi!

>>> 

>>> The voting period has been opened. You can see the proposals for
>>> Wikisource and enter your votes here:
>>> 

>>> https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wikisource
>>> 

>>> Cheers,

>>> Micru

>>> _

>>> Wikisource-l mailing list

>>> Wikisource-l@lists.wikimedia.org

>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

>> 

>> 

>> ___

>>  Wikisource-l mailing list

>> Wikisource-l@lists.wikimedia.org

>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l

>> 

> _

> Wikisource-l mailing list

> Wikisource-l@lists.wikimedia.org

> https://lists.wikimedia.org/mailman/listinfo/wikisource-l




Links:

  1. http://tools.wmflabs.org/ws-search/
  2. 
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wikisource#Upload_Wikisource_text_wizard
  3. 
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wikisource#Support_Open_Archives_Initiative_Protocol_for_Metadata_Harvesting_.28OAI-PMH.29
  4. 
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wikisource#Integrate_the_CIS-LMU_Post_Correction_Tool
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Community Wishlist Survey 2016 - Voting period opened

[Sam Wilson]

And don't forget to vote for your own proposals (otherwise your own
support won't be counted in the tally).


:-)



The top three Wikisource proposals so far are:


Upload Wikisource text wizard[1]

9 Support Open Archives Initiative Protocol for Metadata Harvesting
(OAI-PMH)[2]

7 Integrate the CIS-LMU Post Correction Tool[3]

4


(Although, of course it's far to early to draw any conclusions
from that.)




On Tue, 29 Nov 2016, at 12:16 AM, David Cuenca Tudela wrote:

> Hi!

> 

> The voting period has been opened. You can see the proposals for
> Wikisource and enter your votes here:
> 

> https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wikisource
> 

> Cheers,

> Micru

> _

> Wikisource-l mailing list

> Wikisource-l@lists.wikimedia.org

> https://lists.wikimedia.org/mailman/listinfo/wikisource-l




Links:

  1. 
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wikisource#Upload_Wikisource_text_wizard
  2. 
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wikisource#Support_Open_Archives_Initiative_Protocol_for_Metadata_Harvesting_.28OAI-PMH.29
  3. 
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wikisource#Integrate_the_CIS-LMU_Post_Correction_Tool
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Fwd: [Wikitech-ambassadors] Your help needed: Community Wishlist Survey 2016

[Sam Wilson]

That sounds really interesting! Do you mean as a way for people
unfamiliar with Wikisource to easily contribute notes and corrections?
On the face of things, it could perhaps work by storing the notes in a
the Page_talk namspace and doing some clever thing to display them on
the Page (and perhaps in main) namespaces.

It seems like it'd be cool to be able to get "typo reports" or
something, from people who mightn't have any idea of Wikisource other
than that's where they got an epub.

To rate a page, we currently have the various levels of proofreading
quality. Is this not sufficient? And does the current Index page
overview of all of a book's statuses work for you? I sometimes wonder
if we need another rating, above 'validated', that indicates that a
whole book has been read through and (hopefully) any remaining typos
have been found.

—sam

On Fri, 11 Nov 2016, at 12:27 AM, mathieu stumpf guntz wrote:
> Hmm, at the conference I think someone was interested in a feature to
> make comments on texts, like you can make on some word processors for
> example. That may be interesting, but how you render the result might
> be a huge user interface problem. One should be able to choose whom
> comments should be visible…
> Otherwise, I would still be happy to have more flexibable way to
> "rate" a page. That is, a page might be text proof readed, but laking
> some css, or a picture should be extracted etc. Having a way to see
> that for all pages in the book: namespace would be fine.
> ĝis baldaŭ
>
> Le 10/11/2016 à 06:09, Sam Wilson a écrit :
>> Thanks Alex :) It's a minor project so far, but I reckon the work
>> you've been doing on making a better, bigger, more proofreading-
>> focused interface is really good. Do stick a proposal up!  So far,
>> we've got:  * Add a 'clean' method for side-titles, and side notes to
>> parser * A spelling- and typo-checking system for proofreading *
>> Visual Editor menu refresh * upload text wizard * Language links in
>> Wikisource for edition items in Wikidata * Display subpage name in
>> category * Make Special:IndexPage transcludeable * Fix Extension:Cite
>> to get rid of foibles  If anyone's got half-formed ideas, I'd
>> encourage you to post something, or just post to this mailing list,
>> and we can all have a chat about it. :)  —sam   On Wed, 9 Nov 2016,
>> at 04:50 PM, Alex Brollo wrote:
>>
>>> I too could add *some* proposals but the first one could be a
>>> deep revision of nsPage edit interface to got the goal "fixed tools,
>>> almost full screen scrolling text & image". In the meantime, I'm go
>>> on testing FullScreenEditing.js by Sam, that presently is an
>>> excellent, running  step approximating such a goal.   Alex  2016-11-
>>> 09 1:03 GMT+01:00 Sam Wilson <s...@samwilson.id.au>:
>>>
>>>> __ Huzza for Wikisource; we've currently got more proposals than
>>>> any of the other categories (not that it's a competition, but
>>>> still...).  @Micru: this whole topic of how to represent
>>>> bibliographic data in WD and properly link it in Wikisource is
>>>> great! I'm looking forward to helping. :-)   —samOn Tue, 8 Nov
>>>> 2016, at 10:08 PM, David Cuenca Tudela wrote:
>>>>
>>>>> Hi Thomas, thanks for bringing that up! I wrote a proposal to
>>>>> finish the work retrieving the language links from several
>>>>> editions and represent them in wikisource as language links.  To
>>>>> write or vote exiting Wikisource proposals, the link is:
>>>>> https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Wikisource
>>>>> Cheers, Micru  On Tue, Nov 8, 2016 at 10:06 AM, Thomas PT
>>>>> <thoma...@hotmail.fr> wrote:
>>>>>
>>>>>> Hello everyone,  The Wikimedia Foundation Community Tech team has
>>>>>> launched a new "Community Wishlist Survey". Last year survey
>>>>>> allowed us to get WMF staff time to work on using Google OCR in
>>>>>> Wikisource that allowed some Indian languages Wikisources to
>>>>>> raise and on VisualEditor support.  Please, take time to submit
>>>>>> new wishes and comment them. It could be simple things (e.g. a
>>>>>> new gadget for a specific workflow) or very complicated ones
>>>>>> (e.g. native TEI support).  Cheers,  Thomas

>>>>>>
>>>>>>> Début du message réexpédié :  *De: *Johan Jönsson
>>>>>>> <jjons...@wikimedia.org> *Objet: **[Wikitech-ambassadors] Your
>>>>>&g

Re: [Wikisource-l] Importing books from Project Gutenberg

[Sam Wilson]

That's a really good point Anika, I'd not considered that having PG 
books could be detrimental to Wikisource! :-(


I guess the reverse could also be true? That Google might think that PG 
is a mirror of WS, and decrease PG's page-rank. Either way, not great.


How can I investigate whether this is occuring? How did you figure it 
out for de.ws?


As for replicating the effort: I figure that if there are people 
interested in doing it, then why not! :-) Personally, I want to make 
Wikisource the best digital library it can be, and when I show it to 
people and they say "oh but you haven't got all of Dickens" or 
something, then I want to fix that. And it seems that importing other 
existing (free and open) digital libraries can help with this in a 
quicker fashion than straight-up proofreading. But I totally can see why 
people wouldn't want to spend time doing it! And that's cool.


:-)

—Sam


On 14/10/16 03:55, Anika Born wrote:

Hy Alex,

My comment was not about spending some time on a PG-Projekt or not 
spending any time at all.


The point/question (when it comes to de-WS) is a different one:

(A) to spend some of our valuable contributions into a project that 
already is freely available (in another format) or spend this time in 
a (related) project that is NOT already freely available? (and we do 
have a lot of them)


// note, it is not about not spending any time in proofreading or
the Wikisourceproject... it is about finding valuable
projects/texts to invest our time...


+ (B) to spend this time in a project, that may cost us the 
findability of the whole wikisource-project (and all other texts on 
wikisource) because Google/Bing/others do tag us as fork/reuser/copy 
of ... (as happened in the past, at least with de, when we had some 
texts of the commercial http://gutenberg.spiegel.de/ that is also 
supported by ABBY with a free softwarelizense)



Anika

2016-10-14 10:13 GMT+02:00 Alex Brollo <alex.bro...@gmail.com 
<mailto:alex.bro...@gmail.com>>:


I'm too very interested both into the idea and into its technical
implementation, but I need some more doc for dummies to understand
it fully :-(

About importing into wikisource texts alreary proofread: a text
into wikisource is different from a similar text into another web
site, since it is "a node into wiki network", and this goal
deserves IMHO some pain to proofread (and re-format)  it again,
adding lots of wiki cross links.

Alex


2016-10-14 8:27 GMT+02:00 Andrea Zanni <zanni.andre...@gmail.com
<mailto:zanni.andre...@gmail.com>>:

I think the idea is good,
but I would like to try that in my wikisource:
could you manage to take also the few italian books that PG has?
Thanks!

On Fri, Oct 14, 2016 at 8:23 AM, Anika Born
<wikian...@wikipedia.de <mailto:wikian...@wikipedia.de>> wrote:

corr1: [...] does not ha*ve*/show the scans, [...]

Anika

2016-10-14 8:18 GMT+02:00 Anika Born
<wikian...@wikipedia.de <mailto:wikian...@wikipedia.de>>:

Hy Sam,

would be good, cause PG does not hat/show the scans,

But

as I remember there was/is a policy at de.ws
<http://de.ws> to not use texts from other projects
(say: if there is text A in PG, there won't be a
similar text A in de.WS),

cause at the time de.WS did use PG-texts... Google
said WS is a mirror of PG and all other (not PG)-texts
were left out in Google-Search-Results as well 
The (small) visibility of WS got lost completely...

That is the reason, why there are no new projects on
de-WS about texts that are available in a (nearly)
similar project

(besides the effort: why spending so much time on a
text that already is avilable? - you'd have to
proofread ist at least two times)


But that is this special German-thing.


What do the others think about it?
    Anika

2016-10-14 3:20 GMT+02:00 Sam Wilson
<s...@samwilson.id.au <mailto:s...@samwilson.id.au>>:

Hi all,

I've been tinkering with an idea I've had for
importing Project Gutenberg books into Wikisource:
http://tools.wmflabs.org/pg2ws/
<http://tools.wmflabs.org/pg2ws/>

The idea is that, if Wikidata makes a link between
a PG ID number and a Wikisource Index page, then
we can go through that Index page one page at a
time, and copy the page's text from the PG book to
   

Re: [Wikisource-l] IA Upload tool

[Sam Wilson]

On Thu, 29 Sep 2016, at 07:36 PM, Andrea Zanni wrote:
> I think that IA Upload tool is a critical step in the Wikisource
> workflow,
> and I wonder if maybe Sam (as a Community Tech employee) could
> dedicate some time to it.
> Tpt can't maintain everything by himself...
> For years, I've explained to *a lot* of GLAMs that uploading
> stuff on IA
> and then using Wikisource is the way to do things, and I'm sure this
> is the standard way in other places
> too.

Yes, I agree: the IA-Commons-Wikisource workflow is a thing that should
be encouraged no end! :-)

As far as my work-programming time goes, you (I say 'you' but I just
mean 'not-me', for CoI reasons) just need to get tickets onto the Community-
Tech board, then I can perhaps look at them. Which basically means they
have to contribute towards a Wishlist item.

There's Wishlist #44: https://phabricator.wikimedia.org/T120785 -
*Implement an Internet Archive-like digitalization service.*
I reckon it'd be great to be able to at least upload a PDF or Djvu with
no text layer, and have it create one (either on the same file, or to
upload a new derived file).

—Sam
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Please import your best templates and scripts into mul.source and la.source

[Sam Wilson]

Good point. That's a useful page. (Is it okay that we treat mulws as our
"Meta"? It seems okay to me, but then there's some discussion about that
moving to mul.wikisource.org I think...)

Maybe some of these scripts are candidates to be made into MediaWiki
extensions, or are otherwise getting too big for their boots — if so, we
can raise them in the Community Wishlist survey, and perhaps give them
the attention they deserve! :-) (Mainly I say that because things are
much easier to test etc. when they're not just text-in-wikipages.)

—sam

On Tue, 27 Sep 2016, at 01:02 PM, Bodhisattwa Mandal wrote:
> Hi,
> Excellent idea!
> Also please add a short description of the function of those scripts
> and templates and tabulate them in a single page in mul.wikisource
> like https://wikisource.org/wiki/Wikisource:Shared_Scripts , so that
> they become handy to other Wikisource projects.
> Regards,
>  Bodhisattwa
> On Sep 27, 2016 10:16 AM, "Sam Wilson" <s...@samwilson.id.au> wrote:
>> __
>> Good idea! And keep in mind that it can be a good idea to keep
>> scripts on one wiki and load them from the others using
>> mw.loader.load() — that way there's only one place to update things,
>> and everyone can use the same version.
>>
>> —Sam
>>
>> On Tue, 27 Sep 2016, at 12:02 PM, Alex Brollo wrote:
>>> I guess that both into larger and into smaller wikisource projects
>>> there are plentiful of clever templates, modules and javascript
>>> tools, developed by users for practical goals.
>>>
>>> Please take a little bit of time and  import them into mul.source
>>> and la.source - the latter being something like a second "multi-
>>> language wikisource". IMHO we need to share our best ideas and
>>> tricks, and both mul,source and la.source could be good showcases
>>> for them.
>>>
>>> Alex brollo
>>> _
>>> Wikisource-l mailing list
>>> Wikisource-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>
>>
>> ___
>>  Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Event: demo of the OCR tool for Indic languages

[Sam Wilson]

Good idea!

Talking of which, anyone know who runs the @wikisource Twitter
account[1]?

(I've only just found
https://en.wikisource.org/wiki/Wikisource:WikiProject_Social_media but
it doesn't say.)


On Thu, 22 Sep 2016, at 05:26 PM, Andrea Zanni wrote:
> Yes! Thanks.
> People who have a Wikisource account on FB or other social media,
> please share :-)
> Aubrey
>
> On Thu, Sep 22, 2016 at 10:53 AM, Sam Wilson
> <s...@samwilson.id.au> wrote:
>> __
>> Hi all,
>>
>> Wikisource will be getting some visibility to the rest of the
>> MediaWiki/Wikimedia community:
>>
>> Coming event: Wikisource OCR demo
>> The *OCR tool for Indic language Wikisources*[2] will be demonstrated
>> by Kaldari at the next MediaWiki CREDIT showcase[3] on Wednesday, 7
>> September 2016 at 18:00 UTC[4]. The session will be broadcast on
>> Youtube (link TBA) and live discussion will take place on Etherpad[5]
>> (side-channel discussion will be in #wikimedia-office on IRC).
>>
>>
>> Thanks,
>> Sam
>>
>> ___
>>  Wikisource-l mailing list
>> Wikisource-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
>>
> _
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l


Links:

  1. https://twitter.com/wikisource
  2. https://wikisource.org/wiki/Wikisource:Google_OCR
  3. https://www.mediawiki.org/wiki/CREDIT_showcase
  4. 
http://www.timeanddate.com/worldclock/fixedtime.html?msg=MediaWiki+CREDIT+showcase+%28September+2016%29=20161005T18=%3A
  5. https://etherpad.wikimedia.org/p/CREDIT
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Event: demo of the OCR tool for Indic languages

[Sam Wilson]

Hi all,

Wikisource will be getting some visibility to the rest of the
MediaWiki/Wikimedia community:

Coming event: Wikisource OCR demo
The *OCR tool for Indic language Wikisources*[1] will be demonstrated by
Kaldari at the next MediaWiki CREDIT showcase[2] on Wednesday, 7
September 2016 at 18:00 UTC[3]. The session will be broadcast on Youtube
(link TBA) and live discussion will take place on Etherpad[4] (side-
channel discussion will be in #wikimedia-office on IRC).


Thanks,
Sam

Links:

  1. https://wikisource.org/wiki/Wikisource:Google_OCR
  2. https://www.mediawiki.org/wiki/CREDIT_showcase
  3. 
http://www.timeanddate.com/worldclock/fixedtime.html?msg=MediaWiki+CREDIT+showcase+%28September+2016%29=20161005T18=%3A
  4. https://etherpad.wikimedia.org/p/CREDIT
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Community Tech new hire

[Sam Wilson]

I am very grateful to Aubrey!! :-)

Although, Aubrey, I think you have the wrong word there! ;-) Surely I
must not "pretend" but to actually and properly seek feedback?! ;-)

Which indeed, we shall all do I think.

So, how best to do that? Wikisource communities are small, but I think
we're actually more united in some ways than in other projects. But I
still think there's a fair bit of dispersion of conversations — I think
most people know about their local Scriptorium (or Bar, Cafe, Warung
kopi, or Тековни настани as the case may be), but there are lots of
contributors who aren't on this mailing list, or don't know about
Phabricator, or don't use IRC.

This issue is pertinent:
T144074 Improve the representation of Wikimedia communities beyond
English Wikipedia in the Community Wishlist Survey 2016[1]

So, anyway, thank you everyone for your welcomes. I just hope I can live
up to it all. :-)

Thanks,
Sam.

On Mon, 19 Sep 2016, at 09:03 PM, Andrea Zanni wrote:
> This is *fantastic* news!
> I'm really happy for Sam and I think this will bring a lot of good
> things for our community.
>
> Of course I don't want to take any credit, but I think it's important
> to remember that:
> * I talked with Ryan Kaldari and Danny Horn (of Community Tech) a lot
>   in Berlin. Johann (also CT) was in  Wien e we all met him:
> * they told me they were in need of another person in the team, and
>   would have liked a Wikisource person too
> * they were very impressed by the response that came from Wikisource
>   community during the Community Survey
>
> In the end, all this advocacy and commitment from the community (plus
> the crucial fact that Sam is awesome) paid off: I think we should all
> be proud of this.
>
> Having a person like Sam inside the WMF is special and crucial.
> He will not of course work just for Wikisource, but we have a real
> chance, as a community, to have a fruitful and rich conversation and
> communication between the community and the team, and we must not
> waste that.
>
> Sam ***must pretend*** a thorough feedback from us as a community,
> when he works on Wikisource stuff.
> We can collaborate to put our requests and feedbacks in the right
> places, and make sure that crucial problems are heard by the "top".
> So, it's a lot of work from us :-)
> We really need to to waste this opportunity.
>
> Aubrey
>
> On Mon, Sep 19, 2016 at 4:22 AM, Sam Wilson
> <s...@samwilson.id.au> wrote:
>> Yes, I hope so too!! :-)
>>
>>  Maybe we should create a column on the Wikisource board on which
>>  to put
>>  wishlist items? https://phabricator.wikimedia.org/project/view/1117/
>>
>>
>>  Oh, and for anyone who missed it, there's a great interview with tpt
>>  here:
>> https://blog.wikimedia.de/2016/09/08/i-dont-have-to-find-tasks-tasks-are-coming-to-me-being-a-volunteer-developer-for-wikimedia-projects-an-interview-with-tpt/
>>
>>
>>
>> On Fri, 16 Sep 2016, at 03:22 PM, Thomas Tanon wrote:
>>  > Hello Sam,
>>  >
>>  > Congratulations! That's amazing! I really hope you will be able to
>>  > keep
>>  > making the Wikisource tech backlog lower [1].
>>  >
>>  > Congrats again,
>>  >
>>  > Thomas
>>  >
>>  > [1] https://phabricator.wikimedia.org/tag/wikisource/
>>  >
>>  >
>>  > > Le 16 sept. 2016 à 05:23, Sam Wilson <s...@samwilson.id.au> a
>>  > > écrit :
>>  > >
>>  > > Hi all,
>>  > >
>>  > > I've recently started working on the Community Tech team
>>  > > https://meta.wikimedia.org/wiki/Community_Tech at the Wikimedia
>>  > > Foundation. So I just wanted to say hi and that I'm really
>>  > > excited to be
>>  > > able to work on Wikimedia code full-time! :-)
>>  > >
>>  > > Community Tech is all about helping build tools that support
>>  > > contributors, and basically takes its work-list from the annual
>>  > > Community Wishlist Survey:
>>  > > https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results
>>  > >
>>  > > For the last couple of weeks I've been working on a tool to
>>  > > bring better
>>  > > OCR to indic-language Wikisources, via Google's Cloud Vision
>>  > > API:
>>  > > https://wikisource.org/wiki/Wikisource:Google_OCR
>>  > >
>>  > > I'm not at all exclusively working on Wiksource stuff of course,
>>  > > not by
>>  > > a long shot. But that's still where my personal interest lies,
>>  > > and so if
>>  > > any

Re: [Wikisource-l] Community Tech new hire

[Sam Wilson]

I am very grateful to Aubrey!! :-)

Although, Aubrey, I think you have the wrong word there! ;-) Surely I
must not "pretend" but to actually and properly seek feedback?! ;-)

Which indeed, we shall all do I think.

So, how best to do that? Wikisource communities are small, but I think
we're actually more united in some ways than in other projects. But I
still think there's a fair bit of dispersion of conversations — I think
most people know about their local Scriptorium (or Bar, Cafe, Warung
kopi, or Тековни настани as the case may be), but there are lots of
contributors who aren't on this mailing list, or don't know about
Phabricator, or don't use IRC.

This issue is pertinent:
T144074 Improve the representation of Wikimedia communities beyond
English Wikipedia in the Community Wishlist Survey 2016[1]

So, anyway, thank you everyone for your welcomes. I just hope I can live
up to it all. :-)

Thanks,
Sam.

On Mon, 19 Sep 2016, at 09:03 PM, Andrea Zanni wrote:
> This is *fantastic* news!
> I'm really happy for Sam and I think this will bring a lot of good
> things for our community.
>
> Of course I don't want to take any credit, but I think it's important
> to remember that:
> * I talked with Ryan Kaldari and Danny Horn (of Community Tech) a lot
>   in Berlin. Johann (also CT) was in  Wien e we all met him:
> * they told me they were in need of another person in the team, and
>   would have liked a Wikisource person too
> * they were very impressed by the response that came from Wikisource
>   community during the Community Survey
>
> In the end, all this advocacy and commitment from the community (plus
> the crucial fact that Sam is awesome) paid off: I think we should all
> be proud of this.
>
> Having a person like Sam inside the WMF is special and crucial.
> He will not of course work just for Wikisource, but we have a real
> chance, as a community, to have a fruitful and rich conversation and
> communication between the community and the team, and we must not
> waste that.
>
> Sam ***must pretend*** a thorough feedback from us as a community,
> when he works on Wikisource stuff.
> We can collaborate to put our requests and feedbacks in the right
> places, and make sure that crucial problems are heard by the "top".
> So, it's a lot of work from us :-)
> We really need to to waste this opportunity.
>
> Aubrey
>
> On Mon, Sep 19, 2016 at 4:22 AM, Sam Wilson
> <s...@samwilson.id.au> wrote:
>> Yes, I hope so too!! :-)
>>
>>  Maybe we should create a column on the Wikisource board on which
>>  to put
>>  wishlist items? https://phabricator.wikimedia.org/project/view/1117/
>>
>>
>>  Oh, and for anyone who missed it, there's a great interview with tpt
>>  here:
>> https://blog.wikimedia.de/2016/09/08/i-dont-have-to-find-tasks-tasks-are-coming-to-me-being-a-volunteer-developer-for-wikimedia-projects-an-interview-with-tpt/
>>
>>
>>
>> On Fri, 16 Sep 2016, at 03:22 PM, Thomas Tanon wrote:
>>  > Hello Sam,
>>  >
>>  > Congratulations! That's amazing! I really hope you will be able to
>>  > keep
>>  > making the Wikisource tech backlog lower [1].
>>  >
>>  > Congrats again,
>>  >
>>  > Thomas
>>  >
>>  > [1] https://phabricator.wikimedia.org/tag/wikisource/
>>  >
>>  >
>>  > > Le 16 sept. 2016 à 05:23, Sam Wilson <s...@samwilson.id.au> a
>>  > > écrit :
>>  > >
>>  > > Hi all,
>>  > >
>>  > > I've recently started working on the Community Tech team
>>  > > https://meta.wikimedia.org/wiki/Community_Tech at the Wikimedia
>>  > > Foundation. So I just wanted to say hi and that I'm really
>>  > > excited to be
>>  > > able to work on Wikimedia code full-time! :-)
>>  > >
>>  > > Community Tech is all about helping build tools that support
>>  > > contributors, and basically takes its work-list from the annual
>>  > > Community Wishlist Survey:
>>  > > https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results
>>  > >
>>  > > For the last couple of weeks I've been working on a tool to
>>  > > bring better
>>  > > OCR to indic-language Wikisources, via Google's Cloud Vision
>>  > > API:
>>  > > https://wikisource.org/wiki/Wikisource:Google_OCR
>>  > >
>>  > > I'm not at all exclusively working on Wiksource stuff of course,
>>  > > not by
>>  > > a long shot. But that's still where my personal interest lies,
>>  > > and so if
>>  > > any

Re: [Wikisource-l] Community Tech new hire

[Sam Wilson]

Yes, I hope so too!! :-)

Maybe we should create a column on the Wikisource board on which to put
wishlist items? https://phabricator.wikimedia.org/project/view/1117/


Oh, and for anyone who missed it, there's a great interview with tpt
here:
https://blog.wikimedia.de/2016/09/08/i-dont-have-to-find-tasks-tasks-are-coming-to-me-being-a-volunteer-developer-for-wikimedia-projects-an-interview-with-tpt/


On Fri, 16 Sep 2016, at 03:22 PM, Thomas Tanon wrote:
> Hello Sam,
> 
> Congratulations! That's amazing! I really hope you will be able to keep
> making the Wikisource tech backlog lower [1].
> 
> Congrats again,
> 
> Thomas
> 
> [1] https://phabricator.wikimedia.org/tag/wikisource/
> 
> 
> > Le 16 sept. 2016 à 05:23, Sam Wilson <s...@samwilson.id.au> a écrit :
> > 
> > Hi all,
> > 
> > I've recently started working on the Community Tech team
> > https://meta.wikimedia.org/wiki/Community_Tech at the Wikimedia
> > Foundation. So I just wanted to say hi and that I'm really excited to be
> > able to work on Wikimedia code full-time! :-)
> > 
> > Community Tech is all about helping build tools that support
> > contributors, and basically takes its work-list from the annual
> > Community Wishlist Survey:
> > https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results
> > 
> > For the last couple of weeks I've been working on a tool to bring better
> > OCR to indic-language Wikisources, via Google's Cloud Vision API:
> > https://wikisource.org/wiki/Wikisource:Google_OCR
> > 
> > I'm not at all exclusively working on Wiksource stuff of course, not by
> > a long shot. But that's still where my personal interest lies, and so if
> > anyone's got any ideas about future software development that we need
> > then I'm keen to help if I can. And this year's Wishlist Survey will be
> > happening before too long, so get ready to list stuff there!
> > 
> > Lastly, please be gentle with me as I try to figure out how to shift to
> > life not-as-a-volunteer! (Although I'm still a volunteer too.) I'm
> > trying very hard to be transparent and professional and not blur the
> > various roles gets confusing though! :-)
> > 
> > Thanks,
> > Sam.
> > 
> > --
> > [[User:Samwilson]]
> > [[User:SWilson (WMF)]]
> > 
> > ___
> > Wikisource-l mailing list
> > Wikisource-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> 
> ___
> Wikisource-l mailing list
> Wikisource-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikisource-l
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Community Tech new hire

[Sam Wilson]

Hi all,

I've recently started working on the Community Tech team
https://meta.wikimedia.org/wiki/Community_Tech at the Wikimedia
Foundation. So I just wanted to say hi and that I'm really excited to be
able to work on Wikimedia code full-time! :-)

Community Tech is all about helping build tools that support
contributors, and basically takes its work-list from the annual
Community Wishlist Survey:
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results

For the last couple of weeks I've been working on a tool to bring better
OCR to indic-language Wikisources, via Google's Cloud Vision API:
https://wikisource.org/wiki/Wikisource:Google_OCR

I'm not at all exclusively working on Wiksource stuff of course, not by
a long shot. But that's still where my personal interest lies, and so if
anyone's got any ideas about future software development that we need
then I'm keen to help if I can. And this year's Wishlist Survey will be
happening before too long, so get ready to list stuff there!

Lastly, please be gentle with me as I try to figure out how to shift to
life not-as-a-volunteer! (Although I'm still a volunteer too.) I'm
trying very hard to be transparent and professional and not blur the
various roles gets confusing though! :-)

Thanks,
Sam.

--
[[User:Samwilson]]
[[User:SWilson (WMF)]]

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Wikidata and mass import

[Sam Wilson]

On Thu, 4 Aug 2016, at 03:44 AM, Thomas Tanon wrote:
> > I wonder how the French Wikisource community solved it, for example.
> 
> The easy way to solve it is probably before importing data related to a
> Wikisource page check if an item already exists for this page (it's an
> easy API call). Even if this raw import would have not been done, we
> would have had to do it anyway, because of hand created items. Most bots
> are used to do that before doing any item creation.
> 

Yeah, this is very true. And not even just checking for the existence of
an Item, a bot will have to check each statement it adds too. There is
the matter of a reverse-check also, of making sure that everything that
*does* have an Item at WD is supposed to.

On a related note, does anyone know if this new Librarybase thing is
going to be help to Wikisources?
http://librarybase.wmflabs.org/wiki/Librarybase:Home
Certainly, where possible, items there should point to Wikisources! :-)
Which will be cool.

—Sam

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Wikidata/source search tool

[Sam Wilson]

Hi all,

I've been attempting to get my head around Wikidata and how 
Wikisource-works' data is stored there, and have made a simple little 
search thingo:


https://tools.wmflabs.org/ws-search/

It just searches title and author at the moment, but I'm going to extend 
it for dates, genres/subjects, and other properties. There are also 
plenty of ways in which it's not quite working properly at the moment, 
I'm sure. :-)


—Sam.

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Spoken Wikisource for Wikiradio

[Sam Wilson]

That is very cool! I'd not seen Wikiradio before. Thanks for adding 
Wikisource! :-)


I've been wondering for a while about getting into adding audio books 
for Wikisource; always seems like Librivox is the go-to place for that 
sort of thing though (not that one can't add Librivox audio to WS...).




On 07/06/16 10:52, Bodhisattwa Mandal wrote:

Hi all,

As you all know, that we have Wikiradio with us, which transmits 
real-time audio service via the Internet as synchronized set of tracks.


* https://tools.wmflabs.org/wikiradio/

FYI, I have just started two new Spoken Wikisource specific stations 
to the radio.


* 
https://meta.wikimedia.org/wiki/Wikiradio_%28tool%29/playlist/Spoken_Wikisource/de 
for de WS


* 
https://meta.wikimedia.org/wiki/Wikiradio_%28tool%29/playlist/Spoken_Wikisource/en 
for en WS


Interested Wikisourcers are requested to add more audio files to this 
stations. It would also be great to add more spoken Wikisource 
stations in other languages.



Regards,
--
Bodhisattwa



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Wikisource Meetup in Wikimania 2016

[Sam Wilson]

Cool! See you there Thomas. :-)

I'm excited.


On 11/05/16 15:38, Thomas Tanon wrote:

Are any Wikisourcerers going to the hackathon at the beginning of Wikimania? 
I'm going to be there, and would love to help with any Wikisource-related 
coding.

I will be there and ready to work on Wikisource related things!
Cheers,
Thomas


Le 11 mai 2016 à 08:44, Sam Wilson <s...@samwilson.id.au> a écrit :

Yes, good idea. :-)

Are any Wikisourcerers going to the hackathon at the beginning of Wikimania? 
I'm going to be there, and would love to help with any Wikisource-related 
coding.

—Sam


On 11/05/16 04:34, Bodhisattwa Mandal wrote:

Hi,

Wikisourcers from different language communities, who are attending Wikimania 
this year in Esino Lario, are requested to visit the Wikisource meet-up page.
• https://wikimania2016.wikimedia.org/wiki/Meetups/Wikisource
There is an etherpad link also to sort out the agenda of the meet-up

• https://etherpad.wikimedia.org/p/wikisource
Regards
--
Bodhisattwa



___
Wikisource-l mailing list

Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Fwd: [Wikimedia-l] Launch of Community Consultation on strategic approaches

[Sam Wilson]

Thanks for the reminder. :)

On 03/02/16 15:25, Andrea Zanni wrote:

Hi guys,
forwarding this as a reminder.
I really encourage you to spend time on the community consultation,
is not something you can do in 5 minutes.
But Lila is present, reads all the comments and try to engage people.
I of course talked about Wikisource :-D

Start here:
https://meta.wikimedia.org/wiki/2016_Strategy/Community_consultation

Cheers

Aubrey



-- Forwarded message --
From: *Lila Tretikov* >
Date: Tue, Jan 19, 2016 at 2:37 AM
Subject: [Wikimedia-l] Launch of Community Consultation on strategic 
approaches
To: Wikimedia Mailing List >



Dear Wikimedians,



We are excited to have you participate in an important Community 
Engagement

regarding our strategic approaches. This is a major step to help us
prioritize the work of the Foundation beginning in July 2016 and running
for the next 12 to 24 months thereafter into a strategic plan.

Throughout 2015 the Foundation has been exploring how to prioritize its
work to best support the movement's goals, set forth, but not yet reached,
in the 2010-15 strategic plan.

The strategic approaches presented here are based on our vision, strategy
consultations in 2010 
and 2015
,
research on external impacts, and input from staff and a few small
community think groups on key challenges and potential solutions.

Timeline: These are our target dates for this process.

   -

   January 11: Put up pages for translation (done)
   -

   January 18: Launch of community consultation on key questions
   -

   February 15: Close of consultation
   -

   By February 26: Release synthesis of consultation
   -

   By March 4: Publish first draft strategy for comment


We appreciate your time and efforts to help guide the Foundation in its
work to support the movement.

Warm regards,

Lila
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: wikimedi...@lists.wikimedia.org 

Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
?subject=unsubscribe>




___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Discourse for Wikisource mailing list

[Sam Wilson]

On 20/01/16 17:58, Andrea Zanni wrote:
If there is consensus, I can propose Wikisource-l for a test. Just 
tell me.




I'm supportive. Don't know if there's consensus yet. Nemo, have you had 
any experience using Discourse just via email? Would it work for you 
that way? (i.e. then doesn't involve any javascript).


I think I read somewhere recently that Mozilla or someone is supporting 
Discourse in improving the mail interface. is that true, anyone know?





On Wed, Jan 20, 2016 at 1:57 AM, John Mark Vandenberg 
> wrote:


On Wed, Jan 20, 2016 at 3:46 AM, Federico Leva (Nemo)
> wrote:
> I hate Discourse because it doesn't work without JavaScript.
Every time I
> end up on a discourse website I end up crying.
>
> Last time I checked, it also didn't have particularly good
export features.
> I thought I had added to
>
https://en.wikipedia.org/wiki/Comparison_of_Internet_forum_software but
> seems not, maybe was another wiki.

A raw dump (including all metadata) export functionality should be a
hard requirement for any software put into production in Wikimedia.



I absolutely agree. One thing I'd note, too, is that (in my experience 
of managing a few over the years) Mailman is anything but easy to 
archive well (at least not without server access). I *think* Discourse 
has a sensible API, so at least theoretically one needn't leave the 
archiving up to the sysadmins.



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Discourse for Wikisource mailing list

[Sam Wilson]

I'm amazed -- a non-mediawiki idea for discussion! ;)

I reckon it'd be worth a try. People who don't want to use the web 
interface can still just post and reply via email. And I like the idea 
of non-threaded disucssion... it works really well on all the sites I've 
used it on.


--Sam

On 2016-01-20 00:24, Andrea Zanni wrote:
Luis Villa, from WMF, asks if there is a list that wants to try 
Discourse:


https://lists.wikimedia.org/pipermail/wikimedia-l/2016-January/081244.html 
[1]


Discourse is a (great) software for discussion, and it could be very
useful for giving order to the many mailing lists that we have in the
Wikimedia world.
This list is active but not too much, so I'm asking you if we want to
propose as guinea pigs :-)

Many great open source projects use Discourse, so we are far from
being pioneers, and from what I've seen we could really benefit from
the many features the software has.
Just look it yourselves:
discourse.org

Aubrey


Links:
--
[1] 
https://lists.wikimedia.org/pipermail/wikimedia-l/2016-January/081244.html


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Better way to validate pages

[Sam Wilson]

Yes, I sort of agree with this, I must say!

I love the idea of one-click validate this and go to next page, but I 
reckon it should be when one is viewing wikitext. Maybe it could just be 
as simple as save this and go to next? Although, then one doesn't get 
confirmation that one's edits are correct... hmmm I'm no help am I?


Of course, if visual editor is coming, then that's a whole other 
thing... :-)


I always proofread with that DP font, so perhaps if that were set as 
default for page NS viewing... but that's probably not a good idea...


-sam

On 11/08/15 17:18, an...@mif.pg.gda.pl wrote:

If you wish to add the Big Validate Button in a specific Wikisource, it
is your choice. But the Polish language Wikisource will definitely refuse
to use such a tool. So it should never become a general tool.

We have VERY BAD experience with new users making the final validation
process. Noticing an OCR error omited in previous stages is often a
problem for a user unexperienced in work with OCR-based texts. In general,
they just read both texts, do not compare them word-by-word so they often
cannot notice mistakes like: missing paragraph, missing line of text,
wrong word and also aften miss a typo (eg. missing letter).

Our OCR tetxs are full of OCR-specific typos, like

m  instead of in
rn instead of m
1  instead of l
l  instead of 1
l  instead of ł
ą  instead of ę
i  instead of !
,  instead of .
.  instead of ,
wrong capitalization
missing or extra diacritic marks

In most cases such typos are impossible to eliminate using
dictionary-based tests as both words (OCR-created and the correct one)
exist in the OCR dictionary.

Another disadvantage of directing new users to the validation process
(especially without even viewing the code) is that they might NEVER learn
how to format texts (or even fix broken formatting) as they might never
need to use it!
It does not matter whether it is low-level template-based formatting
process or using VE (however, it is likely that wrong formatting enetered
using VE might be difficult to fix while also using VE).

In plwikisource we prefer to direct new users to start work with simple
texts, when little formatting is required (eg. short stories, novels,
simple poetry) entering them (basing on pre-formatted OCR) or to do the
first Proofread stage (red - yellow) than direct them to final
validation.

Maybe OCR in other languages is much better or you do not care for final
text quality - but it definitely should be a choice.

Ankry


Date: Mon, 10 Aug 2015 18:14:20 +0200
Andrea Zanni wrote:

The Big Validate Button is a good idea,
but I also would like a better navigation experience, as it is pretty slow
and cumbersome to got on the top of the page to click a tiny arrow, wait
for the new page, click edit, etc.

Aubrey


On Mon, Aug 10, 2015 at 4:29 PM, Alex Brollo alex.bro...@gmail.com
wrote:


If this is true, then to add a big button Validate to edit by ajax the
code of the page (the header section only needs to be changed if there's
no
error to fix into the txt) should be a banal task for a good programmer.

Perhaps Andrea is asking for much more, but this could be a first step.

Alex



2015-08-10 14:47 GMT+01:00 Nicolas VIGNERON
vigneron.nico...@gmail.com:


2015-08-10 15:37 GMT+02:00 Alex Brollo alex.bro...@gmail.com:

First point is:
is it a safe practice to validate a page without reviewing its raw

code?

Probably yes.
Obviously, it's safer to check the raw code but it's unrealistic to
expect the raw code to be review for all page. Anyway, the pages
doesn't
contain a lot of code (and most pages does'nt contain code at all), so
it
doesn't seems to be crucial to me.
Plus : when VisualEditor will be on WS, less and less people will
actually see the raw wikicode.


A second point: is it a safe practice to validate a page without

carefully reviewing its transclusion into ns0?

Definitively yes.
When can a transclusion can go wrong? In all cases I can think of, the
problem come from templates, css classes or general stuff like that. It
should be fixed generally and it shouldn't block the page validation
since
it have nothing to do the the page itself (but maybe I'm missing an
obvious
example here).


Alex

Cdlt, ~nicolas

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] More on difficulties of discovery of WS within Wikidata

[Sam Wilson]

Is it acceptable to add a descriptive bit to the title of editions? I 
assume so? (I'm still pretty unsure of the culture on Wikidata.)


I've just done it here: https://www.wikidata.org/wiki/Q20706406

Also: is it true that every Item with a ' 
https://www.wikidata.org/wiki/Property:P1957https://www.wikidata.org/wiki/Property:P1957Wikisource 
index page' claim should an 'edition or translation of' some actual 
work? That makes sense to me. :) 
https://www.wikidata.org/wiki/Property:P629


—sam.

https://www.wikidata.org/wiki/Property:P1957

On 16/07/15 18:46, David Cuenca Tudela wrote:
You could add some cue to the title of each edition, or add a 
description, that way placing the mouse cursor over the item it 
displays the hint.
Of course as you sad for Wikidata the navigation it is not so 
important, since it is considered a backend, the frontend should deal 
with displaying more details of each edition. It is possible to do it, 
just needs programmer time which we don't have.



Regards,
Micru

On Thu, Jul 16, 2015 at 3:01 AM, billinghurst 
billinghurstw...@gmail.com mailto:billinghurstw...@gmail.com wrote:


I was just working through data bits and pieces and found another
interesting example of the issues of difficulties of separation.

d:q936276 is the book wind in the willows from there find out
which one has the edition of the book.

While I know that wikidata is primarily focused on data pulls,
that there is no visual cues is an issue. One wonders whether
there is an opportunity to have sister flags against each of  the
edition(s).

Regards, Billinghurst


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
mailto:Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l




--
Etiamsi omnes, ego non


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Category browser

[Sam Wilson]

Thank you! Yes, what a foolish error on my part.

Actually, I never knew that encodeURIComponent doesn't encode single 
quotes! All fixed now; just had to use doubles instead.


Thanks for finding the bug.

And I see ruwikisource has been added to 
https://www.wikidata.org/wiki/Q15634466 which is cool.


I'm not sure about dewikisource and the multiple use of Kategorie:Fertig 
https://de.wikisource.org/wiki/Kategorie:Fertig. Wikidata doesn't like 
it: The link dewikisource:Kategorie:Fertig 
https://de.wikisource.org/wiki/Kategorie:Fertig is already used by 
item Category:Validated (Q15629403) 
https://www.wikidata.org/wiki/Q15629403. You may remove it from 
Category:Validated (Q15629403) https://www.wikidata.org/wiki/Q15629403 
if it does not belong there or merge the items if they are about the 
exact same topic.


Does anyone have some good wikidata-fu they can put into action here? :)

Thanks,
sam.

On 12/07/15 21:40, billinghurst wrote:

Sam,

Would you mind checking the code for output, it seems to break on 
apostrophes, for example the line

  Mrs. Caudle's curtain lectures [Download EPUB]
gives a link
https://en.wikisource.org/wiki/Mrs._Caudle (wrong)
rather than
https://en.wikisource.org/wiki/Mrs._Caudle%27s_curtain_lectures

Thanks. Regards, Billinghurst

On Fri, Jul 10, 2015 at 10:31 PM Sam Wilson s...@samwilson.id.au 
mailto:s...@samwilson.id.au wrote:


Two things about http://tools.wmflabs.org/ws-cat-browser/ —

1. I've changed the ownership of this tool, and it's now at
https://github.com/wikisource/ws-cat-browser

2. It's slightly multi-lingual now. At least, it allows browsing
of the
Italian categories now. All the UI text is still in English I'm
afraid.
I'd like to add languages, but need to know the names of 'validated
works' and root-level categories (e.g. for French it's perhaps
Catégorie:100%, but I'm not really sure; that might be old).

Thanks,
Sam.


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
mailto:Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

[Wikisource-l] Another category loop (ES)

[Sam Wilson]

Does anyone mind that I keep posting these things? This time it's on es:

[0] = Pedagogía_Tolteca - Categoría:ES-P
[1] = Pedagogía_Tolteca - Categoría:Ensayos
[2] = Pedagogía_Tolteca - Categoría:Ensayos_de_Guillermo_Marín_Ruiz
[3] = Pedagogía_Tolteca - Categoría:Historia_de_México
[4] = Categoría:Historia_de_México - Categoría:Historia_por_países
[5] = Categoría:Historia_por_países - Categoría:Historia
[6] = Categoría:Historia - Categoría:Ciencias_humanísticas
[7] = Categoría:Historia - Categoría:Documentos_históricos
[8] = Categoría:Documentos_históricos - Categoría:Principal
[9] = Categoría:Documentos_históricos - 
Categoría:Índice_de_documentos_históricos
[10] = Categoría:Índice_de_documentos_históricos - 
Categoría:Índice_de_documentos_históricos


I could blunder in and post in english on their Scriptorium/Pub/Cafe, 
but that seems rather rude. :)


—sam.

___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Category browser

[Sam Wilson]

The 'index_root' is the category in which Indexes are put when they're 
validated (i.e. proofread by at least two people).


Perhaps for German it's actually Kategorie:Korrigiert? Or is that what 
proceeds Fertig?


If the correct site link is added to 
https://www.wikidata.org/wiki/Q15634466 then the tool will pick it up 
from there.


—sam.

PS And '2' below is the 'root category', i.e. the topmost category of all.


On 12/07/15 20:18, Arnd wrote:
Niclas, 1 and 3 are fine, for 2 and 4 the semantic is not clear for 
me. What does it mean? Arnd





2015-07-12 13:48 GMT+02:00 Arnd arnd.schroe...@gmail.com 
mailto:arnd.schroe...@gmail.com:


Hi all, what is required to have de there as well? Arnd


Arnd, could you confirm, this is right :

'cat_label'  = 'Kategorie',
'cat_root'   = '!Hauptkategorie',
'index_ns'   = 104,
'index_root' = 'Fertig',

I'm not sure for the last since it's not linked on Q15634466 
https://www.wikidata.org/wiki/Q15634466


Cdlt, ~nicolas


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l




___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l


___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Category browser

[Sam Wilson]

On 12/07/15 19:48, Arnd wrote:

Hi all, what is required to have de there as well? Arnd


Good question!

An addition to https://www.wikidata.org/wiki/Q15634466 is all.

I'm afraid I don't know more about that Item. ricordisamoa pointed it out.

It'd be great to get all Wikisources added there. :-)

—sam.
___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l

Re: [Wikisource-l] Github repository

[Sam Wilson]

On 11/07/15 18:43, Ricordisamoa wrote:


Don't forget about 
https://tools.wmflabs.org/hay/directory/#/keyword/wikisource!




Great idea! :) Thank you.

I've added http://tools.wmflabs.org/ws-cat-browser/toolinfo.json to 
https://wikitech.wikimedia.org/wiki/User:Hay/directory



___
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l