 |
 |
It would be useful if it allowed only create candidate terms via web services? best regards diego ferreyra 2011/3/1 Bobbi Fox <[log in to unmask]>: > I have been tasked with coming up with a RESTful Create, Read, Update [we're > not Deleting] API to our home-grown controlled vocabulary database, "WordShack". > > WordShack was developed as part of our Email Archiving Pilot, where we > control not only for subject, but for person, organization, email address, etc. > > I've investigated Tematres1.2 (nice interface, btw), and also looked into > the lately-announced HIVE RESTful Web Services API, but both these seem to > be Read-only. > > Is anyone working on the C & U part of CRUD? > > An additional complication is that the controlled vocabulary systems I've > seen so far flatten (and store) the "term" into a single string, whereas our > DB, heavily MODS influenced, breaks up terms into fields: say, a "person" > term is broken into a (name,term of address, date) tuple. While I'd > consider putting a skim coat on the DB with a structured text string > gazinta/goesoutta of some sort, I can imagine screams of anguish from the > original designers (some of whom are also on this code4lib ml :-) > > I'd like to hear from anyone who is working on this, or who would like to be > working on it with me. > > Thanks, > Bobbi Fox, Office for Information Systems > Harvard Library, > Harvard University > Cambridge, MA >