It would be useful if it allowed only create candidate terms via web services?
best regards
diego ferreyra
2011/3/1 Bobbi Fox :
> 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".
>
>
eate an interface to your WordShack database.
Ralph
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Bobbi Fox
> Sent: Tuesday, March 01, 2011 1:07 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: [CODE4LIB] Controlled Vocabulary
On Tue, Mar 1, 2011 at 4:31 PM, William Denton wrote:
> On 1 March 2011, Bobbi Fox wrote:
>
>> 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".
>
> I can't help you with your actual q
On Tue, Mar 1, 2011 at 5:07 PM, Luciano Ramalho wrote:
> On Tue, Mar 1, 2011 at 4:31 PM, William Denton wrote:
>> On 1 March 2011, Bobbi Fox wrote:
>>
>>> I have been tasked with coming up with a RESTful Create, Read, Update
>>> [we're not Deleting] API to our home-grown controlled vocabulary dat
On 1 March 2011, Bobbi Fox wrote:
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".
I can't help you with your actual question---except to wish you good
luck---but have you read RESTfu
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 add
