Community Wishlist Survey 2020/Wikiversity

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

Community Wishlist Survey 2020

Wikiversity
20 proposals, 20 contributors

Go-previous.svg Wikispecies  •  Wikivoyage Go-next.svg

The proposal phase has ended.
Come back on November 20 to vote on proposals!


Transclude wikipedia template, module pages on small project as Wikiversity

Edit proposal/discussion

  • Problem: On Wikiversity as on other small wikimedia online projects, we don't have a user community big enough to compete with Wikipedia template and module creation. So we must usually import them from Wikipédia. Especialy on Wikivesity because the pedagogical project is very close to the encyclopedic one in term of edition. Same bibliographic citation for instance. Actually, the import and update work make by administrator is not easy. We are doing this with the page special:import and it's a real nightmare if we want to merge history of pages in the respect of the license and the transparency.
  • If a page name already exist on wikiversity with an other contain or function, the import overwrites the old page to establish the new one. By the way, trouble on the website organization can arise (example of conversation that appear in French Wikiversity after a template importation : https://fr.wikiversity.org/wiki/Sujet:V8jhz8s6sp17evpx).
  • Actually, the import option « Include all models » of the page special:import is really risky because of that. Finally the template or module pages must be frequently updated due to their evolution on Wikipedia and that's also a difficulty for administrators to make this repetitive task.
  • Who would benefit: Wikiversity and potentially other small wiki administrators and users.
  • Proposed solution: Extension:InterwikiExtracts permits to transclude articles from one Wikimedia project to another but unfortunately not template or module pages. A similar MediaWiki extension for template and module could be so a very powerful tool for enhancing collaboration and contain integration between all Wikimedia project. That's also a good way for not duplicate content from one project to an other and to concentrate the force of all Wikimedia technical contributors on single pages and single place. In the long run, a multi language Wikimedia technical commons, similar to Wikimedia Commons but for gathering template, modules, gadgets, and other technical wiki pages available for all projects and transcludable with an exention as scary transclusion could be a great idea!
  • More comments:
  • Phabricator tickets:
  • Proposer: Lionel Scheepmans Contact French native speaker, sorry for my dysorthography 00:39, 29 October 2019 (UTC)

Discussion

Import top features from UDEMY, MOODLE, docebo

Edit proposal/discussion

  • Problem:
  1. Don't have a modern LMS interface so that it could support top features from MOODLE,UDEMY like VIDEO/audio course's & PROGRESS REPORT/ Performance related Features, Options & Policies.
  2. Don't have implemented A.I features at the Wikiversity's core like DOCEBO LMS have, so that it could provide more interactivity, deep and effective learning experiences.
  • Who would benefit: The Wikiversity users , course authors .all the learning community that Wikimedia Foundation project can support.it will certainly give a boost to fulfill Wikiversity & the wikimedias goal.
  • Proposed solution: First of all, "community tech team" would know the best way to implement these "NEEDS" in wiki environment. They are the expert's. MOODLE is in "open license".

    "Kaltura" already have most of the video related solutions that are required. we should contact with them to get assistance. mw:Extension:TimedMediaHandler tech Team would know better.

  • More comments: Some Concerns:
    1. Wikimedia movements, policy,mediaWiki software are heavily depending on "TEXT" related content which is working nicely for all other wiki projects but not for Wikiversity. "Smart Interactivity" & "Video Courses" became the "Right Choice" for all the learning community.
    2. Online assessment, in details progress/performance report For both course author & learners is the top features of any LMS.UDEMY is the number 1, cause they are applying it nicely along with 'attendance statistics' for both. I fear it will not be possible to implement in Wikiversity just because of the current policy.
    3. The current policy heavyly prioritizing "Anyone-Can-Edit" over "Quality Standards".UDEMY also applying "Anyone-Can-Edit" while maintaining a proper "Quality standard" and became successful as a learning community. Along with the traditional Wikiversity course type it should add some other course types ,like instructor-led, self-paced or Mixed, for some specific courses.
    4. UDEMY have a "Quality Review Team" which evaluate's all the course before it go to live .They are not subject wise "expert" but only evaluate the "content" quality. Which is very much needed in Wikiversity.But I fear, it also will not be possible for Wikimedia, Wikiversity to adapt this features.
    5. (Wikiversity:Wikiversity community) 'It say's, Wikiversity isn't participating in conventional courses just because the "wiki interface" isn't appropriate for these. And to get all the wiki environment power it should n't change this process either'.I don't like what it sounds , couse it neglecting the Wikiversity's ORIGINAL GOAL. shouldn't it go the other way around.
    6. I believe,To fulfill foundation's mission Wikiversity should evolve beyond the "wiki environment" .Wikiversity wanted to became the supporting platform for the all the "Learning community", but it didn't . in reality ,(in 2019) when people see these learning community like UDEMY ,Lynda.com or full featured LMS like MOODLE ,DOCEBO then they know what they want .That's why & to fulfill the "mission" it must evolve.

    The mission of the Wikimedia Foundation is to empower and engage people around the world to collect and develop educational content under a free license or in the public domain, and to disseminate it effectively and globally.

    In the beginning ,Wikiversity's fundamental goal was, to broaden the scope of activities within the Wikimedia community to include additional types of learning resources in addition to textbooks. After 13 years,fundamentally it didn't improved much while in the meantime Learning management system (LMS) improved so much that it have some great standard's. Learning community became heavily dependable on MOODLE. Then came docebo, a LMS that use learning-specific artificial intelligence algorithms to produce deeper and more effective learning experiences. It is proven that, in learning community "interactivity" & "VIDEO" is equally or more important then "TEXT" content.

    Udemy allows instructors to build online courses on topics of their choosing by Using "course development tools". Authors can upload video, PowerPoint presentations, PDFs, audio, zip files and live classes to create courses. Authors also have features to engage & interact with user and getting feedbacks which is very very important for any learning platform.

    Wikiversity should maintain a certain standard. implement some extra reviewing featurs in "curator" ,"custodian " user group or make a "video reviewer" user group .they could only review video content to make sure it maintain the quality standard.

    Wikiversity is a center for the creation of and use of free learning materials, and the provision of learning activities.

    The project states that that's why it should became a full featured LMS (along with a learning community) as long as it's within Wikiversity's policy. I know these 2 "NEED'S" & my "concerns" are huge & very very complex tusk for the community tech team/foundation to complete in short time (2-4 years).

    But we can all agree in that, we NEED these 2 features very very much.

  • Phabricator tickets:
  • Proposer: MASUM THE GREAT (talk) 14:48, 23 October 2019 (UTC)

Discussion

  • i like the idea in the sense that educational features should be implemented. the best example i know is edx. see e.g. python for data science. maybe you want to reformulate a little, focus more? --ThurnerRupert (talk) 05:50, 24 October 2019 (UTC)
  • I like the idea, too, and think it could be very useful in general to adopt advanced learning tools on Wikiversity taking inspiration from other learning platforms. --Daniele Pugliesi (talk) 20:56, 30 October 2019 (UTC)
  • MASUM THE GREAT, thank you for submitting this proposal! This wish could be very exciting; it's just too large (for the Community Tech) in its current form. So, we have an idea for you: Perhaps you could identify one feature in this wish that you would like to be implemented. Alternatively, you (or other members of the community) could submit multiple features as as separate wishes. Thank you—and we look forward to see if there are updates to this wish! --IFried (WMF) (talk) 21:43, 30 October 2019 (UTC)
Thanks IFried (WMF). Feel free to split this proposal by any means. If community tech team have to (heavily) narrow it down to 1 simplest proposal then they should choice "progress report" features, just saying.--MASUM THE GREAT (talk) 13:45, 1 November 2019 (UTC)
Currently I'm working to make it 3 different proposal. Please be Patience.--MASUM THE GREAT (talk) 13:29, 5 November 2019 (UTC)
Hello @IFried (WMF): ,@MusikAnimal (WMF):

.I've already split this into 2 different proposal. Please see 'PROGRESS REPORT Feature' & 'Modern Interface for Video Course's' .

If you want to remove this proposal then please replace it with 'this (my 3rd proposal)'

Any kind of advice is welcome. Many Many Thanks .--MASUM THE GREAT (talk) 15:05, 10 November 2019 (UTC)

  • Good idea. Wiki Movimento Brasil User:joalpe is working on a Moodle format for Wikiversity.

--Lgjunior

  • Merge with ThurnerRupert's "electronic course features analysis" proposal? The anyone-can-edit/quality-control issue seems separate from the technical capabilities, and as it is more political than technical, the Community Wishlist may not be a good place to discuss it. HLHJ (talk) 22:30, 3 November 2019 (UTC)

ContentTranslation for Wikiversity

Edit proposal/discussion

  • Problem: the tool ContentTranslation actually only works on Wikipedia. It would be useful on Wikiversity for translating pages for one language to an other.
  • Who would benefit: contributors and students
  • Proposed solution: install ContentTranslation on Wikiversity
  • More comments:
  • Phabricator tickets:
  • Proposer: Lionel Scheepmans Contact French native speaker, sorry for my dysorthography 18:30, 29 October 2019 (UTC)

Discussion

Sample skins for presentations

Edit proposal/discussion

  • Problem: There are users, who create their presentation on Wikiversity itself and try to create their own skin for them. The skins are not perfect, due to the lack of CSS knowledge and thus cannot be use in main namespaces.
  • Who would benefit: Everybody interested in the topic. Presentation placed on Wikiversity as a simple text provide more opportunities for collaboration and learning than presentation left in PDF on Wikimedia Commons. Different skins would provide easier way to use Wikiversity for the use in lectures and at the same time easier colobarative creation.
  • Proposed solution: Create five sample skins in CSS for lectures/presentations, which might be attached to a special namespace or taken by users individually when willing to use Wikiversity for presentations.
  • More comments: Example: v:en:User:Juandev/CEE19/Structured Data on Wikimedia Commons is handled by a skin in v:en:User:Juandev/monobook.css
  • Phabricator tickets:
  • Proposer: Juandev (talk) 07:36, 4 November 2019 (UTC)

Discussion

Juandev, if I've understood you correctly, this is similar to the #Wiki-based slideshows/posters proposal. Would a merge be OK? If you want to merge it, please do. HLHJ (talk) 00:59, 8 November 2019 (UTC)

Well, I am not sure. Poster proposal is about having one simple skin for all Wikiversity pages, this colls for multiple skins. Maybe you can merge it, but ask for more skins, from which the person willing to present directly a Wikiversity page could change. Like we have more skins in our preferences for hole wiki (Monobook, Vector, chicken). I wonder if this is an extension, it could work pretty well for every wiki project and e.g. Wikipedia presentation would benefit out of it also. Juandev (talk) 10:01, 10 November 2019 (UTC)

Autopopulate userpage starting info from ORCID

Edit proposal/discussion

  • Problem: When new users who already have an ORCID account create a Wikimedia account, their userpage is initially blank despite useful info existing to populate it
  • Who would benefit: New Wikiversity users commonly have ORCIDs and also commonly edit under their real names. This may also be relevant to that subsection of the Wikipedia community who also does
  • Proposed solution: When new users sign up to Wikiversity, ask if they have an orcid account and whether they would like it to be used to initially populate their new userpage. Various levels of integration are possible, but may also be an initial step towards ORCID also listing wikimedia contribution summary stats or featured articles in ORCID profiles. See also Meta:ORCID.
  • More comments:
    • Option 1) Just auto add an {{authority control}} template based on the orcid
    • Option 2) Copy over basic information from ORCID to populate the userpage
    • Option 3) Add/transclude their scholia profile to the userpage
    • Option 4) Allow users to verify their ORCID and associate it with their Wikimedia identity
    • Option 5) Allow users to log in using their ORCID profile
  • Phabricator tickets: (T136943 for option 4/5)
  • Proposer: T.Shafee(Evo﹠Evo)talk 10:42, 29 October 2019 (UTC)

Discussion

PROGRESS REPORT Feature

Edit proposal/discussion

  • Problem: Need a Performance related Feature for both The Reader's & Author's.
  • Who would benefit: The Wikiversity users , course authors .all the learning community that Wikimedia Foundation project can support.it will certainly give a boost to fulfill Wikiversity & the wikimedias goal.
  • Proposed solution: To implement this features we can take a approach similar to moodle's ."Activity completion"

MOODLE is in open licence.

like this one Electric_Circuit_Analysis or this. Introduction_to_Computers

Discussion

I think this is hardly applicable at this stage of Wikiversity when there is not a uniform method or platform for course creating. I wonder that this solution would also need some programming on the site of Wikiversity like creating course platform, which will have a stable format and which will allow developers to plug other features like progress report. Juandev (talk) 21:46, 10 November 2019 (UTC)

Managment of research name space title on fr.wikiversity

Edit proposal/discussion

  • Problem: Specifically on French wikiversity, we decided to create a name space for research article. But since this decision we still have a proble to hide the « namespace: » displaying on articles' title.
  • Who would benefit: Editors and readers of research name space on fr.wikiversity
  • Proposed solution: Actually, the solution to hide the name space on the title is to to use the template Titre incorrect in a research presentation banner template. But this solution create a bug displaying in French just after saving a new edition with this text : "En raison de limitations techniques, la typographie souhaitable du titre, « ... », n'a pu être restituée correctement ci-dessus.". That's a bite annoying.
  • More comments:
  • Phabricator tickets:
  • Proposer: Lionel Scheepmans Contact French native speaker, sorry for my dysorthography 11:22, 6 November 2019 (UTC)

Discussion

Export published WikiJournal articles to DOCX or PDF

Edit proposal/discussion

  • Problem: After a WikiJournal paper has been accepted for publication, it requires a labour-intensive process to customize the layout, formatting and front page. This process is currently done manually and will become an impediment as the journal scales up and accepts more submissions. The previous PDF generator has been offline for a while.
  • Who would benefit: WikiJournal editors in particular, and anyone who prefers to read content in a PDF format (including Wikibooks).
  • Proposed solution: The current process becomes automated upon article acceptance.
  • More comments: Related: Wikibooks#EPUB_generation
  • Phabricator tickets:
  • Proposer: OhanaUnitedTalk page 14:40, 1 November 2019 (UTC)

Discussion

  • Support PDF generation. I'm not sure about DOCX, but certainly exporting PDFs is a very common feature of academic publishing. —Justin (koavf)TCM 19:39, 2 November 2019 (UTC)
  • This is a good point, there are other projects and subcommunities in Wikiversity, who may benefit. We used to publish an educative magazine on Czech Wikiversity. Juandev (talk) 08:36, 4 November 2019 (UTC)
  • Would this feaure allow export of any wiki page? I think that it would be useful for offline use of articles from other wikis. If a reader just copies text from a page into a word processor, it is likely that the resulting document won't have the correct attribution. If the wiki offers a word processor friendly export, we can facilitate correct offline reuse. The format need not be Docx, but should be somthing that opens easily in Microsoft Word, Google Docs, Libre Office or elsewhere. AlasdairW (talk) 23:32, 7 November 2019 (UTC)

Wiki-based slideshows/posters

Edit proposal/discussion

There is often a small screen facing the presenter, and a big screen facing the audience; the presenter's screen may show slide notes and timing information
  • Problem: Currently, if you want to upload a presentation to Wikimedia, you convert it to a PDF and put it on Commons. This format is not easily modifiable, reusable, or accessible. If you want to display Mediawiki pages on a big screen, you can use the F11 key to fullscreen the browser content (try it now; hit F11 again to return). But that leaves the screen cluttered with Mediawiki sidebars, and there are no convenient navigation functions for switching between slides.
  • Who would benefit: Anyone wanting to give a slideshow talk, or reuse wiki content in a talk, or vice-versa. Wikiversity users have a particular interest in putting lecture slides online.
  • Proposed solution: A Mediawiki implementation of a web-based slideshow, allowing wiki pages to be used as fullscreen presentation slides. A good addition would be a download/export function to get a flat file containing the presentation. Ideally, there should be second screen capability, so that the presenter can also see a countdown timer and a short set of point-form notes per slide.
  • More comments: Mediawiki obviously already renders in browsers, so this might be a fairly easy way to provide a really useful functionality. It could also attract users and content to Wikiversity.
    • The same format could be used to display an academic poster, made with existing Wikiversity tools, on a screen. SVG already does this well, but less wiki-reusably.
    • The W3C has a (flat-file) format and freely-licensed implementation, HTML Slidy, which might be useful. It exports/is XML; PDF export might also be useful, and might overlap with the article-export proposal.
    • I'm not sure whether it would be appropriate to do this with a skin (skin experts, I'd welcome your comments). If a skin with slide-navigation functions would be OK, then we could do the rest with a template taking, as parameters, a list of the wiki pages/sections to be used as slides, and displaying a slide-thumbnail menu with switch-skin links. Any page with that template would then become a slideshow. Perhaps second-screen capability could be done with a popup?
  • Phabricator tickets:
  • Proposer: HLHJ (talk) 23:45, 3 November 2019 (UTC)

Discussion

Your proposal could be found in these proposals:

Juandev (talk) 10:00, 6 November 2019 (UTC)

Sorry, Juandev, just saw this. I'd be happy to merge to this proposal with the sample-skins one. I think the article-PDF proposal has a different goal, although it would be possible to use some of the same technical tools in doing both. I've tried to separate the wish from possible implementation methods, as I am not the best judge of the latter, but I've mentioned the possible overlap in the proposal. HLHJ (talk)
Thanks to Bawolff for assessing the technical difficulty ("at a glance sounds do-able and an apprppriate difficulty level for community wishlist"). HLHJ (talk) 18:37, 9 November 2019 (UTC)

Export pages as JATS-compliant XML

Edit proposal/discussion

  • Problem: Journal Article Tag Suite (JATS) is a standardised way of representing article content and metadata in a way that is more easily machine-readable. It is used for a wide range of data mining (especially in combination with Wishlist_2020/...uploading_academic_papers_to_Wikisource).
  • Who would benefit: Wikiversity (Wikijournals in particular), but also Wikisource and possibly Wikipedia.
  • Proposed solution: Develop a way to include simple JATS XML tags within the content of a page (automated where possible) and generation of JATXT XML metadata from info in linked wikidata page
  • More comments:
  • Phabricator tickets:
  • Proposer: T.Shafee(Evo﹠Evo)talk 08:05, 9 November 2019 (UTC)

Discussion

Speed reading video option for wikiversity MOOCs

Edit proposal/discussion

  • Problem: Some MOOCs in French Wikiversity include videos (example), but the video player does not allow users to change the playback speed. Watching at a faster playback speed saves time.
  • Who would benefit: Video viewers on Wikiversity
  • Proposed solution: Updating the Wikimedia video player
  • More comments:
  • Phabricator tickets:
  • Proposer: Lionel Scheepmans Contact French native speaker, sorry for my dysorthography 01:03, 29 October 2019 (UTC)

Discussion

I like this idea. I prefer to watch talking-heads informative videos at ~double speed. Slowly trawling through a video is very frustrating, especially when you are just trying to find one fact. Adjustable playback speed would benefit other projects, too; if this proposal therefore gets turned down as out-of-scope for this year, please to re-nominate it next year. I have boldly polished the English, please revert or modify if I have misunderstood you. HLHJ (talk) 21:53, 3 November 2019 (UTC)

Definitely a good idea! Juandev (talk) 08:31, 4 November 2019 (UTC)

The new video.js beta player does have the ability to change playback speed. It would however require some software change to expose that feature conditionally (showing it all the time is not going to be efficient on most of our other sites. Oh btw, depending on your browser, it is sometimes possible to right click the video and adapt the playback speed in that way. —TheDJ (talkcontribs) 13:21, 4 November 2019 (UTC)

Ability to change the license listed at the bottom of the page

Edit proposal/discussion

  • Problem: The license at the bottom of each pages is the same site wide. This is less appropriate for sites that may have different licensing for different pages. This wikiversity example, or wikisource example are both licnesesd CC-BY, yet the bottom of the page still claims that they are CC BY-SA (No idea what the page metadata says).
  • Who would benefit: Those making any pages that aren't CC BY-SA
  • Proposed solution: Simply allow display of different licesnse (and altered page metadata) based on a template or category.
  • More comments:
  • Phabricator tickets:
  • Proposer: T.Shafee(Evo﹠Evo)talk 08:24, 9 November 2019 (UTC)

Discussion

Extension:Page forms on WMF servers

Edit proposal/discussion

  • Problem: Information is often far better input via a form rather than editing wikimarkup (like this page). Especially when either A) the same fields will be repeatedly required or B) when new users are involved. New users are often put off my wikimarkup, even when templates and preloaded text is used (example). This leads to projects and affiliates often using google forms in stead then copy-pasting the information to wiki (example). Currently a small number of outstanding issues remain on the Pageforms Extension that could address this by making an in-house, general-purpose form tool with structured inputs.
  • Who would benefit:
Example use case in wikiversity: It'd be great to be able to use this peer review submission form rather than the current system (peer reviews are submitted via this google form, which deposits them to a google spreadsheet like this, where they're copied to the relevant article talkpage, and noted down on this tracking table, and maybe at some point will have their metadata added to Wikidata).
  • Proposed solution: Finish fixing the last few bugs in mw:Extension:Page_forms in order to implement om WMF servers.
  • More comments: Using more structured input has already been useful for (e.g. the commons upload wizard). A general solution for use in other contexts would be hugely useful.
  • Phabricator tickets: T149869
  • Proposer: T.Shafee(Evo﹠Evo)talk 04:04, 2 November 2019 (UTC)

Discussion

  • No argument that this would be very useful. The phab ticket selection suggests that the main blocker on this is some outstanding security issues in the Page Forms extension (Page Forms on Phab, and the Extension page). Is this the case, or are there other major issues? HLHJ (talk) 22:22, 3 November 2019 (UTC)
  • Strong support. Better form input would help newer editors enter consistent information as well as being able to analyse the resulting structured data. This would be a big win across the board. — Bryandamon (talk) 22:07, 6 November 2019 (UTC)
  • T.Shafee(Evo﹠Evo), thank you for submitting this proposal! We have one request: Can you provide more information on the problem? Right now, we mostly see information on the proposed solution, which we may or may not be able to implement. However, if you flesh out the problem a bit more (in the "Problem" section), we can have a better sense of the potential options to solve the issue. Thanks! --IFried (WMF) (talk) 04:51, 11 November 2019 (UTC)
    @IFried (WMF): Thanks. I've now expanded on it a little from a user point of view. Sadly I don't have enough knowledge to comment on the technical side of T149869. T.Shafee(Evo﹠Evo)talk 05:17, 11 November 2019 (UTC)
    @Evolution and evolvability: Thanks for the update! Your changes helped clarify the problem. --IFried (WMF) (talk) 05:27, 11 November 2019 (UTC)

Transcluding Wikipedia complete article or section on wikiversity courses

Edit proposal/discussion

Discussion

electronic course features analysis

Edit proposal/discussion

  • Problem: it is challenging to create courses.
  • Who would benefit: learners, course providers
  • Proposed solution: create a working group with a single target: analyze learning platforms and come up with a list of features for wikiversity to support electronic courses, see e.g. edX python for data science as an example. this then can be piped into a technical analysis respective feasibility via use existing, build new, not support at all.
  • More comments:
  • Phabricator tickets:
  • Proposer: ThurnerRupert (talk) 05:41, 24 October 2019 (UTC)

Discussion

feel free to adjust/extend the proposal, and add your name as proposer. --ThurnerRupert (talk) 05:41, 24 October 2019 (UTC)

There already a lot of open-source learning-platform software packages. It might be possible to reuse code as well as feature ideas. HLHJ (talk) 22:00, 3 November 2019 (UTC)

I think this is more like a goal for Wikiversity community themselves, not for developers. The Wikiversity community itself should decide what they want, not Wikimedia Tech group. Juandev (talk) 08:39, 4 November 2019 (UTC)

Inclusion of interactive Dimensions, Altmetrics, Crossref badges in pages

Edit proposal/discussion

Discussion

  • This would require some sort of request proxy'ing to avoid any privacy leaks / statistics gathering on our visitors. —TheDJ (talkcontribs) 13:17, 4 November 2019 (UTC)

Improve drag and drop options in Visual Editor

Edit proposal/discussion

  • Problem: There are other more attractive platforms for teaching/learning nowadays. Younger learners cannot read. Some people have difficulties with understanding wiki code.
  • Who would benefit: Wikiversity itself, by attracting more users.
  • Proposed solution: Provide better functionality of drag and drop in Visual Editor. Today, you can move some parts of the text or images within the page edited with the use of VE, but it's still clumsy (e.g. you cannot move the image at whatever position you want). So the proposed improvements might be:
    • allow the user, to drag and drop image at whatever place on the page
    • provide an icon for enlarging/making small the image that the user, can change image dimensions by mouse
    • provide the user with an easy way to create a gallery by moving images within the page by mouse
    • provide other image design on the page other than a gallery (e.g. images in the circle)
    • allow the user to highlight the block of the text, move it and set its background and border color after deployment
    • possibly allow inter-project transclusion, that a sample of text from Wikipedia, Wikibooks, can be drag and drop onto Wikiversity page
    • allow or provide other types of functionality, which will make Wikiversity more attractive and allow it to be used also by younger learners who do not know wiki code or text at all.
  • More comments:
  • Phabricator tickets:
  • Proposer: Juandev (talk) 09:40, 4 November 2019 (UTC)

Discussion

Create official curricula

Edit proposal/discussion

  • Problem: Inconsistent course quality and the general lack of direction for learners.
  • Who would benefit: Learners and contributors
  • Proposed solution: We should create official curriculums, then official courses, like a framework for Wikiversity. Contributors then contribute to improve those curriculums and courses. This way collaboration effort is more focused, increase course quality. This suit Wikiversity better as a open collaboration community. Students will also have better time find the right course.
  • More comments:
  • Phabricator tickets:
  • Proposer: Razel01 (talk) 04:47, 27 October 2019 (UTC)

Discussion

  • It looks interesting, but I did not understand very well the possible details of this proposals. Reading "curriculums" two ideas comes into my mind:
    • "Curriculums of learners": a sort of list of what the learner has learnt on Wikiversity, i.e. completed courses, completed modules, completed lessons, etc. This list could be a self-declaration of learners (simple to implement, but with very poor value in term of "accreditation") or a list generated by an automated mechanism (for example after the completion of a questionnaire that gives a link to the page where everyone can check the questionnaire completed by user - but in this case other users could read it and do the same without studying the subject) or an evaluation made by other users (this case is more difficult to implement, because we do not have so much users competent in each subject and available for doing the evaluation)
    • "Curriculum of editors": it could be a simple list of courses/modules/lessons/etc. at which every users had contributed. In this case I do not see any particular usefulness, because the same information are available in the chronology of pages. Did you have any other idea about it? --Daniele Pugliesi (talk) 20:52, 30 October 2019 (UTC)
  • I think, this is not a work for Wikimedia developer community but for Wikiversity participants itself. As I understood it, you want to have some quality courses to be created right? Juandev (talk) 08:34, 4 November 2019 (UTC)

Wikibase sandbox

Edit proposal/discussion

  • Problem: On Wikiversities we have some database-like research projects (eg. Bloom Clock (beta, cs, en), Dreams (cs)). They are based on collecting observations and further (statistical) analysis. Unfortunately, the core projects are based on technically difficult parser functions and other techniques, which creates difficult its dissemination to other languages mutation or keeping them alive when original creators are gone.
  • Who would benefit: Everybody involved in these projects, gardeners, psychologists and others who may use the results of the research, potential new users, who may be attracted to the new easier way of contribution/participation.
  • Proposed solution: Provide Wikiversity community with sandbox wiki with Wikibase and possibility of creating its own properties and items.
  • More comments: Wikiversity community may experiment with it to see, whether such a solution would ease its database related projects. Other possible uses in teaching/learning might be discovered.
  • Phabricator tickets:
  • Proposer: Juandev (talk) 08:24, 4 November 2019 (UTC)

Discussion

Modern Interface for Video Course's

Edit proposal/discussion

  • Problem: Create an extension only for Wikiversity so that author's can have more easy options when adding 'Video Courses' & wiki functionality will be unchanged.
  • Who would benefit: The Wikiversity users , course authors .all the learning community that Wikimedia Foundation project can support.it will certainly give a boost to fulfill Wikiversity & the wikimedias goal.
  • Proposed solution:

Front-end standards group doing this type of tusk from a long time.

Community tech team could get valuable insight by consulting with them.

"Kaltura" already have most of the video related solutions that are required. we should contact with them to get assistance. The mw:Extension:TimedMediaHandler tech Team would know better.

  • More comments:
  • Phabricator tickets:
  • Proposer: MASUM THE GREAT (talk) 13:44, 10 November 2019 (UTC)

Discussion