You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

Progress status for fall 2015

Geir to provide template soon.

Possible way to use jira-epics to commonly follow progress:

Based on the system architecture (see System Architecture). Each country can of course have other epics as well and are free to drill into these in their own way. But a common high level epic-structure allows for common reporting. This structure is also focused on achieving the end goal of being ready for the field trial. A similar structure can be done for the SMP.

NCP-epics:

  • SMP API
  • Authentication/NCP
  • Study Course Search and Selection
  • Logging
  • Db Search API
  • UAT
  • NCP ready for field trial

SMP-epics

  • NCP API
  • Authentication/SMP
  • EMREG/NCP Selection
  • Student Matching
  • API to HEI
  • Logging (could same epic as for NCP?)
  • UAT (could same epic as for NCP?)
  • SMP ready for field trial

It is possible, at least in Finland, to link from the jira-epics to wiki. Thus there is no need to update wiki, it will automatically be updated with the latest jira-status of the tickets shown. As an example (you might have to be logged in to see the actual description and status?):

Finland- NCP develoment:

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Collaboration tools for developers

The project uses flowdock as a chat-tool. Please keep it open and check if there are any quick questions that you can answer.

https://www.flowdock.com/app/tiptop/emrex

Anybody can invite others, so you can invite your colleagues. Or send an email to Mats and he'll add you

 

Other stuff

WP3 tasks are mainly technical ones. Based on the requirements from work package 2, implement technical solution for National Contact Points and the Student Mobility Plug-in. The work package will be executed through regular project meeting and workshops, both face to face and remote meetings. There will be organized workshops for development and deployment for these solutions.

Activity: Open Source mechanisms

The code developed in the project will be open source. The mechanisms to share this code will be clarified in this WP

Activity: Development of National Contact Points

A National Contact Point has to be developed for each country. In this work package, a foundation for such a contact point will be developed. Based on this foundation each partner in the project signed up for implementing the solution will develop their own.

Activity: Development of Student Mobility Plug-ins

The Student Mobility Plug-in is a common service for collecting data from other higher institutions, via a National Contact Point. The student will be in control of the data exchange.

Activity: Deployment of the National Contact Point and the Student Mobility Plug-in

Each partner signed up for implementing the solution must deploy the National Contact Point and the Student Mobility Plug-in in one or more web applications for applicants and/or students.

Activity: Security

The information exchanged in this solution is personal. It is necessary to implement solutions to secure the integrity and confidentiality in the data exchange.

Activity: Technical documentation

Make technical documentation for the National Contact Point and the Student Mobility Plug-in, including examples of use.

Meetings

Aprox 1. May 2015: Open Source Platform, Detail planning for development and deployment

How often do we need telcom status meetings?

October 2015: Meeting/workshop: Test of NCP

 

 

Overall plan (still planning)

May 2015: Start up meeting

August 2015: First version of SMP

October 2015: Pilot version of SMP, incl technical doc

November 2015: Two NCP ready for testing, incl technical doc

December 2015: Two NCP ready for pilot

December 2015: Five deployments of SMP ready for pilot

April 2016: All five NCP ready for pilot

Rest of 2016: Support, bugfixing, improvements

December 2016: Final report

ELMO

ELMO is uses as exchange format in EMREX. More information at the pages for WP6 Standardisation

A viewer has been developed to show the contenct of an ELMO document in a more human way. This code can as well be used as a starting point for the ELMO viewer in NCP's and Emrex-clients.

The viewer can at the moment be testes at this site: http://matija.no/elmo/

Nordic glossary (link to Google docs)

https://drive.google.com/open?id=1cgGaihsj0S4l_F75Xu9qBQBmDlxHC5pva8Q3KUvRMDg&authuser=0

Wireframes

Wireframes, including a flow diagram for Emrex can be found here:

https://moqups.com/lundin.goran@gmail.com/2sWGyfXn/p:a2fa73ae2

Plans for each participating country

Denmark

Contact person: Anders Bøgebjerg Hansen

Participants: 

Development of National Contact Point: xxxxxx
Deployment of Student Mobility Plug-in: xxxxxxx

Finland

Contact person: Mats Lindstedt

Participants: Ulf Nyström + developers from vendor (not selected yet)

Development of National Contact Point: November 2015 (not confirmed)
Deployment of Student Mobility Plug-in: November 2015 (stand-alone solution, not confirmed)

Italy

Contact person: Stefano Russo <strusso@kion.it>

Participants: Stefano Russo <strusso@kion.it>, Claudio Caso <ccaso@kion.it>

Development of National Contact Point: November 2015
Deployment of Student Mobility Plug-in: November 2015 (Kion Esse3 SIS Plug-in)

Norway

Contact person: Geir Vangen <g.m.vangen@fsat.no>

Participants: Richard Edvin Borge <r.e.borge@fsat.no>, Matija Puzar (matija.puzar@fsat.no), Alen Milkovic <alen.milkovic@fsat.no>

Development of National Contact Point: November 2015
Deployment of Student Mobility Plug-in: November 2015

Sweden

Contact person: Mattias Holmlund <mattias.holmlund@umu.se

Participants: Mikael Berglund <mikael.berglund@umu.se>, Sven Hedqvist <sven.hedqvist@umu.se>

Development of National Contact Point: xxxxxx
Deployment of Student Mobility Plug-in: xxxxxxx
  • No labels