Projects/Wikislice: Difference between revisions

From OLPC
Jump to navigation Jump to search
 
(18 intermediate revisions by 7 users not shown)
Line 32: Line 32:
* Salim Ismail
* Salim Ismail
* [[User:SJ|SJ (Samuel) Klein]]
* [[User:SJ|SJ (Samuel) Klein]]
* Scott Abel
* Scott Abelkkk



----
----
Line 40: Line 41:
Team meeting details are as follows:
Team meeting details are as follows:
Meetings are currently scheduled monthly, using the conference info posted on the Google Group wikislice project. Please contact Lynda Chiotti for info.
* Regular meeting day: 2<sup>nd</sup> and 4<sup>th</sup> Thursday of the month
* Regular meeting time: Thursdays, 08:00PDT/10:00CDT/11:00EDT/16:00BST
* Conference call number: 877.421.0003 (US), 770.615.1374 (UK)
* Conference call passcode: 499831 (followed by the # sign)


See below for meeting minutes; the most recent team meeting appears first.
See below for meeting minutes; the most recent team meeting appears first.


----
----
==== Team meeting, 06 May 2009 ====

'''Attendees:''' Michael, Lynda
==== Team meeting, 24 July 2008 ====
'''Invitees:''' Alyson, Anne, Andy (did not make call), James, Laura, Lynda, Michael P, Michael B, SJ (did not make call), Salim (did not make call), Scott

'''Agenda:'''
# Discussion: Michael's 7/24 email
# Extreme Blue project update
# Status update: target users (teachers)
# Work session to draft assumptions


'''Discussion:'''
'''Discussion:'''
Michael reported from the recent DITA North America conference a new proposal for a mashup subcommittee, looking at combinations of DITA and data, starting with, for example, the semi-conductor and retail industries. This becomes relevant for this committee because if we can get wikipedia material into a structured format, it becomes mashable. Another proposal from the conference was a subcommittee looking at DITA for the web. A draft charter will be circulated and any Oasis members could participate.
# MP discussed background of his message, which was a solution coming from concerns about multiple platforms, among other things. By using web application to edit in a tree view, teacher could prune and reorganize to make a custom curriculum, possibly then saving somewhere like Curriki. Could be built to include other potential sources beyond wikipedia. Avoiding the issue of editing actual topics removes the editor software question from the workflow for the first phase. There was general agreement that this is a good idea, providing a good user experience especially if it is available within a browser. We would need web-based tools that allow drag and drop, delete, etc., which are not currently within public domain, but MP could inquire further. Offline editing would be possible, but repackaging would have to wait for reconnection. This workflow would not be the ultimate solution, but could serve to get to first prototype. Possibility of annotation function was discussed, as an additional topic type, keyed to topic headings. This function is desirable according to teachers. Further inquiry to teachers should be done to find out if they would use this for single lesson, collection of lessons, or whole curriculum plan. This approach does not allow editing at sentence level. James and Laura described that this is being worked on in the Extreme Blue project. Discussion followed to clarify use of DITA map term for structure being used by Extreme Blue editor function. There, the teacher is able to view and edit several editable topics (sections) within editor application, then reparse to make processable using the Toolkit. MP, James and Laura will meet next week to discuss further.


We discussed a full relaunch of this committee to get things going again, starting with a recasting of the mission statement. With a list of deliverables, skills, and roles needed, we could broadcast a call for participation. Given that we have achieved the proof of concept, we can expand beyond XO teachers and go to web-based more generally accessible capability.
# All were reminded of the need to write down project assumptions as we go along.


'''Action needed:'''
# Discussion of MP's workflow and Extreme Blue work will continue at next meeting.
Existing committee members are invited to draft new wording for the wikislice committee mission statement. Discussion as the wording is developed can take place in the Google Group. Lynda will undertake to start the discussion, with a draft available for the next meeting.


==== Team meeting, 01 Apr 2009 ====
# Alyson will set up an interim meeting also to discuss teacher contacts.
'''Attendees:''' Laura, Lynda

'''Regrets:''' Michael P, Mary Ann
==== Team meeting, 10 July 2008 ====
'''Note:''' Today's meeting is cancelled due to a conflict with the IBM members of the team. We'll resume our regular meetings on July 24th. That gives us lots of extra time to complete our homework -- nudge, nudge. ;-)

----

==== Team meeting, 26 June 2008 ====
'''Invitees:''' Alyson, Anne, Andy (did not make call), James, Laura, Lynda, Michael P, Michael B, Salim (did not make call), Scott (did not make call)


'''Agenda:'''
'''Agenda:'''
1. Introductions
# Announcing new team members! Welcome, Lynda, and welcome, Scott!
2. Meeting frequency and meeting notes decisions
# Review of to-dos from previous meeting
3. Revisit mission statement to make sure we all understand why we
# Planning target user participation
exist
# Toward a project plan...
4. Update on specific activities: Infoslicer, others?
5. Action items


'''Discussion:'''
'''Discussion:'''
Laura provided the update on Infoslicer as follows. since release in January 2009, has had some GUI tweaks to make it more Sugar-like. Infoslicer to be included in next release of Sugar on a Stick (bootable USB version of Sugar).
# Team members, including new members Lynda and James, introduced themselves. Alyson recommended that team members post profile pages.
# MichaelP looked into possible Linux editor options, reported that a good range of options exist. DITA Storm, an editor from Inmedius is the lightest weight; the company is fairly friendly to non-profits, even though commercial. It should give us the demo capability we are looking for and has a wysiwyg view (like HTML) as well as a tags-on view.
# MichaelB summarized his understanding of the editor discussion: we want to enable content development on XO, maybe in Windows, but that's not the primary objective. Editing activity could be browser or Sugar based. MichaelB offered help with UI design, to offer a very natural experience, especially targeted to be like other experiences on the XO. MichaelP agreed editing on XO is only one scenario, but we should keep the broader picture in mind.
# Alyson reported discussion with Laura on efforts to find teachers. Laura said one teacher may come to visit The EB students, but is also willing to answer questions in writing. It was agreed that a standard email message and set of questions would be useful. Anne reported a contact in Austin who works with Uruguay people, (maybe not teachers, could be admins) to whom she can send emails. She got a response from someone in Bolivia, but could not tell what his role is. Anne also said someone in Bolivia has use cases for material used in schools, very dated (1964). It was agreed to post information such as Anne's findings at the bottom of the team page, then later consider structuring it as needed. Laura has emailed people contacted through her blog. Two are willing to help by email. Alyson knows someone working in Uganda. Lynda has a contact in Namibia. MichaelB asked about Jamaica not being on the target list. His wife has been a teacher with sister schools there. It was agreed he will go ahead to pursue possible contacts.
# Laura and James gave an update on the EB project: Students arrived this week, are setting up flickr and delicious accounts, did an exercise on printouts of wikipedia pages to get a feel of what would need to be done to edit for suitability for 6-11 year olds. One student's mother is a primary school teacher. He will ask her how she would approach it. Students will blog about progress. MichaelP will talk with them about DITA next week and help with DTD specialization for them to start using.
#Alyson discussed need for timelines and goals, not formally articulated although evident in some material on page. Discussion folllowed of change in hardware and software recently that may suggest change of need to focus efforts. Agreed that upfront steps need to be the same, regardless of delivery platform.


'''To-dos:'''
'''Action needed:'''
Need more people actively working on infoslicer, especially with coding ability.
# Alyson and Laura to develop and refine standard message and survey questions for educators.
Need to figure out what else this committee should work on, eg., a web function based on some of infoslicer code.
# Alyson to post draft assumptions and objectives for project plan on team page.
Can we do some user testing on current version of infoslicer?
# All team members to work on assumptions and objectives for discussion at next meeting, adding to Alyson's post on page.
----


==== Team meeting, 12 June 2008 ====
==== Team meeting, 9 Oct 2008 ====
'''Invitees:''' Alyson, Anne (did not make call), Andy, Laura, Michael P, Michael B (did not make call), Salim (did not make call), Scott Abel (regrets -- at conference)
'''Invitees:''' Alyson, Anne, Andy, James, Laura, Lynda, Michael P, Michael B, SJ, Salim, Scott


'''Agenda:'''
'''Agenda:'''
# Demo Infoslicer Sugar Activity
# Announcing new team member: Scott Abel
# Review of to-dos from previous meeting
# Extreme Blue project update
# What next? Toward a project plan...


'''Discussion:'''
'''Discussion'''
Awesome presentation by Laura.
# Wikibrowse -- development partnership? Working on an offline browser for wiki content. Can we arrive at a common space? How could we work together? Can they provide a browser than can handle DITA content directly or HTML from which we can generate DITA? Net may be that we end up with an effective browser that can work on DITA content in OLPC either directly or indirectly.
# Andy talked to Walter Bender (Sugar Labs) -- assumptions about teachers' machines. Teacher would typically have access to the same laptop as the children. Would be a school server that would provide additional processing capability and storage. Staging post for forwarding content to pupils. Need to align ourselves with Sugar environment rather than OLPC/XO side of things because whatever happens with the OLPC project, the mission of Sugar Labs is to get the Sugar environment with educational software running everywhere. Gives us a broader fan base than merely running on the XO. Bad news is that if we want to concentrate on the end-to-end non-Windows scenario, then that leaves us without a real editor story (InVision issue). Green thread -- not an ideal path, but a path that you know works. The green thread here might involve a hop over to Windows where we know that an editor is available. The Sugar development environment is a desktop runtime that supports applications (C++, C, Perl) and provides a windowing environment that runs on xWindows (UNIX), MS Windows. Just the top layer, a graphical interface -- can run anything on it that accesses the OS. When running on an XO laptop, the underlying environment is currently Fedora Linux. Anything that runs on Fedora would run. Maybe we should see if someone from one of the Fedora-friendly editors would want to get involved here?
# Possible Linux editors -- Oxygen (not sure how heavy duty this is -- recently came out with full featured DITA support release), XML spy.
# Do we support multiple paths? We don't have a native Sugar editor. Sugar may run on Linux (option A, working for the laptop) and Windows (InVision editor).
# MichaelB has lots of UI design experience. If we create a new editor for Sugar, he'll be an expert.
# Laura has sent out 3 emails to possible teachers who might want to get involved. One excellent local UK option will assist us. EB Business Mentor has experience working with education technology in Uganda.


==== Team meeting, 18 Sept 2008 ====
'''To-dos:'''
'''Invitees:''' Alyson, Anne, Andy, James, Laura, Lynda, Michael P, Michael B, SJ, Salim, Scott
# MichaelP to follow up with Lotus Mashup team
# MichaelP to research possible Linux editor options
# Alyson to connect with MichaelB re: editor discussion
# Alyson to follow up with wikibrowse team
# Laura -- any luck on finding teachers?
# Alyson to catch up with Anne
# Alyson to follow up with SJ regarding teacher leads, involvement from wikipedia
# Alyson and Laura to brainstorm on use case validation with her local UK teacher option
# Laura to work with the EB to have them get a wiki set up for their project

----

==== Team meeting, 29 May 2008 ====
'''Invitees:''' Alyson, Anne, Andy, Laura, Michael P, Michael B, Salim, <strike>Tom</strike> (regrets)


'''Agenda:'''
'''Agenda:'''
# After August hiatus, time to regroup:
# Review of team to-dos from the previous meeting (everyone)
## Update on Extreme Blue project
# Excellent news (Laura)
## find coders/sponsors for web implementation
# Efforts to add additional team members (Michael)
## create prototype per Michael's outline
# Work time: continue to flesh out use cases (everyone)
## engage with related teams - per SJ
## get end user participation/involvement
# Team membership updates


'''Discussion:'''
* '''Additional team members.''' MichaelP has sent notes -- (1) Travis from wikiHow (original connection to OLPC and Wikipedia, might like to get back involved now that we're closer to having something real); (2) Scott Abel from Content Wrangler -- has been pushing Web 2.0, content management, and DITA to his audience and is interested in connections in this space; and (3) SJ, trying to get us access to our target users, teachers with whom we can validate use cases. Andy -- what about Sugar Labs (we can focus on educational software on the Sugar platform, independent of the hardware it runs on)? Development using Sugar-based platform for low-end development for educational purposes. Michael -- need to be able to operate with other kinds of software as well.
# Report from Extreme Blue: The students' last day is this week. They're working on a video or e-meeting demonstration of the project results. Laura is working with legal on the intentions to open source the project. Currently it pulls down content from Mediawiki (the engine that Wikipedia runs on) and maps all the content to DITA reference topics. It tracks the version of each sentence so that it can trace back to changes. Doesn't yet get updates from Wikipedia after the content is pulled down. Basically the content is stored in a "library" which contains multiple nested DITA maps. Next meeting we will get to see a demo of the project. There is an opportunity to create a web service (single button press on a web page) to start all the slicing. Michael and Anne took action items to find an interested developer who would like to create this web service.

# Report on related teams: The [[WikiBrowse]] project takes Wikipedia pages with a high number of interest in the pages and creates an offline version of Wikipedia that can be carried around on the XO. This project fits nicely with our aims and offers an offline scenario. The BookSprint project was a documentation project co-managed by OLPC, Sugar Labs ([http://wiki.sugarlabs.org]), and FLOSS Manuals ([http://flossmanuals.net]). While there is not a DITA tie in (FLOSS Manuals uses TWiki and XHTML but it is structured), the content from the BookSprint is available in the new [[Help (activity)]].
* '''Laura's big news.''' One of the projects on IBM's Extreme Blue student summer programme in the UK this year is Educational Mashups for One Laptop Per Child - means we'll have 4 students to work with us on development for this project, starting June 23<sup>rd</sup>. Woo hoo! Lots of discussion on this topic.... Where to focus these students? Bottleneck is getting the content out of wikipedia, into the standalone consumable form (the DITA map and topics). If we can focus there, that's an intermediate function that we can show off and then use for additional work -- subscription model, feedback, coordinate with Sugar Labs to broaden scenarios. First job should be getting a local copy of the DITA content extracted. If we can have Windows running on a laptop, then that means we can use the InVision Word-based DITA editor to work with the DITA content locally with the DITA Open Toolkit as the publishing engine. This could work in, say, US schools but there needs to be a lightweight editor -- shouldn't assume that Windows is present. Key challenge: can't assume that the teachers will have good laptops or Windows. Need to focus on open source -- Sugar is an open platform - currently runs on various Linux distributions. At the very least, we'll have the teacher consumption scenario (they have a PC running Windows) -- in that context, there is room for the InVision editor. First, get the content out of wikipedia -- then diverge along either a Windows or a Sugar path. InVision will contribute the DITA editor but understands there is a Sugar path too. Need to define a workflow based on types of inputs and types of outputs. DITA Open Toolkit runs on any platform. The DITA editor is our sticking point. Not sure how far we can slim down the DITA OT tool stack. If this part of the workflow is on the teacher machine, we can get it working for scenarios where they have a more powerful machine, then focus on getting the processing requirements down over time. A preferable approach, though would be to start with a low-end entry point (e.g. the OLPC XO). Start first with cross-platform. DITA OT works on Linux and Windows. For EB project, one area of great interest is the connection between the local copy and the copy online. MichaelP: get the local copy, design work around what the DITA markup will look like and where we want to store time stamp (when extracted, last changed server, last changed locally), tool that runs on demand when there's a net connection that goes to wiki and gives a list of changed and new topics in the map selected that I have a local copy of. Standard diff between local and server copies, let people decide how to resolve. None of this involves the editor yet. Can use the InVision editor or a free Linux editor (though there are usability issues with the Linux editor). For the EB project, need to demonstrate this working with a swappable editor -- the editor component is left to the community to develop and the audience to choose. Our focus: get DITA content out of wikipedia, reconcile changes, and push select feedback back to the wiki).
# Report on end-user participation/involvement: Anne still has contacts who are willing to help with a teacher survey or testing. After the demo, we can demo the results to groups like the teacher end-users.
*: Comment: focus on Linux & Sugar at first if you want feedback from XO teachers (below)... --[[User:Sj|Sj]]&nbsp;[[User talk:Sj|<font style="color:#f70; font-size:70%">talk</font>]]
# Since the wiki page was getting a little large, I moved all other meeting notes to a [[/TeamMeetingNotes]] page.

* '''We need XO teachers!''' Need to focus on this for next meeting. Hoping that Michael's note to SJ will generate some progress. Worst case scenario: use any teacher. What kind of teacher? Long-term: non-US, non-native speaker of English, experience preparing lesson material for 8-year-olds, environment characterized by extreme lack of resources. What does it mean for a teacher to take content from wikipedia and make it useful? Laura might have a contact with a couple who have this experience in Africa. Agreement that language issues are a future thought. Need to find someone from key target countries (needs to speak English for us for now). Differences in the way people teach in different countries. If we only got teachers from England and Canada and the way they teach is radically different from how the user teachers work, then we'll mis-gear the solution. Need to get real data on job role, job skills, actual work method. First let's find someone who's taught 8 year olds, then try to find a representative user who can address the cultural and environmental issues.
*: Comment: start with someone fluent in English to help revise what to ask for. We could then find a teacher in Brazil / Peru / Haiti... It might be useful to work through this for an English-language teacher in the US as well as long as that doesn't throw off longer term sol'ns.

* '''Use cases.''' Will do further drill-down with students so they can participate and help drive the learning and design process.

'''To-dos:'''
* Andy to contact Sugar Labs to explore their involvement.
* Laura, Andy, Michael, and Alyson to meet next week to nail down details for the Extreme Blue student project -- will bring details back to this group.
* Laura to contact SJ about a development contact for the EB students (and copy Alyson).
* Laura to contact her XO/Africa couple about possible involvement. And blog, too!
* Anne, Alyson, Michael to increase focus on getting teacher involvement.
* Alyson to touch base with Salim on his involvement.

----

==== Team meeting, 22 May 2008 ====
'''Invitees:''' Alyson, Anne, Andy, Laura, Michael P, Michael B, Salim, <strike>Tom</strike> (regrets)

'''Agenda:'''
# Need a note-taker this meeting(Alyson has to leave early).
# Review to-dos from last meeting.
# Drill down on use cases.

'''Discussion notes:'''
* Anne hadn't filled in the tools needed or identified the gaps in the end-to-end use case yet, so we discussed where those can be filled in. Also, Anne will add the main success scenarios and identify actors for the use cases she added in the previous weeks. The tools identified so far are: DITA export from Wikipedia (MediaWiki engine), DITA content editor on the XO laptop, and a DITA map editor on the XO laptop.
* Related to tools, there are some relevant announcements from OLPC for our project. One is - the XO laptop will run WinXP and contain Microsoft Office by the end of the year, likely in the September 2008 time frame. I've been reading as much of the news as I can about the Windows on the XO computer, and I have to say the best essay for helping me understand the background is [[http://radian.org/notebook/sic-transit-gloria-laptopi Ivan Krstic's blog entry]]. Also informative is the [[http://www.nytimes.com/2008/05/16/technology/16laptop.html?_r=2&oref=slogin&oref=slogin New York Times article]]. And I also found the [[http://blogs.technet.com/jamesu/archive/2008/05/15/look-windows-on-the-olpc-xo.aspx Microsoft Unlimited Potential blog entry rather informative]].
* Related to educators, Anne and Alyson emailed folks from the Dallas-Fort Worth deployment of XOs as well as the Birmingham, Alabama deployment, asking for teacher participants in the project. We'll let the team know who is interested, and the request seemed well-received. Once we have tasks for teachers, we can touch base with them again.
----

==== Team meeting, 1 May 2008 ====
'''Invitees:''' Alyson, Anne, Andy, Laura, Michael P, Michael B, <strike>Salim</strike> (regrets), <strike>Tom</strike> (regrets)

'''Agenda:'''
# Administrivia: (a) we've got a meeting time!; (b) user profiles/pages; (c) rotating minute-taking.
# Review SJ's email response to 16 April team meeting.
# Review homework from last team meeting -- begin work on use cases.

'''Discussion notes:'''
* Benefits of DITA: (1) consumable resources, (2) preserve template outside of wiki environment
* Assume we have DITA specializations for wikipedia article types (historical person, animal, country)
* We don't reorganize wiki pages, we reorganize the map -- wikislices then point to whole articles and sections (teachers can edit the map to point to what they want)
* Pages have anchor tags/sections
* Not a wikislice because we're authoring on the local machine, it's a DITA slice -- you create a new parent node in the map with a short description or a new topic on the local system -- "glue content," create new topics -- scenario use case is "creating new content" for teacher use case (not just reordering and edit) -- this is a local operation
* Editing in Word not possible because Word doesn't run on the laptop. We will need a local DITA editor on the laptop (tool requirement!)
* Tools involved: editor, generation step from wikipedia
* Student team might be available in IBM Hursley to help us build this tool if we have requirements specifically defined. Should know within a month whether it's available.
* Our team goal: get to very specific use cases
* For the future: teacher might be using their own laptop or PC -- with PCs in the US scenario, high chances that they'd have Word and therefore Word docs that they might want to add to the wikislice. Need to address international scenario.
* Would In.Vision play in this scenario? Would need low-cost version, lots of people using it! MichaelB absolutely sees this. Some good profile-raising opportunities.
* Editing environments: on the wiki, on the XO laptop, on a non-OLPC PC
* Need to work with Salim -- he has connections to companies developing OLPC tools -- is there a connection there for the editor?
* Usability is a huge issue -- Michael's company has a lot of expertise on usability in the DITA editing world for the student project -- which bit is most appropriate for the student development?
* Need to define the requirements/purpose so we can shop around for development resource
* Need more external awareness -- needs to be a development community around OLPC and wikipedia -- SJ is our contact to both
* We need to figure out our requirements, value-add, etc. to generate that interest from the OLPC development community
* Need to drill down into scenarios with specific tasks - what, why, how
* First pass at a basic comprehensive use case from Michael below

'''To-dos:
* Define details and specifics underneath [[Projects/Wikislice#Use_cases|Michael's simple use case below]] -- Anne to take first pass
* Michael to create blog entry to try to generate interest
* Anne to talk to local teachers to see if there's interest in helping us
* Alyson to try again to connect with SJ on meeting times and finding teachers to help us with participatory design/usability validation
* Alyson to connect with Salim -- get him up to speed, issue on connections to other companies (specifically: he mentioned that he knew some folks in startups that were focusing on tools for the OLPC)


----

==== Team meeting, 16 April 2008 ====
'''Attendees:''' Anne, Andy, Michael P, Michael B, Alyson

'''Minutes:''' (post-meeting comments from SJ Klein added -- look for **SJ)
# Draft audience descriptions for DITA/OLPC project: We're looking forward to having the information below confirmed and enhanced with input from SJ and this group -- this will be the bulk of today's discussion. As you can see, there are some questions (and I'm sure you have some, too!) that need answering.
# our team's goal: bundle wikipedia articles together for children to consume as curriculum (**SJ: "Perfect. Zdenek as you know has been working on generating bundle-sets. There are also a few childrens-encyclopedia projects underway."**)
# actors for a wikislice:
## content consumer.
### kids have to be able to read/interact with the slice, that it makes sense relative to what else they're studying (**SJ: "Interaction is important here. How does annotation reflect/pass up the chain?"**)
### teachers -- teach in the material in the wikislices to the kids on the XO (primary consumers)
### teachers also provide feedback to wikipedia -- requests for slices, requests for enhancements/functionality for slices (**SJ: "Requests are particularly important."**)
#### Andy: they go get the slices, press a button, and out comes a bundle
#### Michael: pure Wikipedia scenario -- situation where some of the resources they want are in Wikipedia but some are coming from another resource (ideally in DITA, DITA is the common currency), then they might start with a wikislice but will end with something that is a custom thing with pointers to some wikipedia sources but also some from other collections -- the wikislice is just a starting point for a curriculum design exercise.
#### Michael/Andy: need to guarantee that wikislices are in synch (that everyone is teaching from the same material). The school would have the main repository with the internet connection, and the kids would connect with each others PCs and the central repository -- update would happen on the central repository and kids would synchronize from that. Potential to be an automatic update. Might want to have an automatic inform ("FYI, there are updates available, come get when ready"), rather than forced. Teachers could preview that update is appropriate.
#### Anne: blue and red indicators that show a wikislice article has info about butterflies but article doesn't exist yet (red=not populated, blue as soon as something was there?).
#### Michael: may be as simple as in the local DITA copy (of the wikislice or of the individual article resources), make sure we include a time stamp -- then when the kids have an internet connection run through the time stamps and compare to time stamps on remote connections. Need to optimize this. If local resources has been edited since last download, then it kicks off a comparison workflow -- "grab the updated copy but create a new version of the document and enable side-by-side viewing."
### New audience: local curriculum designer/deployer -- makes decision of what wikislice to grab and whether or not to edit it.
## content creator
### person with global view of subject organization who does organizing of the content of the slices
### person with detailed subject matter knowledge creating articles (may not even know their topic is part of a slice)
### question: teachers creating wikislices? teachers collaborating with wikipedia about content of a wikislice?
### question: who makes the indexes (subject index and title index)?
### (**SJ: "Teachers, students, parents, subject experts, enthusiasts, global educators."**)
## content maintainer
### someone (teacher? wikipedia people? system?) ensuring that the content of a wikislice is up-to-date and accurate and appropriate
### (**SJ:"Systemic prsentation of data on last-update, the existence of newer versions, etc."**)
## content packager
### person who decides that the content is ready to be packaged and deployed on the XO laptop
### question: not much interaction between teachers and wikipedia regarding creation of wikislices?
### question: wikipedia folks want primarily people experienced with wikipedia creating wikislices? (**SJ: "But to create a good wikislice, someone needs to be able to contribute in a way that is meaningful to other creators; that sort of specfic experience is a matter of fluency with the available tools."**)
# Wikislice examples from Anne for your awareness:
## Wikislice project page on Wikipedia: [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Wikislice]
##2007 Schools Wikipedia: [http://schools-wikipedia.org/wp/index/subject.htm]
# Administrivia
## Team agreed to regular meeting time of Thursdays, 10AM Central. Alyson to confirm with those who couldn't make today's call.
## For next time:
### Team: brainstorm individually on use cases based on updated audience descriptions; come to next session prepared to discuss. Store results of individual use case work in wiki.
### Anne: create OLPC wiki space for us to store team documents. ''(done, you're looking at it now)''
### Alyson: send minutes and suggestion for regular meeting time. (done)


----
----
Line 272: Line 129:
===== Use case input =====
===== Use case input =====
Use case 1: End to end, creation to updates, main success scenario
Use case 1: End to end, creation to updates, main success scenario
## a person who is a wiki editor creates the wikislice,
# a person who is a wiki editor creates the wikislice,
## teacher downloads it as ditamap plus dita documents (1 document per page/wiki article, multiple topics per document) and customizes it (potentially targeting individual topics, other topics from other wiki/source) and sends feedback to wiki editor
# teacher downloads it as ditamap plus dita documents (1 document per page/wiki article, multiple topics per document) and customizes it (potentially targeting individual topics, other topics from other wiki/source) and sends feedback to wiki editor
## student reads it and comments and does an assignment
# student reads it and comments and does an assignment
## teacher grades the assignment and sends more feedback/changes to wiki editor
# teacher grades the assignment and sends more feedback/changes to wiki editor
## wiki editor makes changes
# wiki editor makes changes
##teacher is notified and makes the decision to update three of the content resources but leave the others, and repackages for student
# teacher is notified and makes the decision to update three of the content resources but leave the others, and repackages for student


Tools needed:
Tools needed:
Line 300: Line 157:
----
----


===== Outline for web-centric use case =====
=== Useful Links ===

* Wikislice project page on Wikipedia: [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Wikislice]
If we do the Wikipedia->DITA transform as a webservice which can be accessed directly from a web browser which contains a DITA editor, we might end up with a simplified workflow that goes something like:
* 2007 Schools Wikipedia: [http://schools-wikipedia.org/wp/index/subject.htm]
# pick a wiki slice page, and copy its url
# paste the url into the DITA builder window
# a process on the server converts the wikislice into a DITA map, including pulling in headings from within each page (so the minitoc for each page is accessible from within the dita map)
# the teacher edits the map, including editing the minitoc branches, until they have an outline they're satisfied with.
# they click "store local" and it gives them a place to store the map (they could also choose to store on a public site like Curriki for sharing)
# they can click "merge" to combine two maps, potentially from different sources
# they can click "build package" to create a PDF or HTML

If it's all logic running on the server, then the only thing they store locally is the edited DITA map, and the output. The DITA content is an intermediate step only.

The map could still store time stamps for each page, so the next time a teacher goes to the site they could click "check for refresh" and it would tell them whether there's new content in the pages they're using - then click "refresh package" and it would rebuild if they wanted to.

Next step up would be to allow editing of the individual topics as well. But even the level of editing the TOC (down to the heading level within each page), plus generating some content-type-specific summaries etc., should create some interesting cases, and with absolutely minimal overhead on the teacher's machine.

It would also be easier to demo and share, since anyone with a net connection could use it.

=== Useful Links and Related Ideas===
* Wikislice project page on Wikipedia: [Wikipedia WikiProject_Wikislice http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Wikislice]
* 2007 Schools Wikipedia: [Schools-Wikipedia.org http://schools-wikipedia.org/wp/index/subject.htm]
* Semantic MediaWiki extension to MediaWiki: [Semantic MediaWiki http://semantic-mediawiki.org/wiki/Help:Introduction_to_Semantic_MediaWiki]


Adam Hyde, founder of FLOSS Manuals just sent this page link to me:
[Wikimedia Labs Wiki to Print http://en.labs.wikimedia.org/wiki/Wiki_to_print]


We might want to investigate for the Wikislicing project, and see if we can get DITA on the list with DocBook.
----
----
----
----

Latest revision as of 21:46, 17 April 2013

See also the Wikislice and DITA pages, and the WikiBrowse project

Project Page: OLPC/DITA/Wikipedia/Wikislice project

Team mission

To deliver a proof of concept that demonstrates how to create custom curriculum materials from Wikipedia for OLPC. Our objectives include:

  • use DITA to pull content from Wikipedia in the DITA format
  • deliver Wikipedia resources in an interchange-friendly and semantically-rich set of DITA-specialized topics that can be used as classroom materials
  • integrate DITA topics using a DITA map derived from a wiki slice

Join us!

We're looking for volunteers! Specifically, we're recruiting XO teachers to help us identify design requirements and provide feedback on our approach and prototypes. Because this project is designed primarily for the XO teacher, we have a major dependency on XO teacher insights to ensure the success of this effort. In addition, we're looking for members of the OLPC development community to collaborate with us. So... interested in a humanitarian project that also includes cutting-edge technology and complex content management? Join us! Please comment to this page and provide your email address if interested -- Alyson Riley, our team's project manager, will contact you to discuss your interests and opportunities, as well as your participation level and available time commitment.

Team members

Members of our team include:


Team meetings

Team meeting details are as follows:

Meetings are currently scheduled monthly, using the conference info posted on the Google Group wikislice project. Please contact Lynda Chiotti for info.

See below for meeting minutes; the most recent team meeting appears first.

Team meeting, 06 May 2009

Attendees: Michael, Lynda

Discussion: Michael reported from the recent DITA North America conference a new proposal for a mashup subcommittee, looking at combinations of DITA and data, starting with, for example, the semi-conductor and retail industries. This becomes relevant for this committee because if we can get wikipedia material into a structured format, it becomes mashable. Another proposal from the conference was a subcommittee looking at DITA for the web. A draft charter will be circulated and any Oasis members could participate.

We discussed a full relaunch of this committee to get things going again, starting with a recasting of the mission statement. With a list of deliverables, skills, and roles needed, we could broadcast a call for participation. Given that we have achieved the proof of concept, we can expand beyond XO teachers and go to web-based more generally accessible capability.

Action needed: Existing committee members are invited to draft new wording for the wikislice committee mission statement. Discussion as the wording is developed can take place in the Google Group. Lynda will undertake to start the discussion, with a draft available for the next meeting.

Team meeting, 01 Apr 2009

Attendees: Laura, Lynda Regrets: Michael P, Mary Ann

Agenda: 1. Introductions 2. Meeting frequency and meeting notes decisions 3. Revisit mission statement to make sure we all understand why we exist 4. Update on specific activities: Infoslicer, others? 5. Action items

Discussion: Laura provided the update on Infoslicer as follows. since release in January 2009, has had some GUI tweaks to make it more Sugar-like. Infoslicer to be included in next release of Sugar on a Stick (bootable USB version of Sugar).

Action needed: Need more people actively working on infoslicer, especially with coding ability. Need to figure out what else this committee should work on, eg., a web function based on some of infoslicer code. Can we do some user testing on current version of infoslicer?

Team meeting, 9 Oct 2008

Invitees: Alyson, Anne, Andy, James, Laura, Lynda, Michael P, Michael B, SJ, Salim, Scott

Agenda:

  1. Demo Infoslicer Sugar Activity

Discussion Awesome presentation by Laura.

Team meeting, 18 Sept 2008

Invitees: Alyson, Anne, Andy, James, Laura, Lynda, Michael P, Michael B, SJ, Salim, Scott

Agenda:

  1. After August hiatus, time to regroup:
    1. Update on Extreme Blue project
    2. find coders/sponsors for web implementation
    3. create prototype per Michael's outline
    4. engage with related teams - per SJ
    5. get end user participation/involvement
  2. Team membership updates

Discussion:

  1. Report from Extreme Blue: The students' last day is this week. They're working on a video or e-meeting demonstration of the project results. Laura is working with legal on the intentions to open source the project. Currently it pulls down content from Mediawiki (the engine that Wikipedia runs on) and maps all the content to DITA reference topics. It tracks the version of each sentence so that it can trace back to changes. Doesn't yet get updates from Wikipedia after the content is pulled down. Basically the content is stored in a "library" which contains multiple nested DITA maps. Next meeting we will get to see a demo of the project. There is an opportunity to create a web service (single button press on a web page) to start all the slicing. Michael and Anne took action items to find an interested developer who would like to create this web service.
  2. Report on related teams: The WikiBrowse project takes Wikipedia pages with a high number of interest in the pages and creates an offline version of Wikipedia that can be carried around on the XO. This project fits nicely with our aims and offers an offline scenario. The BookSprint project was a documentation project co-managed by OLPC, Sugar Labs ([1]), and FLOSS Manuals ([2]). While there is not a DITA tie in (FLOSS Manuals uses TWiki and XHTML but it is structured), the content from the BookSprint is available in the new Help (activity).
  3. Report on end-user participation/involvement: Anne still has contacts who are willing to help with a teacher survey or testing. After the demo, we can demo the results to groups like the teacher end-users.
  4. Since the wiki page was getting a little large, I moved all other meeting notes to a /TeamMeetingNotes page.

Team deliverables

Please use this place to store team work items and outputs.

Audience/Actor descriptions

See also descriptions and discussions in Apr 16 meeting minutes.

  1. content consumer; teachers, students
  2. content creator; teachers, students, parents, subject experts, enthusiasts, global educators
  3. content maintainer
  4. content packager; Someone familiar with existing tools

Assumptions

Placeholder -- place for us to store our assumptions.

Use cases

This section contains work-in-progress use case information.

Use case input

Use case 1: End to end, creation to updates, main success scenario

  1. a person who is a wiki editor creates the wikislice,
  2. teacher downloads it as ditamap plus dita documents (1 document per page/wiki article, multiple topics per document) and customizes it (potentially targeting individual topics, other topics from other wiki/source) and sends feedback to wiki editor
  3. student reads it and comments and does an assignment
  4. teacher grades the assignment and sends more feedback/changes to wiki editor
  5. wiki editor makes changes
  6. teacher is notified and makes the decision to update three of the content resources but leave the others, and repackages for student

Tools needed:

Tool to select or extract of articles from Wikipedia into DITA. Note: on the Wikislices page, there is a need for curation that involves finding/listing selections: they say "something like an apt-get service for collections that have been named [and made] (optional: bundle-on-demand, if the bundling takes time; or if a named bundle invokes "get latest version" rather than "get specific revision")."

Tool to organize Wikipedia articles (DITA map editor) on the XO laptop

Tool to edit Wikipedia articles from a wikislice selection for inclusion in Wikipedia on the XO laptop

Use case 2: Reading a wikislice on the XO

    1. Wikislice available on the Internet or school server,
    2. Student or teacher selects relevant wikislice by using the Browse Activity

Use case 3: Creating a wikislice, deploying to XO for offline or online reading

Use case 4: Refreshing a wikislice, deploying to XO

Use case 5: Updates, deploying to XO and sending updates to Wikipedia

Outline for web-centric use case

If we do the Wikipedia->DITA transform as a webservice which can be accessed directly from a web browser which contains a DITA editor, we might end up with a simplified workflow that goes something like:

  1. pick a wiki slice page, and copy its url
  2. paste the url into the DITA builder window
  3. a process on the server converts the wikislice into a DITA map, including pulling in headings from within each page (so the minitoc for each page is accessible from within the dita map)
  4. the teacher edits the map, including editing the minitoc branches, until they have an outline they're satisfied with.
  5. they click "store local" and it gives them a place to store the map (they could also choose to store on a public site like Curriki for sharing)
  6. they can click "merge" to combine two maps, potentially from different sources
  7. they can click "build package" to create a PDF or HTML

If it's all logic running on the server, then the only thing they store locally is the edited DITA map, and the output. The DITA content is an intermediate step only.

The map could still store time stamps for each page, so the next time a teacher goes to the site they could click "check for refresh" and it would tell them whether there's new content in the pages they're using - then click "refresh package" and it would rebuild if they wanted to.

Next step up would be to allow editing of the individual topics as well. But even the level of editing the TOC (down to the heading level within each page), plus generating some content-type-specific summaries etc., should create some interesting cases, and with absolutely minimal overhead on the teacher's machine.

It would also be easier to demo and share, since anyone with a net connection could use it.

Useful Links and Related Ideas


Adam Hyde, founder of FLOSS Manuals just sent this page link to me: [Wikimedia Labs Wiki to Print http://en.labs.wikimedia.org/wiki/Wiki_to_print]

We might want to investigate for the Wikislicing project, and see if we can get DITA on the list with DocBook.

Contacting XO Teachers

Note from Anne: Many apologies for the copy/paste from email threads, but I needed to get this shared in a way that conveys the threaded nature of the connections made here...


From Yama Ploskonka <yama@netoso.com>, http://wiki.laptop.org/go/Profiles/yamaplos The big *maybe* is that no one, in any official, Boston-based OLPC deployment, local or foreign, has reported anything at all that I have heard about XO use connected to the curriculum. (Note from Anne: I need to be careful of the term curriculum vs. content. There are widely different meanings for each.)

The closest thing is a cooperative History-related text written by Uruguayan kids (in pen?), and then copied into an XO. http://www.ceibal.edu.uy/portal/wiki/index.php/Artigas

By the way, it is indicated there that their primary source was a 1964 book, from which they quoted.

  • Yes*, in non-sanctioned experimental events, with usually an outsider volunteer bringing a few XOs for a few days, XOs have been used in conjunction with formal curricula. One recent example:

http://www.olpcnews.com/countries/greece/using_xos_in_greece.html For obvious reasons, these being ephemeral, it is hard to get feedback that could be re-fed.

  • No*, in the sense that *in my opinion*, while Wikislicing is something that is going around the community, so far I believe OLPC-Boston is not interested in connecting XO use with school curriculum. They are about exploring, creating, etc.

Complicated? yes. Hopeless? no. It is possible the lack of reports has more to do with teachers simply using the things, and not reporting.

I will put the question for the Sur list. (Yama's Spanish OLPC list, http://lists.laptop.org/listinfo/olpc-sur)

Adam and Bjorn are connected with the Ethiopia deployment Bjorn Everts <Bjorn.Everts at eduvision.ch>, Adam Abate <aabate at apposit.com>,

Bryan with Nepal http://wiki.laptop.org/go/Profiles/berrybw, Bryan Berry <bryan.berry at gmail.com>

Edward just cares about things Education in general, and often is aware of things I have not seen, and able to help you in this better.

>> Guys, route (Anne's request) as you see fit, this is something that I believe makes a lot >> of sense in your deployments and might be of immediate use to y'all while it >> might be a steep curve for Uruguay and Peru to get to use it (they still >> have to solve the server issue).

From Edward Cherlin Wikibooks has a book on education written by students.

I have thought about using Wikipedia in subject matter and language classes, where an entire class would be assigned to research and write a page on a new topic or to translate and adapt an existing page. Then the class could collaborate on a version combining the best contributions from each student, and post the result. It would be necessary to have a progression, starting with simpler tasks such as checking references, fixing spelling and grammar, researching disputed points, adding references where they are lacking, and so on, before creating whole pages. And before that, some sandbox exercises on Wiki formatting.

The resulting curriculum and detailed information, including student feedback on what works and what doesn't, could then be edited and published as a Constructionist demonstration and guide.

There is a project coming together but not announced that could use a Wikislice on environment and ecology in Spanish, with detail for the area in question. I will be talking to GIS specalists about bringing together maps and related data. We would like to get the students in the region to gather data, take pictures, and so on, and add their observations to the data set. We will have professional guidance and assistance on all aspects of the program, including curriculum development. We would like to publish the specific results for this region, and the plan for doing it in any region.

I would like to do a similar project in the Arahuay region, bringing in specialists to work with the community on a plan for sustainable development. I am assured that much is already known that would help the local farmers and others, and that solving some of the remaining problems there will benefit many other regions, possibly the whole world.

Useful Background Information

Paraphrased from an email from SJ Klein, November 20, 2007:

"We need to implement concrete use cases, using DITA with an editor and publishing pipeline. Say, use the DITA open toolkit, a specific editor, and one of the wikiproject:wikislice slices, and trying to keep up with changes to the slices.

My default for the 'final format' of the edited work would be an html collection, one html file per article, that preserves internal links to other articles in the slice, and leaves out broken links (or converts them into external links to wikipedia).

Identify added value that can come from having this structure to the data, other than identifying red/blue links.

Then it would help to contrast using DITA as an interchange with some of the simplest options: - using no metadata at all and having a named URL that always contains the latest version of a wikislice - using a static set of metadata that get updated when things change, along with a version number that is incremented."

Michael and SJ discussed a few core use cases: maintaining and updating a stream that many people may be contributing to; and maintaining the latest version of a package that many people may be committing to, and which has some sort of 'latest' version.

Some distinctions to be made follow. It would be interesting to see specific implementations of the following notions in DITA format. 0) distinguish map updates from content updates

1) distinguish streams from patch updates to a static object that 'improves' over time

2) provide for pre- and post-filters; a pre-filter might be by keyword; a post-filter might be a transparent redirect for links that don't exist locally; keys that are resolved locally or externally.

3) other dimensions for feeds/streams:

- read-only v. read-write interaction with both streams and packages. Think of the latter as "two-way streams" and "distributed patch updates for packages" - linear v. distributed orderings (a single time-ordering, or a distributed patch-ordering) - whether there are constraints that need to be applied when things are edited for read-write collections. michael : "export v feed"? perhaps the wrong term.

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Projects/Wikislice&oldid=284377"