Settings and activity
1 result found
-
11 votes
a central metadata repository is a big project that folks in uwit have been talking about. we’ll look for some smaller bits that we could do within the web services to provide some value in the meantime
An error occurred while saving the comment An error occurred while saving the comment 
Sean Eamon Kennedy
commented
I'm on the analyst side of things and don't know anything about the coding details. What I was hoping for is an easy way to explain to our development team how they could implement a look up function in any app. For instance, if they develop a form that requires the end user to enter a budget number, I could ask them to add a look up function where the end user enters part of the budget name and it returns the budget number (or list of options if there is more than one hit). I could say "just copy the code used in this other app that looks up a person's netid based on part of their name. There's probably a resource that uses the same protocol for a budget number look up and you can probably guess the parameters that need to be changed because it's a standard protocol."
Besides, it has a good acronym: SLURP
Sean Eamon Kennedy
shared this idea
·
There are a few look up requests in this list already: lookup netid from name, look up person info from netid, and look up person (student) info from SDB systemkey (or is it the other way around?)
Using a standard protocol you could plug in code that says:
1) this is a SLURP
2) I need data about this object (person, budgets, course, etc)
3) here's what I have, and here's its value (e.g. string containing part of name)
4) here's what I need (e.g. uw netid for name part)