Date: Fri, 15 Dec 2006 09:42:33 -0500
From: Laurel Williams <[EMAIL PROTECTED]>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: stephen Bannasch <[EMAIL PROTECTED]>,
Jim Slotta <[EMAIL PROTECTED]>,
Cynick Young <[EMAIL PROTECTED]>
Subject: portal/SDS issues
Hi Stephen,
Cynick and I managed to get the SDS interactions working with the
portal (only very minimal right now) but came across a couple of
issues
that we thought we would like to bring up. We have outlined them on
this wiki page
http://www.telscenter.org/confluence/display/SAIL/Portal+interaction+with+SDS+-+Issues
Looking forward to chatting about this in the next meeting.
comments also on wiki page:
1) Toronto Simplified Portal is VERY simplified and has few
requirements for a user to join.
Toronto Portal user: requires specification of a desired username and
password. Not sure what will be actually required in the future (this
will be up to the group to decide).
SDS user creation: requires submission of first and last name (not
sure if any checking is done such as validation for character data,
not blank, etc.
* the only data required are firstname and lastname,
I'll have to check what chars are allowed
To access the SDS the portal user must create an SDS user, but
equivalent data is not available. As stop gap we have chosen to use
username from Portal as SDS first and last name.
* that should work but I recommend adding first and
last name to your simple portal.
2) At this time there is no concept in the portal of a "work group".
Users log in as an individual
SDS provides offerings only when associated with a work group (not an
individual).
To access an offering from the SDS, probably need to create a work
group of size 1 for each portal user to run an offering and have data
saved.
* Yes, you'll need to create a workgroup. The scope of
a workgroup is an offering so if you create two users of Laurel and
Cynick you'll need to create a new workgroup consisting of these two
users for every offering you want them to be able to run.
* Perhaps an attribute of an offering could allow
dynamic creation of associated workgroup when it is run with a new
user (normally users are 'subscribed' to an offering by making
associated workgroups.
3) What would cause a 404 Bad Request for any of the REST commands
outlined in your specs?
* any malformed url (mispelled or missing elements in path)
4) How do we know what are required fields, what are optional fields,
any restrictions on valid inputs (legal characters, encoding, etc.)
for the fields for the REST commands outlined in your specs.
* All fields in documentation are required. Use alpha,
numeric, and 'friendly' chars like '_' and '-'. I'll figure out
something a bit more precise.
--
- Stephen Bannasch
Concord Consortium, http://www.concord.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SAIL-Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/SAIL-Dev?hl=en
-~----------~----~----~----~------~----~------~--~---
