Versions Compared

Old Version 1

changes.mady.by.user Abi James

Saved on

compared with

New Version Current

changes.mady.by.user Kurt Junghanns

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Related JIRA tasks
Page Properties
DevelopersQA
Work Package & deliverables 
Target release
EpicDocument status
Status
titleDRAFT
Document owner

Abi James

Designer
2.0 RC!
Epic

Jira Legacy
serverJIRA (slidewiki.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

maximumIssues20jqlQuerysummary ~ "transform" OR description ~ "transform"

serverId497b9b88-e2b8-32ee-be05-4d265f33883f
keySWIK-194

Document status
Status
titleDRAFT
Document owner

Darya Tarasowa

Designer
DevelopersDarya Tarasowa
QA

Summary

...

Work Package & deliverables 
Related JIRA tasks

Task - A task that needs to be done.Image Added SWIK-351 Create script for migrating existing content from old slidewiki.org to new SW2.0

 

Task - A task that needs to be done.Image Added SWIK-99 Migrate the content of old slidewiki platform to our new platform/schema 

 

Summary

  • Transfer all the content from SlideWiki 1.0 to the new platform and ensure that authors maintain their rights to own and edit the content
  • See Migration progress to get the overview about progress

Background and goals

Old users of Slidewiki should not suffer from the switch to the new architecture. Also, we have announced that our future pilot runners could create drafts of the content in the old SlideWiki. 

Assumptions

  • First step will be the theoretical schema integration between old relational schema and new MongoDB data models.  - this integration is similar to the RDB2RDF mapping, we can reuse it.


  • For that all data models used by the services have to be retrieved from github or the developers .- the process can be done in the iterative manner, we should be able to change the data scheme relatively easy

  • For semi-testing the old database dump from github could be used.

  • The final MySQL dump have to be surrendered by Ben as he is the only one who can get access to the running instance/database - not exactly true. Ali and Darya have access to the database as root users. 

Requirements

#TitleUser StoryImportanceNotesJIRA
1TransfereTransfer contentAs a user I want to be able to access presentations that were on SlideWiki 1.0

Jira Legacy
serverJIRA (slidewiki.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId497b9b88-e2b8-32ee-be05-4d265f33883f
keySWIK-194

2 Access rightsAs an author I want to be able to access rights to all the presentations that I added to SlideWiki 1.0 Must Have  
3 User credentialsAs a user I want to be able to log-in to SW 2.0 with the same details as SW 1.0  PreferablyMigrated users will get a new password 

User interaction and design

Description of fields/input/elements + validation + test scenarios


Questions

Below is a list of questions to be addressed as a result of this requirements document:

Question

Asked by

Outcome

 

Not Doing

Feature

Status

  

Source material for user/stakeholder feedback

Requirements (/user stories) from pilot roadmap:

 

Evaluation/improvements by Farid Hasanov master thesis :


 

Evaluation at UniBonn :  


Project Partners feedback:

...