Hi, 
Guest
Pic
Sign In

talk@lists.collectionspace.org

WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org

View all threads

Schema Extension and Search in CSpace v1.0

AS
Angela Spinazze
Tue, Jun 15, 2010 5:40 PM

Hi all,

During my recent visit to SMK, we talked about the fact that they will
be extending CSpace schemas to accommodate some SMK-specific fields
(such as notes).  Chris asked about how those fields will be
accommodated by basic search and advanced search.

In other words, How will fields added as SMK extensions to schemas be
made available for search?  Will these fields be searchable?  If so,
how?  If not, why not?  If not now, when?

Can our developers chime in with some details?

Thanks,

Angela

Hi all, During my recent visit to SMK, we talked about the fact that they will be extending CSpace schemas to accommodate some SMK-specific fields (such as notes). Chris asked about how those fields will be accommodated by basic search and advanced search. In other words, How will fields added as SMK extensions to schemas be made available for search? Will these fields be searchable? If so, how? If not, why not? If not now, when? Can our developers chime in with some details? Thanks, Angela
AR
Aron Roberts
Tue, Jun 15, 2010 6:54 PM

Hi Angela,

In the message "[Talk] Schema Extension and Search in CSpace v1.0",
dated 2010-06-15, Angela Spinazze wrote:

During my recent visit to SMK, we talked about the fact that they
will be extending CSpace schemas to accommodate some SMK-specific
fields (such as notes).  Chris asked about how those fields will be
accommodated by basic search and advanced search.

In other words, How will fields added as SMK extensions to schemas
be made available for search?  Will these fields be searchable?

Yes.

If so, how?

A quick test verified that, in the University & Jepson Herbaria
(UCJEPS) instance of CollectionSpace - which is running release 0.6 -
at least for keyword / full text searching, fields added via
extension schema are searchable (below).

Others may wish to comment on whether these fields can or will also
be made searchable via other means, such as via 'Advanced Search.'

Aron

P.S. This UCJEPS instance was used as an example, because it has an
extensive set of custom fields in an extension schema.

--

  1. Retrieve this record via the UI:

http://ucjeps.collectionspace.org:8180/cspace-ui/html/objects.html?csid=f7137ff0-81ee-4d0c-a802

  1. Note the value of the "Field Location Verbatum" field - that it
    contains the word "Rockefeller":

"On the east side of Rockefeller Road, at the intersection of Bald
Rock Road and Rockefeller Road, about 13 miles (air) northeast of
Oroville"

  1. Retrieve this record via the CollectionObject service:

curl -u test@collectionspace.org:testtest
http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects/f7137ff0-81ee-4d0c-a802

Note that in the record returned in the response, the corresponding
field (to "Field Location Verbatum"), fieldLocPlace, is within a
'collectionobjects_naturalhistory' extension schema:

--2ed55496-92f0-464a-822f-b4b20e8782ec
label: collectionobjects_naturalhistory
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>

<ns2:collectionobjects_naturalhistory
xmlns:ns2="http://collectionspace.org/services/collectionobject/domain/naturalhistory"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://collectionspace.org/services/collectionobject/domain/naturalhistory
http://collectionspace.org/services/collectionobject/domain/collectionobjects_naturalhistory.xsd">
<fieldLocLongDecimal>-121.37944793701172</fieldLocLongDecimal>
<fieldLocLatDecimal>39.664169311523438</fieldLocLatDecimal>
...
<fieldLocPlace>On the east side of Rockefeller Road, at the
intersection of Bald Rock Road and Rockefeller Road, about 13 miles
(air) northeast of Oroville</fieldLocPlace>
<fieldCollectionDateLatest>Jun 12, 2007</fieldCollectionDateLatest>
<fieldLocElevation>3320 ft</fieldLocElevation>
...
</ns2:collectionobjects_naturalhistory>

--2ed55496-92f0-464a-822f-b4b20e8782ec
label: collectionobjects_common
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>

<ns2:collectionobjects_common
xmlns:ns2="http://collectionspace.org/services/collectionobject"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://collectionspace.org/services/collectionobject
http://services.collectionspace.org/collectionobject/collectionobjects_common.xsd">
<otherNumberType>collector number</otherNumberType>
<otherNumber>14081</otherNumber>
<responsibleDepartments/>
<objectNumber>JEPS113857</objectNumber>

<title>Juncus tenuis Willd.</title> ... </ns2:collectionobjects_common>

--2ed55496-92f0-464a-822f-b4b20e8782ec--

  1. Perform a search on the keyword "Rockefeller" in the
    CollectionObject service:

curl -u test@collectionspace.org:testtest
http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects?kw=rockefeller

Note that the record returned has the same object number, JEPS113857,
and the same CollectionSpace ID (CSID), f7137ff0-81ee-4d0c-a802, as
the record above:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:collectionobjects-common-list

xmlns:ns2="http://collectionspace.org/services/collectionobject"
xmlns:ns3="http://collectionspace.org/services/jaxb"><pageNum>0</pageNum><pageSize>40</pageSize><itemsInPage>1</itemsInPage><totalItems>1</totalItems><collection-object-list-item><objectNumber>JEPS113857</objectNumber><title>Juncus
tenuis
Willd.</title><uri>/collectionobjects/f7137ff0-81ee-4d0c-a802</uri><csid>f7137ff0-81ee-4d0c-a802</csid></collection-object-list-item></ns2:collectionobjects-common-list>

  1. Perform a search on the keyword "Rockefeller" in the UI:

Enter "Rockefeller" into the "Search" box at top left.  Keep the
original drop-down menu selection to its left at "Object".  Click
"Search".

One record is returned, matching the record above:

ID Number Summary                Type
JEPS113857 Juncus tenuis Willd. objects

Hi Angela, In the message "[Talk] Schema Extension and Search in CSpace v1.0", dated 2010-06-15, Angela Spinazze wrote: >During my recent visit to SMK, we talked about the fact that they >will be extending CSpace schemas to accommodate some SMK-specific >fields (such as notes). Chris asked about how those fields will be >accommodated by basic search and advanced search. > >In other words, How will fields added as SMK extensions to schemas >be made available for search? Will these fields be searchable? Yes. > If so, how? A quick test verified that, in the University & Jepson Herbaria (UCJEPS) instance of CollectionSpace - which is running release 0.6 - at least for keyword / full text searching, fields added via extension schema are searchable (below). Others may wish to comment on whether these fields can or will also be made searchable via other means, such as via 'Advanced Search.' Aron P.S. This UCJEPS instance was used as an example, because it has an extensive set of custom fields in an extension schema. -- 1. Retrieve this record via the UI: http://ucjeps.collectionspace.org:8180/cspace-ui/html/objects.html?csid=f7137ff0-81ee-4d0c-a802 2. Note the value of the "Field Location Verbatum" field - that it contains the word "Rockefeller": "On the east side of Rockefeller Road, at the intersection of Bald Rock Road and Rockefeller Road, about 13 miles (air) northeast of Oroville" 3. Retrieve this record via the CollectionObject service: curl -u test@collectionspace.org:testtest http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects/f7137ff0-81ee-4d0c-a802 Note that in the record returned in the response, the corresponding field (to "Field Location Verbatum"), fieldLocPlace, is within a 'collectionobjects_naturalhistory' extension schema: --2ed55496-92f0-464a-822f-b4b20e8782ec label: collectionobjects_naturalhistory Content-Type: application/xml <?xml version="1.0" encoding="UTF-8"?> <ns2:collectionobjects_naturalhistory xmlns:ns2="http://collectionspace.org/services/collectionobject/domain/naturalhistory" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://collectionspace.org/services/collectionobject/domain/naturalhistory http://collectionspace.org/services/collectionobject/domain/collectionobjects_naturalhistory.xsd"> <fieldLocLongDecimal>-121.37944793701172</fieldLocLongDecimal> <fieldLocLatDecimal>39.664169311523438</fieldLocLatDecimal> ... <fieldLocPlace>On the east side of Rockefeller Road, at the intersection of Bald Rock Road and Rockefeller Road, about 13 miles (air) northeast of Oroville</fieldLocPlace> <fieldCollectionDateLatest>Jun 12, 2007</fieldCollectionDateLatest> <fieldLocElevation>3320 ft</fieldLocElevation> ... </ns2:collectionobjects_naturalhistory> --2ed55496-92f0-464a-822f-b4b20e8782ec label: collectionobjects_common Content-Type: application/xml <?xml version="1.0" encoding="UTF-8"?> <ns2:collectionobjects_common xmlns:ns2="http://collectionspace.org/services/collectionobject" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://collectionspace.org/services/collectionobject http://services.collectionspace.org/collectionobject/collectionobjects_common.xsd"> <otherNumberType>collector number</otherNumberType> <otherNumber>14081</otherNumber> <responsibleDepartments/> <objectNumber>JEPS113857</objectNumber> <title>Juncus tenuis Willd.</title> ... </ns2:collectionobjects_common> --2ed55496-92f0-464a-822f-b4b20e8782ec-- 4. Perform a search on the keyword "Rockefeller" in the CollectionObject service: curl -u test@collectionspace.org:testtest http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects?kw=rockefeller Note that the record returned has the same object number, JEPS113857, and the same CollectionSpace ID (CSID), f7137ff0-81ee-4d0c-a802, as the record above: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:collectionobjects-common-list xmlns:ns2="http://collectionspace.org/services/collectionobject" xmlns:ns3="http://collectionspace.org/services/jaxb"><pageNum>0</pageNum><pageSize>40</pageSize><itemsInPage>1</itemsInPage><totalItems>1</totalItems><collection-object-list-item><objectNumber>JEPS113857</objectNumber><title>Juncus tenuis Willd.</title><uri>/collectionobjects/f7137ff0-81ee-4d0c-a802</uri><csid>f7137ff0-81ee-4d0c-a802</csid></collection-object-list-item></ns2:collectionobjects-common-list> 5. Perform a search on the keyword "Rockefeller" in the UI: Enter "Rockefeller" into the "Search" box at top left. Keep the original drop-down menu selection to its left at "Object". Click "Search". One record is returned, matching the record above: ID Number Summary Type JEPS113857 Juncus tenuis Willd. objects
AS
Angela Spinazze
Wed, Jun 16, 2010 2:00 PM

Hi Aron,

Thanks so much for your quick reply to this post.  I just spoke with
Chris P. and you'll see a follow up from him directly as well.

Angela

On 15 Jun, 2010, at 13:54, Aron Roberts wrote:

Hi Angela,

In the message "[Talk] Schema Extension and Search in CSpace v1.0",
dated 2010-06-15, Angela Spinazze wrote:

During my recent visit to SMK, we talked about the fact that they
will be extending CSpace schemas to accommodate some SMK-specific
fields (such as notes).  Chris asked about how those fields will be
accommodated by basic search and advanced search.

In other words, How will fields added as SMK extensions to schemas
be made available for search?  Will these fields be searchable?

Yes.

If so, how?

A quick test verified that, in the University & Jepson Herbaria
(UCJEPS) instance of CollectionSpace - which is running release 0.6

  • at least for keyword / full text searching, fields added via
    extension schema are searchable (below).

Others may wish to comment on whether these fields can or will also
be made searchable via other means, such as via 'Advanced Search.'

Aron

P.S. This UCJEPS instance was used as an example, because it has an
extensive set of custom fields in an extension schema.

--

  1. Retrieve this record via the UI:

http://ucjeps.collectionspace.org:8180/cspace-ui/html/objects.html?csid=f7137ff0-81ee-4d0c-a802

  1. Note the value of the "Field Location Verbatum" field - that it
    contains the word "Rockefeller":

"On the east side of Rockefeller Road, at the intersection of Bald
Rock Road and Rockefeller Road, about 13 miles (air) northeast of
Oroville"

  1. Retrieve this record via the CollectionObject service:

curl -u test@collectionspace.org:testtest http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects/f7137ff0-81ee-4d0c-a802

Note that in the record returned in the response, the corresponding
field (to "Field Location Verbatum"), fieldLocPlace, is within a
'collectionobjects_naturalhistory' extension schema:

--2ed55496-92f0-464a-822f-b4b20e8782ec
label: collectionobjects_naturalhistory
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>

<ns2:collectionobjects_naturalhistory xmlns:ns2="http://collectionspace.org/services/collectionobject/domain/naturalhistory
" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://collectionspace.org/services/collectionobject/domain/naturalhistory
http://collectionspace.org/services/collectionobject/domain/collectionobjects_naturalhistory.xsd
">
<fieldLocLongDecimal>-121.37944793701172</fieldLocLongDecimal>
<fieldLocLatDecimal>39.664169311523438</fieldLocLatDecimal>
...
<fieldLocPlace>On the east side of Rockefeller Road, at the
intersection of Bald Rock Road and Rockefeller Road, about 13 miles
(air) northeast of Oroville</fieldLocPlace>
<fieldCollectionDateLatest>Jun 12, 2007</fieldCollectionDateLatest>
<fieldLocElevation>3320 ft</fieldLocElevation>
...
</ns2:collectionobjects_naturalhistory>

--2ed55496-92f0-464a-822f-b4b20e8782ec
label: collectionobjects_common
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>

<ns2:collectionobjects_common xmlns:ns2="http://collectionspace.org/services/collectionobject
" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://collectionspace.org/services/collectionobject
http://services.collectionspace.org/collectionobject/collectionobjects_common.xsd
">
<otherNumberType>collector number</otherNumberType>
<otherNumber>14081</otherNumber>
<responsibleDepartments/>
<objectNumber>JEPS113857</objectNumber>

<title>Juncus tenuis Willd.</title> ... </ns2:collectionobjects_common>

--2ed55496-92f0-464a-822f-b4b20e8782ec--

  1. Perform a search on the keyword "Rockefeller" in the
    CollectionObject service:

curl -u test@collectionspace.org:testtest http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects?kw=rockefeller

Note that the record returned has the same object number,
JEPS113857, and the same CollectionSpace ID (CSID),
f7137ff0-81ee-4d0c-a802, as the record above:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?

<ns2:collectionobjects-common-list xmlns:ns2="http://collectionspace.org/services/collectionobject

" xmlns:ns3="http://collectionspace.org/services/jaxb"><pageNum>0</
pageNum><pageSize>40</pageSize><itemsInPage>1</
itemsInPage><totalItems>1</totalItems><collection-object-list- item><objectNumber>JEPS113857</objectNumber><title>Juncus tenuis
Willd.</title><uri>/collectionobjects/f7137ff0-81ee-4d0c-a802</
uri><csid>f7137ff0-81ee-4d0c-a802</csid></collection-object-list-
item></ns2:collectionobjects-common-list>

  1. Perform a search on the keyword "Rockefeller" in the UI:

Enter "Rockefeller" into the "Search" box at top left.  Keep the
original drop-down menu selection to its left at "Object".  Click
"Search".

One record is returned, matching the record above:

ID Number Summary                Type
JEPS113857 Juncus tenuis Willd. objects

Hi Aron, Thanks so much for your quick reply to this post. I just spoke with Chris P. and you'll see a follow up from him directly as well. Angela On 15 Jun, 2010, at 13:54, Aron Roberts wrote: > Hi Angela, > > In the message "[Talk] Schema Extension and Search in CSpace v1.0", > dated 2010-06-15, Angela Spinazze wrote: > >> During my recent visit to SMK, we talked about the fact that they >> will be extending CSpace schemas to accommodate some SMK-specific >> fields (such as notes). Chris asked about how those fields will be >> accommodated by basic search and advanced search. >> >> In other words, How will fields added as SMK extensions to schemas >> be made available for search? Will these fields be searchable? > > Yes. > >> If so, how? > > A quick test verified that, in the University & Jepson Herbaria > (UCJEPS) instance of CollectionSpace - which is running release 0.6 > - at least for keyword / full text searching, fields added via > extension schema are searchable (below). > > Others may wish to comment on whether these fields can or will also > be made searchable via other means, such as via 'Advanced Search.' > > Aron > > P.S. This UCJEPS instance was used as an example, because it has an > extensive set of custom fields in an extension schema. > > -- > > 1. Retrieve this record via the UI: > > http://ucjeps.collectionspace.org:8180/cspace-ui/html/objects.html?csid=f7137ff0-81ee-4d0c-a802 > > 2. Note the value of the "Field Location Verbatum" field - that it > contains the word "Rockefeller": > > "On the east side of Rockefeller Road, at the intersection of Bald > Rock Road and Rockefeller Road, about 13 miles (air) northeast of > Oroville" > > 3. Retrieve this record via the CollectionObject service: > > curl -u test@collectionspace.org:testtest http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects/f7137ff0-81ee-4d0c-a802 > > Note that in the record returned in the response, the corresponding > field (to "Field Location Verbatum"), fieldLocPlace, is within a > 'collectionobjects_naturalhistory' extension schema: > > --2ed55496-92f0-464a-822f-b4b20e8782ec > label: collectionobjects_naturalhistory > Content-Type: application/xml > > <?xml version="1.0" encoding="UTF-8"?> > <ns2:collectionobjects_naturalhistory xmlns:ns2="http://collectionspace.org/services/collectionobject/domain/naturalhistory > " xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://collectionspace.org/services/collectionobject/domain/naturalhistory > http://collectionspace.org/services/collectionobject/domain/collectionobjects_naturalhistory.xsd > "> > <fieldLocLongDecimal>-121.37944793701172</fieldLocLongDecimal> > <fieldLocLatDecimal>39.664169311523438</fieldLocLatDecimal> > ... > <fieldLocPlace>On the east side of Rockefeller Road, at the > intersection of Bald Rock Road and Rockefeller Road, about 13 miles > (air) northeast of Oroville</fieldLocPlace> > <fieldCollectionDateLatest>Jun 12, 2007</fieldCollectionDateLatest> > <fieldLocElevation>3320 ft</fieldLocElevation> > ... > </ns2:collectionobjects_naturalhistory> > > --2ed55496-92f0-464a-822f-b4b20e8782ec > label: collectionobjects_common > Content-Type: application/xml > > <?xml version="1.0" encoding="UTF-8"?> > <ns2:collectionobjects_common xmlns:ns2="http://collectionspace.org/services/collectionobject > " xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://collectionspace.org/services/collectionobject > http://services.collectionspace.org/collectionobject/collectionobjects_common.xsd > "> > <otherNumberType>collector number</otherNumberType> > <otherNumber>14081</otherNumber> > <responsibleDepartments/> > <objectNumber>JEPS113857</objectNumber> > <title>Juncus tenuis Willd.</title> > ... > </ns2:collectionobjects_common> > > --2ed55496-92f0-464a-822f-b4b20e8782ec-- > > 4. Perform a search on the keyword "Rockefeller" in the > CollectionObject service: > > curl -u test@collectionspace.org:testtest http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects?kw=rockefeller > > Note that the record returned has the same object number, > JEPS113857, and the same CollectionSpace ID (CSID), > f7137ff0-81ee-4d0c-a802, as the record above: > > <?xml version="1.0" encoding="UTF-8" standalone="yes"? > ><ns2:collectionobjects-common-list xmlns:ns2="http://collectionspace.org/services/collectionobject > " xmlns:ns3="http://collectionspace.org/services/jaxb"><pageNum>0</ > pageNum><pageSize>40</pageSize><itemsInPage>1</ > itemsInPage><totalItems>1</totalItems><collection-object-list- > item><objectNumber>JEPS113857</objectNumber><title>Juncus tenuis > Willd.</title><uri>/collectionobjects/f7137ff0-81ee-4d0c-a802</ > uri><csid>f7137ff0-81ee-4d0c-a802</csid></collection-object-list- > item></ns2:collectionobjects-common-list> > > 5. Perform a search on the keyword "Rockefeller" in the UI: > > Enter "Rockefeller" into the "Search" box at top left. Keep the > original drop-down menu selection to its left at "Object". Click > "Search". > > One record is returned, matching the record above: > > ID Number Summary Type > JEPS113857 Juncus tenuis Willd. objects
CP
Christopher Pott
Fri, Jun 18, 2010 9:11 AM

Hi Aron,

Thanks for posting the information and the links. The basic search functionality is exactly what I was hoping for, and I hope someone can comment if it will also be possible to include these fields as their own entries in the advanced search dialog as I feel this will also be important.

I was especially interested to see your deployment of version 0.6, and the natural history schema extensions you had included with your collection objects. Are you defining these extensions yourself, or is it in collaboration with some other similar institutions? I'm asking because we will soon have to investigate a similar schema for fine arts (as well as a local schema) and I'm interested in your experience of this process.

Regards,
Chris

Developer, Corpus Project
Statens Museum for Kunst (National Gallery of Denmark)

-----Oprindelig meddelelse-----
Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
Sendt: 15. juni 2010 20:54
Til: Angela Spinazze
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] Schema Extension and Search in CSpace v1.0

Hi Angela,

In the message "[Talk] Schema Extension and Search in CSpace v1.0",
dated 2010-06-15, Angela Spinazze wrote:

During my recent visit to SMK, we talked about the fact that they
will be extending CSpace schemas to accommodate some SMK-specific
fields (such as notes).  Chris asked about how those fields will be
accommodated by basic search and advanced search.

In other words, How will fields added as SMK extensions to schemas
be made available for search?  Will these fields be searchable?

Yes.

If so, how?

A quick test verified that, in the University & Jepson Herbaria
(UCJEPS) instance of CollectionSpace - which is running release 0.6 -
at least for keyword / full text searching, fields added via
extension schema are searchable (below).

Others may wish to comment on whether these fields can or will also
be made searchable via other means, such as via 'Advanced Search.'

Aron

P.S. This UCJEPS instance was used as an example, because it has an
extensive set of custom fields in an extension schema.

--

  1. Retrieve this record via the UI:

http://ucjeps.collectionspace.org:8180/cspace-ui/html/objects.html?csid=f7137ff0-81ee-4d0c-a802

  1. Note the value of the "Field Location Verbatum" field - that it
    contains the word "Rockefeller":

"On the east side of Rockefeller Road, at the intersection of Bald
Rock Road and Rockefeller Road, about 13 miles (air) northeast of
Oroville"

  1. Retrieve this record via the CollectionObject service:

curl -u test@collectionspace.org:testtest
http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects/f7137ff0-81ee-4d0c-a802

Note that in the record returned in the response, the corresponding
field (to "Field Location Verbatum"), fieldLocPlace, is within a
'collectionobjects_naturalhistory' extension schema:

--2ed55496-92f0-464a-822f-b4b20e8782ec
label: collectionobjects_naturalhistory
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>

<ns2:collectionobjects_naturalhistory
xmlns:ns2="http://collectionspace.org/services/collectionobject/domain/naturalhistory"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://collectionspace.org/services/collectionobject/domain/naturalhistory
http://collectionspace.org/services/collectionobject/domain/collectionobjects_naturalhistory.xsd">
<fieldLocLongDecimal>-121.37944793701172</fieldLocLongDecimal>
<fieldLocLatDecimal>39.664169311523438</fieldLocLatDecimal>
...
<fieldLocPlace>On the east side of Rockefeller Road, at the
intersection of Bald Rock Road and Rockefeller Road, about 13 miles
(air) northeast of Oroville</fieldLocPlace>
<fieldCollectionDateLatest>Jun 12, 2007</fieldCollectionDateLatest>
<fieldLocElevation>3320 ft</fieldLocElevation>
...
</ns2:collectionobjects_naturalhistory>

--2ed55496-92f0-464a-822f-b4b20e8782ec
label: collectionobjects_common
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>

<ns2:collectionobjects_common
xmlns:ns2="http://collectionspace.org/services/collectionobject"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://collectionspace.org/services/collectionobject
http://services.collectionspace.org/collectionobject/collectionobjects_common.xsd">
<otherNumberType>collector number</otherNumberType>
<otherNumber>14081</otherNumber>
<responsibleDepartments/>
<objectNumber>JEPS113857</objectNumber>

<title>Juncus tenuis Willd.</title> ... </ns2:collectionobjects_common>

--2ed55496-92f0-464a-822f-b4b20e8782ec--

  1. Perform a search on the keyword "Rockefeller" in the
    CollectionObject service:

curl -u test@collectionspace.org:testtest
http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects?kw=rockefeller

Note that the record returned has the same object number, JEPS113857,
and the same CollectionSpace ID (CSID), f7137ff0-81ee-4d0c-a802, as
the record above:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:collectionobjects-common-list

xmlns:ns2="http://collectionspace.org/services/collectionobject"
xmlns:ns3="http://collectionspace.org/services/jaxb"><pageNum>0</pageNum><pageSize>40</pageSize><itemsInPage>1</itemsInPage><totalItems>1</totalItems><collection-object-list-item><objectNumber>JEPS113857</objectNumber><title>Juncus
tenuis
Willd.</title><uri>/collectionobjects/f7137ff0-81ee-4d0c-a802</uri><csid>f7137ff0-81ee-4d0c-a802</csid></collection-object-list-item></ns2:collectionobjects-common-list>

  1. Perform a search on the keyword "Rockefeller" in the UI:

Enter "Rockefeller" into the "Search" box at top left.  Keep the
original drop-down menu selection to its left at "Object".  Click
"Search".

One record is returned, matching the record above:

ID Number Summary                Type
JEPS113857 Juncus tenuis Willd. objects

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Hi Aron, Thanks for posting the information and the links. The basic search functionality is exactly what I was hoping for, and I hope someone can comment if it will also be possible to include these fields as their own entries in the advanced search dialog as I feel this will also be important. I was especially interested to see your deployment of version 0.6, and the natural history schema extensions you had included with your collection objects. Are you defining these extensions yourself, or is it in collaboration with some other similar institutions? I'm asking because we will soon have to investigate a similar schema for fine arts (as well as a local schema) and I'm interested in your experience of this process. Regards, Chris Developer, Corpus Project Statens Museum for Kunst (National Gallery of Denmark) -----Oprindelig meddelelse----- Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts Sendt: 15. juni 2010 20:54 Til: Angela Spinazze Cc: talk@lists.collectionspace.org Emne: Re: [Talk] Schema Extension and Search in CSpace v1.0 Hi Angela, In the message "[Talk] Schema Extension and Search in CSpace v1.0", dated 2010-06-15, Angela Spinazze wrote: >During my recent visit to SMK, we talked about the fact that they >will be extending CSpace schemas to accommodate some SMK-specific >fields (such as notes). Chris asked about how those fields will be >accommodated by basic search and advanced search. > >In other words, How will fields added as SMK extensions to schemas >be made available for search? Will these fields be searchable? Yes. > If so, how? A quick test verified that, in the University & Jepson Herbaria (UCJEPS) instance of CollectionSpace - which is running release 0.6 - at least for keyword / full text searching, fields added via extension schema are searchable (below). Others may wish to comment on whether these fields can or will also be made searchable via other means, such as via 'Advanced Search.' Aron P.S. This UCJEPS instance was used as an example, because it has an extensive set of custom fields in an extension schema. -- 1. Retrieve this record via the UI: http://ucjeps.collectionspace.org:8180/cspace-ui/html/objects.html?csid=f7137ff0-81ee-4d0c-a802 2. Note the value of the "Field Location Verbatum" field - that it contains the word "Rockefeller": "On the east side of Rockefeller Road, at the intersection of Bald Rock Road and Rockefeller Road, about 13 miles (air) northeast of Oroville" 3. Retrieve this record via the CollectionObject service: curl -u test@collectionspace.org:testtest http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects/f7137ff0-81ee-4d0c-a802 Note that in the record returned in the response, the corresponding field (to "Field Location Verbatum"), fieldLocPlace, is within a 'collectionobjects_naturalhistory' extension schema: --2ed55496-92f0-464a-822f-b4b20e8782ec label: collectionobjects_naturalhistory Content-Type: application/xml <?xml version="1.0" encoding="UTF-8"?> <ns2:collectionobjects_naturalhistory xmlns:ns2="http://collectionspace.org/services/collectionobject/domain/naturalhistory" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://collectionspace.org/services/collectionobject/domain/naturalhistory http://collectionspace.org/services/collectionobject/domain/collectionobjects_naturalhistory.xsd"> <fieldLocLongDecimal>-121.37944793701172</fieldLocLongDecimal> <fieldLocLatDecimal>39.664169311523438</fieldLocLatDecimal> ... <fieldLocPlace>On the east side of Rockefeller Road, at the intersection of Bald Rock Road and Rockefeller Road, about 13 miles (air) northeast of Oroville</fieldLocPlace> <fieldCollectionDateLatest>Jun 12, 2007</fieldCollectionDateLatest> <fieldLocElevation>3320 ft</fieldLocElevation> ... </ns2:collectionobjects_naturalhistory> --2ed55496-92f0-464a-822f-b4b20e8782ec label: collectionobjects_common Content-Type: application/xml <?xml version="1.0" encoding="UTF-8"?> <ns2:collectionobjects_common xmlns:ns2="http://collectionspace.org/services/collectionobject" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://collectionspace.org/services/collectionobject http://services.collectionspace.org/collectionobject/collectionobjects_common.xsd"> <otherNumberType>collector number</otherNumberType> <otherNumber>14081</otherNumber> <responsibleDepartments/> <objectNumber>JEPS113857</objectNumber> <title>Juncus tenuis Willd.</title> ... </ns2:collectionobjects_common> --2ed55496-92f0-464a-822f-b4b20e8782ec-- 4. Perform a search on the keyword "Rockefeller" in the CollectionObject service: curl -u test@collectionspace.org:testtest http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects?kw=rockefeller Note that the record returned has the same object number, JEPS113857, and the same CollectionSpace ID (CSID), f7137ff0-81ee-4d0c-a802, as the record above: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:collectionobjects-common-list xmlns:ns2="http://collectionspace.org/services/collectionobject" xmlns:ns3="http://collectionspace.org/services/jaxb"><pageNum>0</pageNum><pageSize>40</pageSize><itemsInPage>1</itemsInPage><totalItems>1</totalItems><collection-object-list-item><objectNumber>JEPS113857</objectNumber><title>Juncus tenuis Willd.</title><uri>/collectionobjects/f7137ff0-81ee-4d0c-a802</uri><csid>f7137ff0-81ee-4d0c-a802</csid></collection-object-list-item></ns2:collectionobjects-common-list> 5. Perform a search on the keyword "Rockefeller" in the UI: Enter "Rockefeller" into the "Search" box at top left. Keep the original drop-down menu selection to its left at "Object". Click "Search". One record is returned, matching the record above: ID Number Summary Type JEPS113857 Juncus tenuis Willd. objects _______________________________________________ Talk mailing list Talk@lists.collectionspace.org http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
CH
Chris Hoffman
Fri, Jun 18, 2010 3:50 PM

Hi Chris,

At Berkeley, we've been talking with a group of natural history museums (the Berkeley Natural History Museum consortium) for a couple years, and my team manages collection management systems for several of these right now.  I believe that Aron and the services team have set up a schema extension for the natural history domain partly to demonstrate how this is going to work.  From my perspective, the fields they put in that set are likely to change.  My team is working closely with the Berkeley Natural History Museums to identify the schema extensions that will be needed.  The schema extensions are absolutely critical to our deployments at UC Berkeley.  We did some great customizations for the UC and Jepson Herbaria on top of the 0.6 version of CollectionSpace.  We'll be interested to hear about schema extensions at SMK too!

Thanks,
Chris

On Jun 18, 2010, at 2:11 AM, Christopher Pott wrote:

Hi Aron,

Thanks for posting the information and the links. The basic search functionality is exactly what I was hoping for, and I hope someone can comment if it will also be possible to include these fields as their own entries in the advanced search dialog as I feel this will also be important.

I was especially interested to see your deployment of version 0.6, and the natural history schema extensions you had included with your collection objects. Are you defining these extensions yourself, or is it in collaboration with some other similar institutions? I'm asking because we will soon have to investigate a similar schema for fine arts (as well as a local schema) and I'm interested in your experience of this process.

Regards,
Chris

Developer, Corpus Project
Statens Museum for Kunst (National Gallery of Denmark)

-----Oprindelig meddelelse-----
Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
Sendt: 15. juni 2010 20:54
Til: Angela Spinazze
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] Schema Extension and Search in CSpace v1.0

Hi Angela,

In the message "[Talk] Schema Extension and Search in CSpace v1.0",
dated 2010-06-15, Angela Spinazze wrote:

During my recent visit to SMK, we talked about the fact that they
will be extending CSpace schemas to accommodate some SMK-specific
fields (such as notes).  Chris asked about how those fields will be
accommodated by basic search and advanced search.

In other words, How will fields added as SMK extensions to schemas
be made available for search?  Will these fields be searchable?

Yes.

If so, how?

A quick test verified that, in the University & Jepson Herbaria
(UCJEPS) instance of CollectionSpace - which is running release 0.6 -
at least for keyword / full text searching, fields added via
extension schema are searchable (below).

Others may wish to comment on whether these fields can or will also
be made searchable via other means, such as via 'Advanced Search.'

Aron

P.S. This UCJEPS instance was used as an example, because it has an
extensive set of custom fields in an extension schema.

--

  1. Retrieve this record via the UI:

http://ucjeps.collectionspace.org:8180/cspace-ui/html/objects.html?csid=f7137ff0-81ee-4d0c-a802

  1. Note the value of the "Field Location Verbatum" field - that it
    contains the word "Rockefeller":

"On the east side of Rockefeller Road, at the intersection of Bald
Rock Road and Rockefeller Road, about 13 miles (air) northeast of
Oroville"

  1. Retrieve this record via the CollectionObject service:

curl -u test@collectionspace.org:testtest
http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects/f7137ff0-81ee-4d0c-a802

Note that in the record returned in the response, the corresponding
field (to "Field Location Verbatum"), fieldLocPlace, is within a
'collectionobjects_naturalhistory' extension schema:

--2ed55496-92f0-464a-822f-b4b20e8782ec
label: collectionobjects_naturalhistory
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>

<ns2:collectionobjects_naturalhistory
xmlns:ns2="http://collectionspace.org/services/collectionobject/domain/naturalhistory"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://collectionspace.org/services/collectionobject/domain/naturalhistory
http://collectionspace.org/services/collectionobject/domain/collectionobjects_naturalhistory.xsd">
<fieldLocLongDecimal>-121.37944793701172</fieldLocLongDecimal>
<fieldLocLatDecimal>39.664169311523438</fieldLocLatDecimal>
...
<fieldLocPlace>On the east side of Rockefeller Road, at the
intersection of Bald Rock Road and Rockefeller Road, about 13 miles
(air) northeast of Oroville</fieldLocPlace>
<fieldCollectionDateLatest>Jun 12, 2007</fieldCollectionDateLatest>
<fieldLocElevation>3320 ft</fieldLocElevation>
...
</ns2:collectionobjects_naturalhistory>

--2ed55496-92f0-464a-822f-b4b20e8782ec
label: collectionobjects_common
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>

<ns2:collectionobjects_common
xmlns:ns2="http://collectionspace.org/services/collectionobject"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://collectionspace.org/services/collectionobject
http://services.collectionspace.org/collectionobject/collectionobjects_common.xsd">
<otherNumberType>collector number</otherNumberType>
<otherNumber>14081</otherNumber>
<responsibleDepartments/>
<objectNumber>JEPS113857</objectNumber>

<title>Juncus tenuis Willd.</title> ... </ns2:collectionobjects_common>

--2ed55496-92f0-464a-822f-b4b20e8782ec--

  1. Perform a search on the keyword "Rockefeller" in the
    CollectionObject service:

curl -u test@collectionspace.org:testtest
http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects?kw=rockefeller

Note that the record returned has the same object number, JEPS113857,
and the same CollectionSpace ID (CSID), f7137ff0-81ee-4d0c-a802, as
the record above:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:collectionobjects-common-list

xmlns:ns2="http://collectionspace.org/services/collectionobject"
xmlns:ns3="http://collectionspace.org/services/jaxb"><pageNum>0</pageNum><pageSize>40</pageSize><itemsInPage>1</itemsInPage><totalItems>1</totalItems><collection-object-list-item><objectNumber>JEPS113857</objectNumber><title>Juncus
tenuis
Willd.</title><uri>/collectionobjects/f7137ff0-81ee-4d0c-a802</uri><csid>f7137ff0-81ee-4d0c-a802</csid></collection-object-list-item></ns2:collectionobjects-common-list>

  1. Perform a search on the keyword "Rockefeller" in the UI:

Enter "Rockefeller" into the "Search" box at top left.  Keep the
original drop-down menu selection to its left at "Object".  Click
"Search".

One record is returned, matching the record above:

ID Number Summary                Type
JEPS113857 Juncus tenuis Willd. objects

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

Hi Chris, At Berkeley, we've been talking with a group of natural history museums (the Berkeley Natural History Museum consortium) for a couple years, and my team manages collection management systems for several of these right now. I believe that Aron and the services team have set up a schema extension for the natural history domain partly to demonstrate how this is going to work. From my perspective, the fields they put in that set are likely to change. My team is working closely with the Berkeley Natural History Museums to identify the schema extensions that will be needed. The schema extensions are absolutely critical to our deployments at UC Berkeley. We did some great customizations for the UC and Jepson Herbaria on top of the 0.6 version of CollectionSpace. We'll be interested to hear about schema extensions at SMK too! Thanks, Chris On Jun 18, 2010, at 2:11 AM, Christopher Pott wrote: > Hi Aron, > > Thanks for posting the information and the links. The basic search functionality is exactly what I was hoping for, and I hope someone can comment if it will also be possible to include these fields as their own entries in the advanced search dialog as I feel this will also be important. > > I was especially interested to see your deployment of version 0.6, and the natural history schema extensions you had included with your collection objects. Are you defining these extensions yourself, or is it in collaboration with some other similar institutions? I'm asking because we will soon have to investigate a similar schema for fine arts (as well as a local schema) and I'm interested in your experience of this process. > > Regards, > Chris > > Developer, Corpus Project > Statens Museum for Kunst (National Gallery of Denmark) > > -----Oprindelig meddelelse----- > Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts > Sendt: 15. juni 2010 20:54 > Til: Angela Spinazze > Cc: talk@lists.collectionspace.org > Emne: Re: [Talk] Schema Extension and Search in CSpace v1.0 > > Hi Angela, > > In the message "[Talk] Schema Extension and Search in CSpace v1.0", > dated 2010-06-15, Angela Spinazze wrote: > >> During my recent visit to SMK, we talked about the fact that they >> will be extending CSpace schemas to accommodate some SMK-specific >> fields (such as notes). Chris asked about how those fields will be >> accommodated by basic search and advanced search. >> >> In other words, How will fields added as SMK extensions to schemas >> be made available for search? Will these fields be searchable? > > Yes. > >> If so, how? > > A quick test verified that, in the University & Jepson Herbaria > (UCJEPS) instance of CollectionSpace - which is running release 0.6 - > at least for keyword / full text searching, fields added via > extension schema are searchable (below). > > Others may wish to comment on whether these fields can or will also > be made searchable via other means, such as via 'Advanced Search.' > > Aron > > P.S. This UCJEPS instance was used as an example, because it has an > extensive set of custom fields in an extension schema. > > -- > > 1. Retrieve this record via the UI: > > http://ucjeps.collectionspace.org:8180/cspace-ui/html/objects.html?csid=f7137ff0-81ee-4d0c-a802 > > 2. Note the value of the "Field Location Verbatum" field - that it > contains the word "Rockefeller": > > "On the east side of Rockefeller Road, at the intersection of Bald > Rock Road and Rockefeller Road, about 13 miles (air) northeast of > Oroville" > > 3. Retrieve this record via the CollectionObject service: > > curl -u test@collectionspace.org:testtest > http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects/f7137ff0-81ee-4d0c-a802 > > Note that in the record returned in the response, the corresponding > field (to "Field Location Verbatum"), fieldLocPlace, is within a > 'collectionobjects_naturalhistory' extension schema: > > --2ed55496-92f0-464a-822f-b4b20e8782ec > label: collectionobjects_naturalhistory > Content-Type: application/xml > > <?xml version="1.0" encoding="UTF-8"?> > <ns2:collectionobjects_naturalhistory > xmlns:ns2="http://collectionspace.org/services/collectionobject/domain/naturalhistory" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://collectionspace.org/services/collectionobject/domain/naturalhistory > http://collectionspace.org/services/collectionobject/domain/collectionobjects_naturalhistory.xsd"> > <fieldLocLongDecimal>-121.37944793701172</fieldLocLongDecimal> > <fieldLocLatDecimal>39.664169311523438</fieldLocLatDecimal> > ... > <fieldLocPlace>On the east side of Rockefeller Road, at the > intersection of Bald Rock Road and Rockefeller Road, about 13 miles > (air) northeast of Oroville</fieldLocPlace> > <fieldCollectionDateLatest>Jun 12, 2007</fieldCollectionDateLatest> > <fieldLocElevation>3320 ft</fieldLocElevation> > ... > </ns2:collectionobjects_naturalhistory> > > --2ed55496-92f0-464a-822f-b4b20e8782ec > label: collectionobjects_common > Content-Type: application/xml > > <?xml version="1.0" encoding="UTF-8"?> > <ns2:collectionobjects_common > xmlns:ns2="http://collectionspace.org/services/collectionobject" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://collectionspace.org/services/collectionobject > http://services.collectionspace.org/collectionobject/collectionobjects_common.xsd"> > <otherNumberType>collector number</otherNumberType> > <otherNumber>14081</otherNumber> > <responsibleDepartments/> > <objectNumber>JEPS113857</objectNumber> > <title>Juncus tenuis Willd.</title> > ... > </ns2:collectionobjects_common> > > --2ed55496-92f0-464a-822f-b4b20e8782ec-- > > 4. Perform a search on the keyword "Rockefeller" in the > CollectionObject service: > > curl -u test@collectionspace.org:testtest > http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects?kw=rockefeller > > Note that the record returned has the same object number, JEPS113857, > and the same CollectionSpace ID (CSID), f7137ff0-81ee-4d0c-a802, as > the record above: > > <?xml version="1.0" encoding="UTF-8" > standalone="yes"?><ns2:collectionobjects-common-list > xmlns:ns2="http://collectionspace.org/services/collectionobject" > xmlns:ns3="http://collectionspace.org/services/jaxb"><pageNum>0</pageNum><pageSize>40</pageSize><itemsInPage>1</itemsInPage><totalItems>1</totalItems><collection-object-list-item><objectNumber>JEPS113857</objectNumber><title>Juncus > tenuis > Willd.</title><uri>/collectionobjects/f7137ff0-81ee-4d0c-a802</uri><csid>f7137ff0-81ee-4d0c-a802</csid></collection-object-list-item></ns2:collectionobjects-common-list> > > 5. Perform a search on the keyword "Rockefeller" in the UI: > > Enter "Rockefeller" into the "Search" box at top left. Keep the > original drop-down menu selection to its left at "Object". Click > "Search". > > One record is returned, matching the record above: > > ID Number Summary Type > JEPS113857 Juncus tenuis Willd. objects > > _______________________________________________ > 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
Fri, Jun 18, 2010 5:36 PM

On Fri, Jun 18, 2010 at 2:11 AM, Christopher Pott
Christopher.Pott@smk.dk wrote:

I was especially interested to see your deployment of version 0.6,
and the natural history schema extensions you had included with
your collection objects. Are you defining these extensions yourself,
or is it in collaboration with some other similar institutions?
I'm asking because we will soon have to investigate a similar
schema for fine arts (as well as a local schema) and I'm interested
in your experience of this process.

As far as I'm aware - and our Museum Informatics folks would have
the definitive answer - the use of a 'collectionobject_naturalhistory'
namespace for a custom schema extension to CollectionObjects is purely
a matter of convenience at this point, and does not imply that any
collaborative work has taken place among institutions to define such
an extension.

That namespace is already defined - as a representative example /
placeholder, for custom schema extensions in client tests of the
CollectionObject service in CollectionSpace.

We do hope and envision that institutions using CollectionSpace will
collaborate on domain-specific schema extensions, in the fine arts, in
the natural sciences and its sub-domains, and in many other
communities of shared interest and practice.  And we're keenly
interested in your thoughts about how to best foster that activity!

Aron

Regards,
Chris

Developer, Corpus Project
Statens Museum for Kunst (National Gallery of Denmark)

-----Oprindelig meddelelse-----
Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
Sendt: 15. juni 2010 20:54
Til: Angela Spinazze
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] Schema Extension and Search in CSpace v1.0

Hi Angela,

In the message "[Talk] Schema Extension and Search in CSpace v1.0",
dated 2010-06-15, Angela Spinazze wrote:

During my recent visit to SMK, we talked about the fact that they
will be extending CSpace schemas to accommodate some SMK-specific
fields (such as notes).  Chris asked about how those fields will be
accommodated by basic search and advanced search.

In other words, How will fields added as SMK extensions to schemas
be made available for search?  Will these fields be searchable?

  Yes.

  If so, how?

  A quick test verified that, in the University & Jepson Herbaria
(UCJEPS) instance of CollectionSpace - which is running release 0.6 -
at least for keyword / full text searching, fields added via
extension schema are searchable (below).

  Others may wish to comment on whether these fields can or will also
be made searchable via other means, such as via 'Advanced Search.'

Aron

P.S. This UCJEPS instance was used as an example, because it has an
extensive set of custom fields in an extension schema.

--

  1. Retrieve this record via the UI:

http://ucjeps.collectionspace.org:8180/cspace-ui/html/objects.html?csid=f7137ff0-81ee-4d0c-a802

  1. Note the value of the "Field Location Verbatum" field - that it
    contains the word "Rockefeller":

"On the east side of Rockefeller Road, at the intersection of Bald
Rock Road and Rockefeller Road, about 13 miles (air) northeast of
Oroville"

  1. Retrieve this record via the CollectionObject service:

curl -u test@collectionspace.org:testtest
http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects/f7137ff0-81ee-4d0c-a802

Note that in the record returned in the response, the corresponding
field (to "Field Location Verbatum"), fieldLocPlace, is within a
'collectionobjects_naturalhistory' extension schema:

--2ed55496-92f0-464a-822f-b4b20e8782ec
label: collectionobjects_naturalhistory
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>

<ns2:collectionobjects_naturalhistory
xmlns:ns2="http://collectionspace.org/services/collectionobject/domain/naturalhistory"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://collectionspace.org/services/collectionobject/domain/naturalhistory
http://collectionspace.org/services/collectionobject/domain/collectionobjects_naturalhistory.xsd">
<fieldLocLongDecimal>-121.37944793701172</fieldLocLongDecimal>
<fieldLocLatDecimal>39.664169311523438</fieldLocLatDecimal>
...
<fieldLocPlace>On the east side of Rockefeller Road, at the
intersection of Bald Rock Road and Rockefeller Road, about 13 miles
(air) northeast of Oroville</fieldLocPlace>
<fieldCollectionDateLatest>Jun 12, 2007</fieldCollectionDateLatest>
<fieldLocElevation>3320 ft</fieldLocElevation>
...
</ns2:collectionobjects_naturalhistory>

--2ed55496-92f0-464a-822f-b4b20e8782ec
label: collectionobjects_common
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>

<ns2:collectionobjects_common
xmlns:ns2="http://collectionspace.org/services/collectionobject"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://collectionspace.org/services/collectionobject
http://services.collectionspace.org/collectionobject/collectionobjects_common.xsd">
<otherNumberType>collector number</otherNumberType>
<otherNumber>14081</otherNumber>
<responsibleDepartments/>
<objectNumber>JEPS113857</objectNumber>

<title>Juncus tenuis Willd.</title> ... </ns2:collectionobjects_common>

--2ed55496-92f0-464a-822f-b4b20e8782ec--

  1. Perform a search on the keyword "Rockefeller" in the
    CollectionObject service:

curl -u test@collectionspace.org:testtest
http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects?kw=rockefeller

Note that the record returned has the same object number, JEPS113857,
and the same CollectionSpace ID (CSID), f7137ff0-81ee-4d0c-a802, as
the record above:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:collectionobjects-common-list

xmlns:ns2="http://collectionspace.org/services/collectionobject"
xmlns:ns3="http://collectionspace.org/services/jaxb"><pageNum>0</pageNum><pageSize>40</pageSize><itemsInPage>1</itemsInPage><totalItems>1</totalItems><collection-object-list-item><objectNumber>JEPS113857</objectNumber><title>Juncus
tenuis
Willd.</title><uri>/collectionobjects/f7137ff0-81ee-4d0c-a802</uri><csid>f7137ff0-81ee-4d0c-a802</csid></collection-object-list-item></ns2:collectionobjects-common-list>

  1. Perform a search on the keyword "Rockefeller" in the UI:

Enter "Rockefeller" into the "Search" box at top left.  Keep the
original drop-down menu selection to its left at "Object".  Click
"Search".

One record is returned, matching the record above:

ID Number       Summary                 Type
JEPS113857      Juncus tenuis Willd.    objects

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

On Fri, Jun 18, 2010 at 2:11 AM, Christopher Pott <Christopher.Pott@smk.dk> wrote: > I was especially interested to see your deployment of version 0.6, > and the natural history schema extensions you had included with > your collection objects. Are you defining these extensions yourself, > or is it in collaboration with some other similar institutions? > I'm asking because we will soon have to investigate a similar > schema for fine arts (as well as a local schema) and I'm interested > in your experience of this process. As far as I'm aware - and our Museum Informatics folks would have the definitive answer - the use of a 'collectionobject_naturalhistory' namespace for a custom schema extension to CollectionObjects is purely a matter of convenience at this point, and does not imply that any collaborative work has taken place among institutions to define such an extension. That namespace is already defined - as a representative example / placeholder, for custom schema extensions in client tests of the CollectionObject service in CollectionSpace. We do hope and envision that institutions using CollectionSpace will collaborate on domain-specific schema extensions, in the fine arts, in the natural sciences and its sub-domains, and in many other communities of shared interest and practice. And we're keenly interested in your thoughts about how to best foster that activity! Aron > > Regards, > Chris > > Developer, Corpus Project > Statens Museum for Kunst (National Gallery of Denmark) > > -----Oprindelig meddelelse----- > Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts > Sendt: 15. juni 2010 20:54 > Til: Angela Spinazze > Cc: talk@lists.collectionspace.org > Emne: Re: [Talk] Schema Extension and Search in CSpace v1.0 > > Hi Angela, > > In the message "[Talk] Schema Extension and Search in CSpace v1.0", > dated 2010-06-15, Angela Spinazze wrote: > >>During my recent visit to SMK, we talked about the fact that they >>will be extending CSpace schemas to accommodate some SMK-specific >>fields (such as notes).  Chris asked about how those fields will be >>accommodated by basic search and advanced search. >> >>In other words, How will fields added as SMK extensions to schemas >>be made available for search?  Will these fields be searchable? > >   Yes. > >>   If so, how? > >   A quick test verified that, in the University & Jepson Herbaria > (UCJEPS) instance of CollectionSpace - which is running release 0.6 - > at least for keyword / full text searching, fields added via > extension schema are searchable (below). > >   Others may wish to comment on whether these fields can or will also > be made searchable via other means, such as via 'Advanced Search.' > > Aron > > P.S. This UCJEPS instance was used as an example, because it has an > extensive set of custom fields in an extension schema. > > -- > > 1. Retrieve this record via the UI: > > http://ucjeps.collectionspace.org:8180/cspace-ui/html/objects.html?csid=f7137ff0-81ee-4d0c-a802 > > 2. Note the value of the "Field Location Verbatum" field - that it > contains the word "Rockefeller": > > "On the east side of Rockefeller Road, at the intersection of Bald > Rock Road and Rockefeller Road, about 13 miles (air) northeast of > Oroville" > > 3. Retrieve this record via the CollectionObject service: > > curl -u test@collectionspace.org:testtest > http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects/f7137ff0-81ee-4d0c-a802 > > Note that in the record returned in the response, the corresponding > field (to "Field Location Verbatum"), fieldLocPlace, is within a > 'collectionobjects_naturalhistory' extension schema: > > --2ed55496-92f0-464a-822f-b4b20e8782ec > label: collectionobjects_naturalhistory > Content-Type: application/xml > > <?xml version="1.0" encoding="UTF-8"?> > <ns2:collectionobjects_naturalhistory > xmlns:ns2="http://collectionspace.org/services/collectionobject/domain/naturalhistory" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://collectionspace.org/services/collectionobject/domain/naturalhistory > http://collectionspace.org/services/collectionobject/domain/collectionobjects_naturalhistory.xsd"> > <fieldLocLongDecimal>-121.37944793701172</fieldLocLongDecimal> > <fieldLocLatDecimal>39.664169311523438</fieldLocLatDecimal> > ... > <fieldLocPlace>On the east side of Rockefeller Road, at the > intersection of Bald Rock Road and Rockefeller Road, about 13 miles > (air) northeast of Oroville</fieldLocPlace> > <fieldCollectionDateLatest>Jun 12, 2007</fieldCollectionDateLatest> > <fieldLocElevation>3320 ft</fieldLocElevation> > ... > </ns2:collectionobjects_naturalhistory> > > --2ed55496-92f0-464a-822f-b4b20e8782ec > label: collectionobjects_common > Content-Type: application/xml > > <?xml version="1.0" encoding="UTF-8"?> > <ns2:collectionobjects_common > xmlns:ns2="http://collectionspace.org/services/collectionobject" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://collectionspace.org/services/collectionobject > http://services.collectionspace.org/collectionobject/collectionobjects_common.xsd"> > <otherNumberType>collector number</otherNumberType> > <otherNumber>14081</otherNumber> > <responsibleDepartments/> > <objectNumber>JEPS113857</objectNumber> > <title>Juncus tenuis Willd.</title> > ... > </ns2:collectionobjects_common> > > --2ed55496-92f0-464a-822f-b4b20e8782ec-- > > 4. Perform a search on the keyword "Rockefeller" in the > CollectionObject service: > > curl -u test@collectionspace.org:testtest > http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects?kw=rockefeller > > Note that the record returned has the same object number, JEPS113857, > and the same CollectionSpace ID (CSID), f7137ff0-81ee-4d0c-a802, as > the record above: > > <?xml version="1.0" encoding="UTF-8" > standalone="yes"?><ns2:collectionobjects-common-list > xmlns:ns2="http://collectionspace.org/services/collectionobject" > xmlns:ns3="http://collectionspace.org/services/jaxb"><pageNum>0</pageNum><pageSize>40</pageSize><itemsInPage>1</itemsInPage><totalItems>1</totalItems><collection-object-list-item><objectNumber>JEPS113857</objectNumber><title>Juncus > tenuis > Willd.</title><uri>/collectionobjects/f7137ff0-81ee-4d0c-a802</uri><csid>f7137ff0-81ee-4d0c-a802</csid></collection-object-list-item></ns2:collectionobjects-common-list> > > 5. Perform a search on the keyword "Rockefeller" in the UI: > > Enter "Rockefeller" into the "Search" box at top left.  Keep the > original drop-down menu selection to its left at "Object".  Click > "Search". > > One record is returned, matching the record above: > > ID Number       Summary                 Type > JEPS113857      Juncus tenuis Willd.    objects > > _______________________________________________ > 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
Fri, Jun 18, 2010 5:44 PM

Hi Chris,

On Fri, Jun 18, 2010 at 10:36 AM, Aron Roberts
aron@socrates.berkeley.edu wrote:

On Fri, Jun 18, 2010 at 2:11 AM, Christopher Pott
Christopher.Pott@smk.dk wrote:

I was especially interested to see your deployment of version 0.6,
and the natural history schema extensions you had included with
your collection objects. Are you defining these extensions yourself,
or is it in collaboration with some other similar institutions? ...

 As far as I'm aware - and our Museum Informatics folks would have
the definitive answer - the use of a 'collectionobject_naturalhistory'
namespace for a custom schema extension to CollectionObjects is purely
a matter of convenience at this point, and does not imply that any
collaborative work has taken place among institutions to define such
an extension.

I wrote this before seeing Chris Hoffman's response, confirming the above.

We envision that schema extensions might be defined in any number of contexts:

  • By an individual institution, or one of its units.

  • By a set of institutions under common affiliation with a parent.

  • By a set of collaborating institutions.

  • By a society or association of institutions or professionals within
    a particular domain.

  • And in a number of other contexts ...

    There have also been some early discussions and thoughts shared
    about governance of schema extensions, including dissemination and
    maintenance of those extensions.  Once again, SMK's input on this and
    other topics is extremely welcome!

    An early overview document that discusses schema extensions:

    Services Architecture
    http://wiki.collectionspace.org/display/collectionspace/Services+Architecture

Aron

Hi Chris, On Fri, Jun 18, 2010 at 10:36 AM, Aron Roberts <aron@socrates.berkeley.edu> wrote: > On Fri, Jun 18, 2010 at 2:11 AM, Christopher Pott > <Christopher.Pott@smk.dk> wrote: >> I was especially interested to see your deployment of version 0.6, >> and the natural history schema extensions you had included with >> your collection objects. Are you defining these extensions yourself, >> or is it in collaboration with some other similar institutions? ... > >  As far as I'm aware - and our Museum Informatics folks would have > the definitive answer - the use of a 'collectionobject_naturalhistory' > namespace for a custom schema extension to CollectionObjects is purely > a matter of convenience at this point, and does not imply that any > collaborative work has taken place among institutions to define such > an extension. I wrote this before seeing Chris Hoffman's response, confirming the above. We envision that schema extensions might be defined in any number of contexts: * By an individual institution, or one of its units. * By a set of institutions under common affiliation with a parent. * By a set of collaborating institutions. * By a society or association of institutions or professionals within a particular domain. * And in a number of other contexts ... There have also been some early discussions and thoughts shared about governance of schema extensions, including dissemination and maintenance of those extensions. Once again, SMK's input on this and other topics is extremely welcome! An early overview document that discusses schema extensions: Services Architecture http://wiki.collectionspace.org/display/collectionspace/Services+Architecture Aron
CP
Christopher Pott
Tue, Jun 22, 2010 1:16 PM

Hi, and thanks for the responses.

We're at the point now where we've mapped most of our fields to the current schemas and have identified a number of extensions which we need to create. Initially I will add these to the deployment all as local extensions only, but I haven't started this work yet. In parallel my colleagues (with the necessary domain expertise) will open a discussion together with other institutions and start building a domain specific schema for the fine arts. At this time I don't know the form this discussion will take but we'll keep you posted.

/Chris

-----Oprindelig meddelelse-----
Fra: Chris Hoffman [mailto:chris.hoffman@berkeley.edu]
Sendt: 18. juni 2010 17:51
Til: Christopher Pott
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] Schema Extension and Search in CSpace v1.0

Hi Chris,

At Berkeley, we've been talking with a group of natural history museums (the Berkeley Natural History Museum consortium) for a couple years, and my team manages collection management systems for several of these right now.  I believe that Aron and the services team have set up a schema extension for the natural history domain partly to demonstrate how this is going to work.  From my perspective, the fields they put in that set are likely to change.  My team is working closely with the Berkeley Natural History Museums to identify the schema extensions that will be needed.  The schema extensions are absolutely critical to our deployments at UC Berkeley.  We did some great customizations for the UC and Jepson Herbaria on top of the 0.6 version of CollectionSpace.  We'll be interested to hear about schema extensions at SMK too!

Thanks,
Chris

On Jun 18, 2010, at 2:11 AM, Christopher Pott wrote:

Hi Aron,

Thanks for posting the information and the links. The basic search functionality is exactly what I was hoping for, and I hope someone can comment if it will also be possible to include these fields as their own entries in the advanced search dialog as I feel this will also be important.

I was especially interested to see your deployment of version 0.6, and the natural history schema extensions you had included with your collection objects. Are you defining these extensions yourself, or is it in collaboration with some other similar institutions? I'm asking because we will soon have to investigate a similar schema for fine arts (as well as a local schema) and I'm interested in your experience of this process.

Regards,
Chris

Developer, Corpus Project
Statens Museum for Kunst (National Gallery of Denmark)

-----Oprindelig meddelelse-----
Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts
Sendt: 15. juni 2010 20:54
Til: Angela Spinazze
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] Schema Extension and Search in CSpace v1.0

Hi Angela,

In the message "[Talk] Schema Extension and Search in CSpace v1.0",
dated 2010-06-15, Angela Spinazze wrote:

During my recent visit to SMK, we talked about the fact that they
will be extending CSpace schemas to accommodate some SMK-specific
fields (such as notes).  Chris asked about how those fields will be
accommodated by basic search and advanced search.

In other words, How will fields added as SMK extensions to schemas
be made available for search?  Will these fields be searchable?

Yes.

If so, how?

A quick test verified that, in the University & Jepson Herbaria
(UCJEPS) instance of CollectionSpace - which is running release 0.6 -
at least for keyword / full text searching, fields added via
extension schema are searchable (below).

Others may wish to comment on whether these fields can or will also
be made searchable via other means, such as via 'Advanced Search.'

Aron

P.S. This UCJEPS instance was used as an example, because it has an
extensive set of custom fields in an extension schema.

--

  1. Retrieve this record via the UI:

http://ucjeps.collectionspace.org:8180/cspace-ui/html/objects.html?csid=f7137ff0-81ee-4d0c-a802

  1. Note the value of the "Field Location Verbatum" field - that it
    contains the word "Rockefeller":

"On the east side of Rockefeller Road, at the intersection of Bald
Rock Road and Rockefeller Road, about 13 miles (air) northeast of
Oroville"

  1. Retrieve this record via the CollectionObject service:

curl -u test@collectionspace.org:testtest
http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects/f7137ff0-81ee-4d0c-a802

Note that in the record returned in the response, the corresponding
field (to "Field Location Verbatum"), fieldLocPlace, is within a
'collectionobjects_naturalhistory' extension schema:

--2ed55496-92f0-464a-822f-b4b20e8782ec
label: collectionobjects_naturalhistory
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>

<ns2:collectionobjects_naturalhistory
xmlns:ns2="http://collectionspace.org/services/collectionobject/domain/naturalhistory"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://collectionspace.org/services/collectionobject/domain/naturalhistory
http://collectionspace.org/services/collectionobject/domain/collectionobjects_naturalhistory.xsd">
<fieldLocLongDecimal>-121.37944793701172</fieldLocLongDecimal>
<fieldLocLatDecimal>39.664169311523438</fieldLocLatDecimal>
...
<fieldLocPlace>On the east side of Rockefeller Road, at the
intersection of Bald Rock Road and Rockefeller Road, about 13 miles
(air) northeast of Oroville</fieldLocPlace>
<fieldCollectionDateLatest>Jun 12, 2007</fieldCollectionDateLatest>
<fieldLocElevation>3320 ft</fieldLocElevation>
...
</ns2:collectionobjects_naturalhistory>

--2ed55496-92f0-464a-822f-b4b20e8782ec
label: collectionobjects_common
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>

<ns2:collectionobjects_common
xmlns:ns2="http://collectionspace.org/services/collectionobject"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://collectionspace.org/services/collectionobject
http://services.collectionspace.org/collectionobject/collectionobjects_common.xsd">
<otherNumberType>collector number</otherNumberType>
<otherNumber>14081</otherNumber>
<responsibleDepartments/>
<objectNumber>JEPS113857</objectNumber>

<title>Juncus tenuis Willd.</title> ... </ns2:collectionobjects_common>

--2ed55496-92f0-464a-822f-b4b20e8782ec--

  1. Perform a search on the keyword "Rockefeller" in the
    CollectionObject service:

curl -u test@collectionspace.org:testtest
http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects?kw=rockefeller

Note that the record returned has the same object number, JEPS113857,
and the same CollectionSpace ID (CSID), f7137ff0-81ee-4d0c-a802, as
the record above:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:collectionobjects-common-list

xmlns:ns2="http://collectionspace.org/services/collectionobject"
xmlns:ns3="http://collectionspace.org/services/jaxb"><pageNum>0</pageNum><pageSize>40</pageSize><itemsInPage>1</itemsInPage><totalItems>1</totalItems><collection-object-list-item><objectNumber>JEPS113857</objectNumber><title>Juncus
tenuis
Willd.</title><uri>/collectionobjects/f7137ff0-81ee-4d0c-a802</uri><csid>f7137ff0-81ee-4d0c-a802</csid></collection-object-list-item></ns2:collectionobjects-common-list>

  1. Perform a search on the keyword "Rockefeller" in the UI:

Enter "Rockefeller" into the "Search" box at top left.  Keep the
original drop-down menu selection to its left at "Object".  Click
"Search".

One record is returned, matching the record above:

ID Number Summary                Type
JEPS113857 Juncus tenuis Willd. objects

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

Hi, and thanks for the responses. We're at the point now where we've mapped most of our fields to the current schemas and have identified a number of extensions which we need to create. Initially I will add these to the deployment all as local extensions only, but I haven't started this work yet. In parallel my colleagues (with the necessary domain expertise) will open a discussion together with other institutions and start building a domain specific schema for the fine arts. At this time I don't know the form this discussion will take but we'll keep you posted. /Chris -----Oprindelig meddelelse----- Fra: Chris Hoffman [mailto:chris.hoffman@berkeley.edu] Sendt: 18. juni 2010 17:51 Til: Christopher Pott Cc: talk@lists.collectionspace.org Emne: Re: [Talk] Schema Extension and Search in CSpace v1.0 Hi Chris, At Berkeley, we've been talking with a group of natural history museums (the Berkeley Natural History Museum consortium) for a couple years, and my team manages collection management systems for several of these right now. I believe that Aron and the services team have set up a schema extension for the natural history domain partly to demonstrate how this is going to work. From my perspective, the fields they put in that set are likely to change. My team is working closely with the Berkeley Natural History Museums to identify the schema extensions that will be needed. The schema extensions are absolutely critical to our deployments at UC Berkeley. We did some great customizations for the UC and Jepson Herbaria on top of the 0.6 version of CollectionSpace. We'll be interested to hear about schema extensions at SMK too! Thanks, Chris On Jun 18, 2010, at 2:11 AM, Christopher Pott wrote: > Hi Aron, > > Thanks for posting the information and the links. The basic search functionality is exactly what I was hoping for, and I hope someone can comment if it will also be possible to include these fields as their own entries in the advanced search dialog as I feel this will also be important. > > I was especially interested to see your deployment of version 0.6, and the natural history schema extensions you had included with your collection objects. Are you defining these extensions yourself, or is it in collaboration with some other similar institutions? I'm asking because we will soon have to investigate a similar schema for fine arts (as well as a local schema) and I'm interested in your experience of this process. > > Regards, > Chris > > Developer, Corpus Project > Statens Museum for Kunst (National Gallery of Denmark) > > -----Oprindelig meddelelse----- > Fra: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] På vegne af Aron Roberts > Sendt: 15. juni 2010 20:54 > Til: Angela Spinazze > Cc: talk@lists.collectionspace.org > Emne: Re: [Talk] Schema Extension and Search in CSpace v1.0 > > Hi Angela, > > In the message "[Talk] Schema Extension and Search in CSpace v1.0", > dated 2010-06-15, Angela Spinazze wrote: > >> During my recent visit to SMK, we talked about the fact that they >> will be extending CSpace schemas to accommodate some SMK-specific >> fields (such as notes). Chris asked about how those fields will be >> accommodated by basic search and advanced search. >> >> In other words, How will fields added as SMK extensions to schemas >> be made available for search? Will these fields be searchable? > > Yes. > >> If so, how? > > A quick test verified that, in the University & Jepson Herbaria > (UCJEPS) instance of CollectionSpace - which is running release 0.6 - > at least for keyword / full text searching, fields added via > extension schema are searchable (below). > > Others may wish to comment on whether these fields can or will also > be made searchable via other means, such as via 'Advanced Search.' > > Aron > > P.S. This UCJEPS instance was used as an example, because it has an > extensive set of custom fields in an extension schema. > > -- > > 1. Retrieve this record via the UI: > > http://ucjeps.collectionspace.org:8180/cspace-ui/html/objects.html?csid=f7137ff0-81ee-4d0c-a802 > > 2. Note the value of the "Field Location Verbatum" field - that it > contains the word "Rockefeller": > > "On the east side of Rockefeller Road, at the intersection of Bald > Rock Road and Rockefeller Road, about 13 miles (air) northeast of > Oroville" > > 3. Retrieve this record via the CollectionObject service: > > curl -u test@collectionspace.org:testtest > http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects/f7137ff0-81ee-4d0c-a802 > > Note that in the record returned in the response, the corresponding > field (to "Field Location Verbatum"), fieldLocPlace, is within a > 'collectionobjects_naturalhistory' extension schema: > > --2ed55496-92f0-464a-822f-b4b20e8782ec > label: collectionobjects_naturalhistory > Content-Type: application/xml > > <?xml version="1.0" encoding="UTF-8"?> > <ns2:collectionobjects_naturalhistory > xmlns:ns2="http://collectionspace.org/services/collectionobject/domain/naturalhistory" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://collectionspace.org/services/collectionobject/domain/naturalhistory > http://collectionspace.org/services/collectionobject/domain/collectionobjects_naturalhistory.xsd"> > <fieldLocLongDecimal>-121.37944793701172</fieldLocLongDecimal> > <fieldLocLatDecimal>39.664169311523438</fieldLocLatDecimal> > ... > <fieldLocPlace>On the east side of Rockefeller Road, at the > intersection of Bald Rock Road and Rockefeller Road, about 13 miles > (air) northeast of Oroville</fieldLocPlace> > <fieldCollectionDateLatest>Jun 12, 2007</fieldCollectionDateLatest> > <fieldLocElevation>3320 ft</fieldLocElevation> > ... > </ns2:collectionobjects_naturalhistory> > > --2ed55496-92f0-464a-822f-b4b20e8782ec > label: collectionobjects_common > Content-Type: application/xml > > <?xml version="1.0" encoding="UTF-8"?> > <ns2:collectionobjects_common > xmlns:ns2="http://collectionspace.org/services/collectionobject" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://collectionspace.org/services/collectionobject > http://services.collectionspace.org/collectionobject/collectionobjects_common.xsd"> > <otherNumberType>collector number</otherNumberType> > <otherNumber>14081</otherNumber> > <responsibleDepartments/> > <objectNumber>JEPS113857</objectNumber> > <title>Juncus tenuis Willd.</title> > ... > </ns2:collectionobjects_common> > > --2ed55496-92f0-464a-822f-b4b20e8782ec-- > > 4. Perform a search on the keyword "Rockefeller" in the > CollectionObject service: > > curl -u test@collectionspace.org:testtest > http://ucjeps.collectionspace.org:8180/cspace-services/collectionobjects?kw=rockefeller > > Note that the record returned has the same object number, JEPS113857, > and the same CollectionSpace ID (CSID), f7137ff0-81ee-4d0c-a802, as > the record above: > > <?xml version="1.0" encoding="UTF-8" > standalone="yes"?><ns2:collectionobjects-common-list > xmlns:ns2="http://collectionspace.org/services/collectionobject" > xmlns:ns3="http://collectionspace.org/services/jaxb"><pageNum>0</pageNum><pageSize>40</pageSize><itemsInPage>1</itemsInPage><totalItems>1</totalItems><collection-object-list-item><objectNumber>JEPS113857</objectNumber><title>Juncus > tenuis > Willd.</title><uri>/collectionobjects/f7137ff0-81ee-4d0c-a802</uri><csid>f7137ff0-81ee-4d0c-a802</csid></collection-object-list-item></ns2:collectionobjects-common-list> > > 5. Perform a search on the keyword "Rockefeller" in the UI: > > Enter "Rockefeller" into the "Search" box at top left. Keep the > original drop-down menu selection to its left at "Object". Click > "Search". > > One record is returned, matching the record above: > > ID Number Summary Type > JEPS113857 Juncus tenuis Willd. objects > > _______________________________________________ > 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
Empathy v1.0   2025 ©emwd.com
Documentation