[Building Sakai] Roster data via REST?

[Gregory Guthrie]

Ok; uniqueness is important, but could be administratively arranged. 
How about getting site ID from the shortened URL name, those are unique.

Or, more generally - what is a human (administrator) friendly way to describe sites for reporting and queries?
-------------------------------------------
Subject: Re: [Building Sakai] Roster data via REST?

I'm pretty sure there isn't a way (and if there is there shouldn't be), to query sited (something unique) by name (not actually unique) and return only one unique result.

I may be misunderstanding the relationship, but I don't think that entityTitle is a unique ID in the model. You could get back one or many results.
-------------------------------------------
Steve, Thanks (again.), but while I can see how to use /direct/site/..siteID.xml for site information,
How do I get the SiteID to do this?
 
I want to go from what that gives me as  <entityTitle> to the <entityID> which I need to run the site query and others.
Then from that I can get Roster, etc.
 
Just to be clear, so that I can get a roster via: /server/direct/membership/site/dc228507-e011-445c-aafc-6757341b9ffa.xml
I want something where I can start with "CS505-Fall2012" and get the SiteID to make that query.
 
The /direct/site/ seems to do the converse, given a SiteID I can query and get all sorts of stuff, including the Title (which is also used in the short URL).
 -------------------------------------------
Hi Gregory,
Yes there is a provider to get the list of sites (/site). The idea is that you chains some of these requests together, ie get a list of sites, then for each site get a list of X.
cheers,
Steve
 
They require a course ID - given a program dealing with the human-readable course names, is there some REST-full way to get the course ID to make these calls? I.e. to lookup course names?

-------------------------------------------