Open issues

If you (user A) make a change on a deck, and another user (user B) forks it, your (user A) current deck version becomes view only, and e.g., all intermediate changes on a slide are lost
SWIK-2555
Support reveal.js video backgrounds
SWIK-2551
Deck Landing page test
SWIK-2547
SlideWiki as an LTI Provider (live)
SWIK-2534
Edit an LTI Group
SWIK-2531
Create an LTI Group
SWIK-2530
SlideWiki as an LTI Provider (locally)
SWIK-2518
SlideWiki as an LTI Consumer
SWIK-2517
Use new deck service POST/PATCH calls to partially update deck metadata
SWIK-2436
Improve edit/reorder playlist view
SWIK-2434
Add Drag&Drop to the visual DeckTree and remove unused/unnecessary code
SWIK-2284
Use NavLink tags for links in Deck View instead of <a> tags
SWIK-2233
Services using mongodb should exit once there's no way to reconnect to mongodb
SWIK-2227
Need method of accessing 1st slide other than thumbnail from deckview when tree not visible
SWIK-2220
Allow users to create a deck playlist from a large deck with many sub-deck
SWIK-2090
Questions & Exams - feedback from trials
SWIK-2068
Presentation Rooms
SWIK-1894
Enable progressive display of items in slide
SWIK-1778
download PDF of entire deck or subdeck
SWIK-1770
PDF export https://testing.slidewiki.org/deck/9740
SWIK-1769
Usability / explanation / preview for history tab.
SWIK-1552
Slide content edit test
SWIK-1420
Adapt Performance: webpack to only include scripts and css in defaultHTMLlayout on certain pages
SWIK-1367
Provide Wikimedia content to SlideWiki users via a tab as part of the slidewiki media gallery
SWIK-1353
Improve CKEditor styles managment
SWIK-1334
Refactor use of userstore in SlideContentEditor
SWIK-1316
Remove empty input elements in slide content on slide load
SWIK-1303
Refactor slide edit to make use of react / isomorphic code instead of client-side JS
SWIK-1294
Clip horizontal (left and right) edges of slides in presentation mode?
SWIK-1289
thumbnails of themes
SWIK-1283
Semantic links or homepage for supporting conferences
SWIK-1255
Select text on slide rename
SWIK-1227
Social log in test
SWIK-1209
Move to Redux?
SWIK-1097
Remove hardcoded defaults for new slides
SWIK-1055
Include reverse ordering in "My Decks" page
SWIK-1044
Changing UI language in user profile is not intuitive - is search box and current language needs removal (backspace/delete) before new language can be selected
SWIK-2631
Adding APIs to follow updates on SlideWiki
SWIK-2575
Add option to enable/restart subtitle generation in presentation rooms
SWIK-2476
Create a summary in deck-service that returns the modified deck (ids) from a timestamp
SWIK-2323
Different border for slides in slide view/edit mode to improve visibility and clarify purpose
SWIK-2283
Strip down PresentorHTMLLayout to improve its loading time
SWIK-2280
Improve Presentation Rooms
SWIK-2256
Having a minimum height for slides in the presentation mode
SWIK-2218
allow export of SlideWiki content in Neo4J
SWIK-2189
create a simple markdown editor as an alternative way of creating slides on SlideWiki
SWIK-1866
setup old.slidewiki.org server to refer to our old slidewiki in read-only mode
SWIK-1782
Investigate GraphQL and its connection to Kong
SWIK-1629
Add sr-only to links of users
SWIK-1480
Provide a way for user to add a deck or slide after a subdeck in the tree
SWIK-1396
issue 1 of 54

If you (user A) make a change on a deck, and another user (user B) forks it, your (user A) current deck version becomes view only, and e.g., all intermediate changes on a slide are lost

Description

Involved

Ali and me tested user interaction of forking branching flow on latest experimental/master.

In summary: If you (user A) make a change on a deck, and another user (user B) forks it, your (user A) current deck version becomes view-only, without explanation, and you have a small change that all intermediate changes on a slide are lost (if you did not click on "updated version available in infopanel")

Tested in a fork chain of decks:
User A: Ali: https://platform.experimental.slidewiki.org/deck/4996-3/my-deck-1-1-1
User B: Klaas: https://platform.experimental.slidewiki.org/deck/5001-1/_/deck/5001-1 and deck ID 4997, 4998, 4999 - all copies of a version of 4996 (respectively -> 4996, 4996-1, 4996-2, and 4996-3)

Or:
Ali makes deck 4996
Klaas forks it to 4997
Ali's deck 4996 becomes view only - needs to go to 4996-1 and loses changes.

Klaas forks 4996-1 (haha, sneaky fork!) to create deck 4998
Ali's deck 4996-1 becomes view only - needs to go to 4996-2 and loses changes.

Klaas forks 4996-2 (haha, fooled you once...! ) to create deck 4999
Ali's deck 4996-1 becomes view only - needs to go to 4996-2 and loses changes.

Klaas forks 4996-2 (TROLOLOLO) to create deck 5000
Ali's deck 4996-2 becomes view only - needs to go to 4996-3 and loses changes.

Et cetera.

This is confusing for users, but we think not critical.
A possible improvement would be a notification that says WHY the current version of your deck has suddenly become view only (i.e., another user forked your deck and a copy has been saved as a baseline for that user).
And perhaps a mechanism to keep/store your intermediate slide changes, such that they do not get lost...

Good news: If you (user A) do not make any changes after your deck has been forked by user B, then user B can again fork your deck again but you (user A) will not notice (user B will fork from the same baseline).

Not sure though if N other people (user C, D, E) can fork your (user A) unedited deck without you knowing / without you having still the same deck version..

Status

Assignee

Unassigned

Reporter

Klaas Andries de Graaf

Labels

None

Priority

Major
Configure