Wikisource-l

wikisource-l@lists.wikimedia.org

2 participants
1306 discussions

Re: [Wikisource-l] [Wikitech-l] Fwd: Book extension and navigation
by Federico Leva (Nemo) 06 Jan '15

06 Jan '15

Bjoern, I don't know whether BookManagerv2 is able to "feed" Collection; I asked a few months ago at https://phabricator.wikimedia.org/T28448#302254 (cc Raylton), you could file the request as separate bug. A comment says «Extension:BookManager, which provides both automatic navigation and automatic print version». https://phabricator.wikimedia.org/T17073#203184 I doubt anyone in Wikimedia ever really tried this extension yet (cc Wikisource, Wikibooks). You could check those 3 wikis: https://wikiapiary.com/wiki/Extension:BookManagerv2 (there's also an OER wiki of Guatemala it seems). Again, this is uncharted territory... if the extension gets some real world usage and feedback outside Wikimedia, its development may get faster and after some years it might end up being used in Wikisource/Wikibooks too; don't hope for it to go the other way round, because it never happens. Nemo

1 0

Last CFP | EECEA2015 | February 11-14, 2015 | Philippines
by Jackie Blanco 02 Jan '15

02 Jan '15

The Second International Conference on Electrical, Electronics, Computer Engineering and their Applications (EECEA2015) World Trade Center, Manila Philippines February 11, 2015 University of Perpetual Help System Dalta, Las Piñas - Manila, Philippines February 12-14, 2015 http://sdiwc.net/conferences/eecea2015/ All registered papers will be included in SDIWC Digital Library. =========================================================== The event will be held over four days with presentations delivered by researchers from the international community, including presentations from keynote speakers and state-of-the-art lectures. A seminar will take place at the World Trade Center, Manila Philippines on February 11, 2015 where international participants are free to attend. The conference will be held in University of Perpetual Help System DALTA, Las Piñas – Manila, Philippines on February 12-14, 2015. In addition, trainings will be conducted by companies namely Microchip, Dassault Systèmes and TechSource in parallel with the paper presentations where delegates are encouraged to participate. RESEARCH TOPICS ARE NOT LIMITED TO: * Electronics Engineering * Electrical Engineering * Computer Engineering SUBMISSION GUIDELINES: - Researchers are encouraged to submit their work electronically. - Full paper must be submitted (Abstracts are not acceptable). - Submitted paper should not exceed 15 pages, including illustrations. All papers must be without page numbers. - Papers should be submitted electronically as pdf format without author(s) name. - Paper submission link: http://sdiwc.net/conferences/eecea2015/openconf/openconf.php IMPORTANT DATES: Submission Deadline: January 12, 2015 Notification of Acceptance: 2-3 weeks from the date of submission Camera Ready Submission: January 30, 2015 Registration Deadline: January 30, 2015 Seminar Date: February 11, 2015 Conference Dates: February 12-14, 2015

1 0

Phabricator project for Wikisource
by Wiki Billinghurst 17 Dec '14

17 Dec '14

With the recent conversion of Bugzilla to Phabricator, I requested the conversion[1] of our tracking bug to be a project[2], with the basic premise that a [tag = project], and we are a community working across multiple languages, and that some of our individual efforts spread outside of Wikisource, and sometimes the outer efforts flow inside. Anyway part of the discussion comes to the point that we are not unique among the sisters with that request/idea, and there is a thought about nomenclature, for which the following post points to that aspect. Being a person of simple thoughts, I would be happy for our project to be called (wait for it) ... Wikisource, though that doesn't allow for any future aspects, and others will have valuable input. So I point you to the general nomenclature discussion [3] and my specific request [1] that is lacking a name in the request. Regards, Billinghurst PS. Apologies for the noise for those who are already cc'd the phabricator post. [1] https://phabricator.wikimedia.org/T78498 [2] https://www.mediawiki.org/wiki/Phabricator/Help#Creating_a_project [3] https://phabricator.wikimedia.org/T78482 ---------- Forwarded message ---------- From: Qgil <no-reply(a)phabricator.wikimedia.org> Date: Mon, Dec 15, 2014 at 9:35 PM Subject: [Maniphest] [Changed CC] T78482: XXXX-Radar projects for Wikimedia family projects and languages + MediaWiki Stakeholders To: billinghurstwiki(a)gmail.com Qgil added subscribers: Rillke, Steinsplitter, Billinghurst, Praveenp. Qgil added a comment. In https://phabricator.wikimedia.org/T78482#846850, @Nemo_bis wrote: > I have no idea what "radar" means here. A "Wiktionary" project in phabricator could also be a project used by the Wiktionary community to organize their work. This is why I'm proposing "-Radar" to identify tags used to collect tasks //on the radar// of a community. Could be another word, or could be no word if you think it's not needed. > Tags aren't inherently "more elegant" than tracking bugs. For instance, https://phabricator.wikimedia.org/T43492 used to be an on-wiki page, which I converted to a tracking bug, which worked well because cc'ing yourself is equivalent to watchlisting a page. Watching a project, instead, brings you a ton of notifications for all tasks past and future: yes, there side ways but they're not as easy. > > So, if the aim is to *replace* on-wiki lists, let's make this the summary. Fair point. A notification like "Send me an email when a task is assigned to projects X, Y, Z" is possible with Herald (https://phabricator.wikimedia.org/T630), and I expect most advanced users to set one for themselves to fill the current gap of notifications between joining (almost no notification) and watching (all notifications) a project. In any case, you are right that the main change is to move on-wiki lists of tasks to Phabricator. I have edited the description to make this more clear. I think nowadays an own tag project is a better solution for a new list, but tracking tasks also do the work, and they are indeed easier to subscribe to. Maybe the difference is whether you want to organize the tasks tracked in a workboard or not. > Then ask one by one what their requirements are for such a replacement. Adding *additional* lists, instead, is out of question. The maintainers of these lists are CCed here, please help if I have missed someone. I guess you mean that i.e. it is out of question to create a Commons-Radar project paralel to https://commons.wikimedia.org/wiki/Commons:Bugs still exists? Absolutely. New lists could be started by communities that have none, though. TASK DETAIL https://phabricator.wikimedia.org/T78482 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>. EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Qgil Cc: Aklapper, Qgil, Tpt, Micru, Ricordisamoa, Rdicerb, He7d3r, Carlb, Quiddity, Krenair, Glaisher, Reedy, Nemo_bis, MZMcBride, MarkAHershberger, Vriullop, Toniher, Arnaugir, GPHemsley, jayvdb, Darkdadaah, Raymond, Gryllida, scfc, Krinkle, marcoil, Rillke, Steinsplitter, Billinghurst, Praveenp, Jdforrester-WMF, Rfarrand, Keegan, wikibugs-l

3 2

Call for Papers: Switzerland - International Conference on Semantic Web Business and Innovation (SWBI2015)
by ANNOUNCEMENT 12 Dec '14

12 Dec '14

The International Conference on Semantic Web Business and Innovation (SWBI2015) The University of Applied Sciences and Arts Western Switzerland (HES-SO Valais-Wallis) October 7-9, 2015 http://sdiwc.net/conferences/swbi2015/ All registered papers will be included in SDIWC Digital Library ================================================================ The proposed conference on the above theme will be held at he University of Applied Sciences and Arts Western Switzerland (HES-SO Valais-Wallis) on October 7-9, 2015 which aims to enable researchers build connections between different digital applications. The conference welcomes papers on the following (but not limited to) research topics: *Semantic Web and Linked Data - Database, IR, NLP and AI technologies for the Semantic Web - Geospatial Semantic Web - Information Extraction from unstructured data - Information visualization of Semantic Web data and Linked Data - Internet of things - Languages, tools, and methodologies for representing and managing Semantic Web data - Linked open data - Management of Semantic Web data and Linked Data - Ontology engineering and ontology patterns for the Semantic Web - Ontology modularity, mapping, merging, and alignment - Ontology-based data access - Privacy and Security - Query and inference over data streams - Search, query, integration, and analysis on the Semantic Web - Semantic business process management - Semantic Sensor networks - Semantic technologies for mobile platforms - Semantic Web and Linked Data for Cloud Environments - Semantic Web, Ontologies - Social networks and processes on the Semantic Web - Supporting multi-linguality in the Semantic Web - User Interfaces and interacting with Semantic Web data and Linked Data *Business and Innovation in Semantic Web - Business Model Innovation - Business Models and E-Commerce - Business Technology Intelligence - Challenges for change in semantic services - Collaborative improvement and innovation - E-Business Applications and Software - E-commerce Technology Adoption - E-commerce, E-Business Strategies - E-tailing and Multi-Channel selling - Evolution of Business model for Semantic Web Applications - High-tech marketing - Implementation strategies for responsible innovation - Innovation for E-Business - Innovative methods and tools for products and services - Practices and Cases in E-Commerce - Production of Knowledge Economy - Technology and Business Transformation - Technology strategies - The Latest Trends in Linked Data - Web Advertising and Web Publishing - Web and Mobile Applications Researchers are encouraged to submit their work electronically. All papers will be fully refereed by a minimum of two specialized referees. Before final acceptance, all referees comments must be considered. Important Dates ============== Submission Date: Open from now until Sept. 1, 2015 Notification of Acceptance: 6 weeks from the submission date Camera Ready Submission: September 14, 2015 Registration Deadline: September 14, 2015 Conference Dates: October 7-9, 2015

1 0

Structured data: use of schema.org's structured data for Wikisource works (or similar)
by Wiki Billinghurst 08 Dec '14

08 Dec '14

Dear Wikitech (cc'd Wikisource) A recent discussion in English Wikisource's Scriptorium was querying why commercial book companies, etc. were getting higher search hits, especially where they may just have summary information, rather than full text. In that discussion someone pointed to some of the webmaster information at Google, eg. [1], which (ultimately) talks about their microformat (preferred) or JSON-LD as a means to put in more particular metadata as explained at schema.org (for creative works [2]) I went to play, and ultimately failed, and was pointed to the inability to <script> for security reasons, and the inability to add micodata (<cite user="bawolff">microdata attributes are implemented in MediaWiki, but currently disabled via $wgAllowMicrodataAttributes</cite> thx). So my naive questions to those that know these things are 1) How do we look to improve external search engine hits for the sister sites where they are particularly pertinent to a search [wikipedia already gets Google special treatment] 2) if the schema.org metadata is a preferred means to progress, what is the recommended means to progress such an issue 3) presumably some of this fits into the discussion about Structured Data discussion, and what means is there to include this into that discussion? Thanks for the guidance. Regards, Billinghurst [1] https://support.google.com/webmasters/answer/3227642?hl=en&ref_topic=3222270 [2] http://www.schema.org/CreativeWork

4 3

Tool to check transclusions of index pages? (something not manual)
by Wiki Billinghurst 02 Dec '14

02 Dec '14

Anyone know of a tool or a ready means that can check for works (that are proofread) for the amount/percentage transcluded? I am wondering how many works may be out there that have plenty of work done on them but sitting there needing transcluding. It seems that a tool that can do that sort of analysis, or that could project that data to an Index: page would be useful. To note that MZM did create the checker tool on toollabs to manually run a check on an index page, however, that level of reaction is only useful for a detailed analysis of a work. While I am mumbling about wishes, I would still love to have the ability to project the transcription status of a work (the ribbon) onto a page rather than having to poke [[Special:IndexPages]] Regards, Billinghurst

1 0

Again on funding for sister projects
by Federico Leva (Nemo) 28 Nov '14

28 Nov '14

See https://meta.wikimedia.org/wiki/Grants_talk:APG/Staff_proposal_assessment_f… : there seems to still be an assumption that Wikipedia is ok by default while everything else needs to be justified. Nemo

5 10

GLAMs crowdsourcing transcription and branding
by Ben Brumfield 26 Nov '14

26 Nov '14

In a separate thread (sorry--digest mode bit me), Dominic wrote: Many cultural institutions are developing their own crowdsourced transcription projects. I think Wikisource can be a much more robust platform than these one-off projects, with a more well-developed community that aggregates the transcription efforts of texts from many institutions in a single place with a proven process. I'm a big fan of Wikisource, and have recommended it, but I don't think that data extraction is the biggest barrier to adoption the GLAM sector faces. Branding is a much, much bigger deal. I talked about this the ALA this summer ( http://manuscripttranscription.blogspot.com/2014/07/collaborative-digitizat… -- see the slide with a screenshot of Wiksource next to one of Letters 1916, which uses DIY History/Scripto as its platform): "The first one is is the French-language version of Wikisource. Wikisource is a sister project to Wikipedia that was spun off around 2003 that allows people to transcribe documents and do OCR correction both. This is being used by the Departmental Archives of Alpes-Maritimes to transcribe a set of journals of episcopal visits <http://fr.wikisource.org/wiki/Livre:FRAD006_001J201.pdf>. The bishop in the sixteenth century would go around and report on all the villages [in his diocese], so there's all this local history, but it's also got some difficult paleography. "So they're using Wikisource <http://manuscripttranscription.blogspot.com/2012/04/french-departmental-arc…>, which is a great tool! It has all kinds of version control. It has ways to track proofreading. It does an elegant job of putting together indiviual pages into larger documents. But, do you see "Departmental Archives of Alpes-Maritimes" on this page? No! You have no idea [who the institution is]. Now, if they're using this internally, that may be fine -- it's a powerful tool. "By contrast, look at the Letters of 1916 <http://dh.tcd.ie/letters1916/diyhistory/>. [Three sentences inaudible.] This is public engagement in a public-facing site. " There were a lot of nods in the room, and even more when I revisited the slide in a crowdsourcing workshop a month later. If an institution were able to attach a custom stylesheet to pages displaying its 'project', if it were able to send users to an attractive homepage for its 'project', showing the project's materials, and recent activity on them, with ways for admins to monitor their volunteers' questions or discussions on talk pages, or announce news -- that would drop that barrier to entry. At the moment, a GLAM that points its users to Wikisource effectively 'loses' them -- they're sending them off to a different community and a different site that just happens to contain copies of the institution's material, with no easy way for the users to get back to the institution. That said, think bulk export of transcripts would help, especially if there were an easy way for the institution to match each transcript to the identifier in its own system. Plaintext may be good enough for e.g. a library that's using a CMS and just wants their docs to be searchable. I've seen TEI recommended in the past, and while I'm a big fan, I suspect it's of secondary importance. Ben

2 1

What is our next major hurdle, or where we need most development assistance
by Wiki Billinghurst 25 Nov '14

25 Nov '14

What do we see as the next components for Wikisource? What are our major hurdles for system development? If we were offered development help where do people think that we should be making use of that help? Is it incremental fixes, transactional changes, or are we wanting transformational changes, completely new features, and new opportunities? Regards, Billinghurst

6 14

Wikisource contest starts tonight!
by Andrea Zanni 24 Nov '14

24 Nov '14

Just a reminder :-) Aubrey

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Wikisource-l