This scenario illustrates how a curnit is registered Wise. The result is a Wise project for which teachers can make runs.
This differs from what Turadg described at the retreat. The difference is that his approach required a WISE administrator to do the registering.
Text Description
Preconditions:
- Curnit is available as a URL.
- It could be attached to a confluence page.
- It could simply uploaded to a webserver.
Sequence
- User selects "register curnit" in WISE
- WISE displays a form with two text input boxes. One for the curnit URL and one for the new Project name.
- User fills out form.
- WISE calls createCurnit passing the curnitURL on the SDS.
- SDS returns a uuid for this curnit
- WISE creates a new Project and stores the uuid from the SDS in it.
Notes
This could be streamlined from a user's point of view:
If WISE provided a way to store the curnits. Then import curnit form would include a form field for uploading the curnit instead entering in a URL.
It would also be more reusable if the "import curnit" form was supplied by SDS or some other non-wise service. In that way this same form could be reused by portals other than WISE. Additionally this generalized form might allow the user to "import" curnits into wise that had that
Coming soon are senarios describing this streamlining
Comments (2)
Aug 02, 2006
Anthony Perritano says:
"It would also be more reusable if the "import curnit" form was supplied by SDS ..."It would also be more reusable if the "import curnit" form was supplied by SDS or some other non-wise service. In that way this same form could be reused by portals other than WISE. Additionally this generalized form might allow the user to "import" curnits into wise that had that"
this could be generic jsp's or servlets running in the same server as the services?
Aug 03, 2006
Scott Cytacki says:
Yes, I think jsps would work.Yes, I think jsps would work.