WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View
all threads
ST
sandrayun.tsai@gmail.com
Thu, Jul 19, 2012 7:08 PM
Hi CollectionSpacers, We referred to the instructions at
http://wiki.collectionspace.org/display/collectionspace/Person+Service+REST+APIs
in the section titled "PersonAuthority REST payload schemas" to import Person
records (vocabulary records). We found that our records could be saved in our
server, but it didn't display the person's name. When we checked the XML file
in the browser window, there is no element "" as well. Did we do something
wrong or miss some steps? P.S. We use CocoaRestClient app to import the
record. Thanks, Sandra
Hi CollectionSpacers, We referred to the instructions at
http://wiki.collectionspace.org/display/collectionspace/Person+Service+REST+APIs
in the section titled "PersonAuthority REST payload schemas" to import Person
records (vocabulary records). We found that our records could be saved in our
server, but it didn't display the person's name. When we checked the XML file
in the browser window, there is no element "" as well. Did we do something
wrong or miss some steps? P.S. We use CocoaRestClient app to import the
record. Thanks, Sandra
AR
Aron Roberts
Thu, Jul 19, 2012 7:45 PM
Sandra,
Two things come to mind:
- The general concept is that:
a) You create a Person Authority record - essentially, a vocabulary
into which you can import terms. This record doesn't have any
individual person's name.
b) Then, you can create Person records - essentially individual terms
within the vocabulary you just created. Each of those records will
contain a person's name.
The part of the REST API document you mentioned, "PersonAuthority
REST payload schemas", pertains to step a) above. There's also a part
later down that page, "Person REST payload schemas", that pertains to
step b).
- Are you still using CollectionSpace version 2.0? Starting in
version 2.4, the REST payload for Person records changed - so you can
now have multiple terms (and hence multiple names for the same person,
like "Samuel Clemens" and "Mark Twain"), but the documentation doesn't
seem to have been updated to reflect this.
If you're using 2.4 or later, please write back and we can point you
to the newer schema. (And yes, we BADLY need to update these docs,
and I'll make sure there's an issue for us to do so.)
Thanks!
Aron
On Thu, Jul 19, 2012 at 12:08 PM, sandrayun.tsai@gmail.com wrote:
Sandra,
Two things come to mind:
1) The general concept is that:
a) You create a Person Authority record - essentially, a vocabulary
into which you can import terms. This record doesn't have any
individual person's name.
b) Then, you can create Person records - essentially individual terms
within the vocabulary you just created. Each of those records *will*
contain a person's name.
The part of the REST API document you mentioned, "PersonAuthority
REST payload schemas", pertains to step a) above. There's also a part
later down that page, "Person REST payload schemas", that pertains to
step b).
2) Are you still using CollectionSpace version 2.0? Starting in
version 2.4, the REST payload for Person records changed - so you can
now have multiple terms (and hence multiple names for the same person,
like "Samuel Clemens" and "Mark Twain"), but the documentation doesn't
seem to have been updated to reflect this.
If you're using 2.4 or later, please write back and we can point you
to the newer schema. (And yes, we BADLY need to update these docs,
and I'll make sure there's an issue for us to do so.)
Thanks!
Aron
On Thu, Jul 19, 2012 at 12:08 PM, <sandrayun.tsai@gmail.com> wrote:
> Hi CollectionSpacers, We referred to the instructions at
> http://wiki.collectionspace.org/display/collectionspace/Person+Service+REST+APIs
> in the section titled "PersonAuthority REST payload schemas" to import
> Person
> records (vocabulary records). We found that our records could be saved in
> our
> server, but it didn't display the person's name. When we checked the XML
> file
> in the browser window, there is no element "" as well. Did we do something
> wrong or miss some steps? P.S. We use CocoaRestClient app to import the
> record. Thanks, Sandra
>
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
CH
Chris Hoffman
Thu, Jul 19, 2012 7:54 PM
Hi Sandra,
You can also use a REST call to see what's returned by the services layer by doing something like:
http://yourserver.com:8180/cspace-services/personauthorities/persons/items/{your-csid-here}
Or since you're on 2.0, you can do this sql:
select * from persons_common
to see what's in the database
Does any other data for the person record you loaded display?
Feel free to send us the XML file you tried to load -- we can take a look and get back to you.
Thanks,
Chris
On Jul 19, 2012, at 12:45 PM, Aron Roberts wrote:
Sandra,
Two things come to mind:
- The general concept is that:
a) You create a Person Authority record - essentially, a vocabulary
into which you can import terms. This record doesn't have any
individual person's name.
b) Then, you can create Person records - essentially individual terms
within the vocabulary you just created. Each of those records will
contain a person's name.
The part of the REST API document you mentioned, "PersonAuthority
REST payload schemas", pertains to step a) above. There's also a part
later down that page, "Person REST payload schemas", that pertains to
step b).
- Are you still using CollectionSpace version 2.0? Starting in
version 2.4, the REST payload for Person records changed - so you can
now have multiple terms (and hence multiple names for the same person,
like "Samuel Clemens" and "Mark Twain"), but the documentation doesn't
seem to have been updated to reflect this.
If you're using 2.4 or later, please write back and we can point you
to the newer schema. (And yes, we BADLY need to update these docs,
and I'll make sure there's an issue for us to do so.)
Thanks!
Aron
On Thu, Jul 19, 2012 at 12:08 PM, sandrayun.tsai@gmail.com wrote:
Hi Sandra,
You can also use a REST call to see what's returned by the services layer by doing something like:
http://yourserver.com:8180/cspace-services/personauthorities/persons/items/{your-csid-here}
Or since you're on 2.0, you can do this sql:
select * from persons_common
to see what's in the database
Does any other data for the person record you loaded display?
Feel free to send us the XML file you tried to load -- we can take a look and get back to you.
Thanks,
Chris
On Jul 19, 2012, at 12:45 PM, Aron Roberts wrote:
> Sandra,
>
> Two things come to mind:
>
> 1) The general concept is that:
>
> a) You create a Person Authority record - essentially, a vocabulary
> into which you can import terms. This record doesn't have any
> individual person's name.
>
> b) Then, you can create Person records - essentially individual terms
> within the vocabulary you just created. Each of those records *will*
> contain a person's name.
>
> The part of the REST API document you mentioned, "PersonAuthority
> REST payload schemas", pertains to step a) above. There's also a part
> later down that page, "Person REST payload schemas", that pertains to
> step b).
>
> 2) Are you still using CollectionSpace version 2.0? Starting in
> version 2.4, the REST payload for Person records changed - so you can
> now have multiple terms (and hence multiple names for the same person,
> like "Samuel Clemens" and "Mark Twain"), but the documentation doesn't
> seem to have been updated to reflect this.
>
> If you're using 2.4 or later, please write back and we can point you
> to the newer schema. (And yes, we BADLY need to update these docs,
> and I'll make sure there's an issue for us to do so.)
>
> Thanks!
> Aron
>
> On Thu, Jul 19, 2012 at 12:08 PM, <sandrayun.tsai@gmail.com> wrote:
>> Hi CollectionSpacers, We referred to the instructions at
>> http://wiki.collectionspace.org/display/collectionspace/Person+Service+REST+APIs
>> in the section titled "PersonAuthority REST payload schemas" to import
>> Person
>> records (vocabulary records). We found that our records could be saved in
>> our
>> server, but it didn't display the person's name. When we checked the XML
>> file
>> in the browser window, there is no element "" as well. Did we do something
>> wrong or miss some steps? P.S. We use CocoaRestClient app to import the
>> record. Thanks, Sandra
>>
>>
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
AR
Aron Roberts
Thu, Jul 19, 2012 8:02 PM
Hi Sandra,
You can also use a REST call to see what's returned by the services layer by doing something like:
http://yourserver.com:8180/cspace-services/personauthorities/persons/items/{your-csid-here}
Or since you're on 2.0, you can do this sql:
select * from persons_common
to see what's in the database
Does any other data for the person record you loaded display?
Feel free to send us the XML file you tried to load -- we can take a look and get back to you.
Thanks,
Chris
On Jul 19, 2012, at 12:45 PM, Aron Roberts wrote:
Sandra,
Two things come to mind:
- The general concept is that:
a) You create a Person Authority record - essentially, a vocabulary
into which you can import terms. This record doesn't have any
individual person's name.
b) Then, you can create Person records - essentially individual terms
within the vocabulary you just created. Each of those records will
contain a person's name.
The part of the REST API document you mentioned, "PersonAuthority
REST payload schemas", pertains to step a) above. There's also a part
later down that page, "Person REST payload schemas", that pertains to
step b).
- Are you still using CollectionSpace version 2.0? Starting in
version 2.4, the REST payload for Person records changed - so you can
now have multiple terms (and hence multiple names for the same person,
like "Samuel Clemens" and "Mark Twain"), but the documentation doesn't
seem to have been updated to reflect this.
If you're using 2.4 or later, please write back and we can point you
to the newer schema. (And yes, we BADLY need to update these docs,
and I'll make sure there's an issue for us to do so.)
Thanks!
Aron
On Thu, Jul 19, 2012 at 12:08 PM, sandrayun.tsai@gmail.com wrote:
Thanks, Chris!
Sandra, - or, for the default person authority, you might try:
http://yourserver.com:8180/cspace-services/personauthorities/urn:cspace:name(persons)/items/{your-csid-here}
or for a person authority that you created yourself:
http://yourserver.com:8180/cspace-services/personauthorities/{your-person-authority-csid-here}/items/{your-person-csid-here}
On Thu, Jul 19, 2012 at 12:54 PM, Chris Hoffman
<chris.hoffman@berkeley.edu> wrote:
> Hi Sandra,
> You can also use a REST call to see what's returned by the services layer by doing something like:
> http://yourserver.com:8180/cspace-services/personauthorities/persons/items/{your-csid-here}
>
> Or since you're on 2.0, you can do this sql:
> select * from persons_common
> to see what's in the database
>
> Does any other data for the person record you loaded display?
>
> Feel free to send us the XML file you tried to load -- we can take a look and get back to you.
>
> Thanks,
> Chris
>
> On Jul 19, 2012, at 12:45 PM, Aron Roberts wrote:
>
>> Sandra,
>>
>> Two things come to mind:
>>
>> 1) The general concept is that:
>>
>> a) You create a Person Authority record - essentially, a vocabulary
>> into which you can import terms. This record doesn't have any
>> individual person's name.
>>
>> b) Then, you can create Person records - essentially individual terms
>> within the vocabulary you just created. Each of those records *will*
>> contain a person's name.
>>
>> The part of the REST API document you mentioned, "PersonAuthority
>> REST payload schemas", pertains to step a) above. There's also a part
>> later down that page, "Person REST payload schemas", that pertains to
>> step b).
>>
>> 2) Are you still using CollectionSpace version 2.0? Starting in
>> version 2.4, the REST payload for Person records changed - so you can
>> now have multiple terms (and hence multiple names for the same person,
>> like "Samuel Clemens" and "Mark Twain"), but the documentation doesn't
>> seem to have been updated to reflect this.
>>
>> If you're using 2.4 or later, please write back and we can point you
>> to the newer schema. (And yes, we BADLY need to update these docs,
>> and I'll make sure there's an issue for us to do so.)
>>
>> Thanks!
>> Aron
>>
>> On Thu, Jul 19, 2012 at 12:08 PM, <sandrayun.tsai@gmail.com> wrote:
>>> Hi CollectionSpacers, We referred to the instructions at
>>> http://wiki.collectionspace.org/display/collectionspace/Person+Service+REST+APIs
>>> in the section titled "PersonAuthority REST payload schemas" to import
>>> Person
>>> records (vocabulary records). We found that our records could be saved in
>>> our
>>> server, but it didn't display the person's name. When we checked the XML
>>> file
>>> in the browser window, there is no element "" as well. Did we do something
>>> wrong or miss some steps? P.S. We use CocoaRestClient app to import the
>>> record. Thanks, Sandra
>>>
>>>
>>> _______________________________________________
>>> Talk mailing list
>>> Talk@lists.collectionspace.org
>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org