Hi All,

After another night of pretty solid virtuoso-integrating, here are my
finding for tonight; those which are blocking usage in some way I've
marked as "blocker"(s). Primarily I've been working through conductor
stored procedure editing & all the ODS.ODS_API.user.* functionality.


#1 blocker
Conductor -> SQL Database Objects -> Procedure [EDIT]
when you save a procedure it removes all associated permissions for that
procedure. (first hit editing ODS.ODS_API.user.invite)

note: may be related to next bug..


#2: blocker
Conductor -> SQL Database Objects -> Procedure [PERMISSIONS]
When you edit permissions and hit save you get the following error:
error when processing "/conductor/databases_grants.vspx" page.
SQL State       37000
SQL Message     SQ074: Line 1: syntax error at 'user' before '.'

meaning you can't update permissions when they are removed by bug #1
again hit this bug when editing ODS.ODS_API.user.* procedures


#3
ODS.ODS_API.user.invite always returns 'The e-mail address(es) is not
valid and mail cannot be sent.' for all emails; valid or not.


#4 blocker
need documentation for input on ODS.ODS_API.user.update( user_info any )
checked the procedure but my virtuoso/pl isn't up to par yet and don't
know what's avail + noticed a --FIX ME in there


#5 blocker
can't view / use / see blog for new users:
see: http://webr3.org:8890/weblog/nathan/
tried deleting, remaking etc etc nothing works


#6
ods -> edit profile -> security tab (broken)
differing unexpected errors depending on logged in user


#7 blocker
ODS.ODS_API.user.relation_update
method is stubbed/unimplemented


#8 blocker
missing/needed method(s) for password recovery
ODS.ODS_API.user.passwordReset( name ) // generate and return password
+ modification to
ODS.ODS_API.user.password_change( new_password , name=null )
to allow admin change of a users password; extra param name shouldn't
break bc


#9
the following areas are all missing .list methods
ODS.ODS_API.user.thingOfInterest
ODS.ODS_API.user.topicOfInterest
ODS.ODS_API.user.bioevent <-blocker
ODS.ODS_API.user.annotation

notes:
thingOfInterest and topicOfInterest can be found by calling
user.getFOAFData, however bioevents are not listed here; nor are any of
these items included with the return of user.get
ODS.ODS_API.user.bioevent.list would ideally include bioID for use in
bioevent.delete


#10
much of the user profile functionality in ODS web interface is missing
from the api, of these the first three would be priority imho
- Personal -> Online Accounts
- Personal -> Messaging Service(s)
- Personal -> Address
- Personal -> Main
- Business -> *
-

#11 trivial
ODS web interface, how do you invite somebody..?


#12 minor
could do with a method to get a users uri by name
ODS.ODS_API.user.getURI( name )


Many Regards,

Nathan

Reply via email to