CDS-Invenio: understanding OAI setSpec’s, Collections and phrases
Having trouble with CDS-Invenio oaiarchive or setSpec‘s? Continue reading
First of all I would like to thank CDS Support Team and specially to Samuele Kaplun for their great help and support. Without them my life would be much more complicated. Thanks, guys.
General explanation of CDS-Invenio OAI system
When you define a new OAI set CDS-Invenio’s form has several fields, which I’ll try to explain (from the user point of view). The better way to do this is showing an example.
This is the screen you will see:

The first two fields (setSpec and setName) are the ways to identify your new set. First one is the machine-readable name and the second, the human-readable one. Usually I type the same name in both fields.
In my example I will type ‘public’ in these fields.
The next field is Collection(s). Here you must type the Collection(s) to which belong the records you want to add to the OAI. For instance, I have a collection called “Tesis” so I type “Tesis” in this field. Please note this name is exactly the one displayed in WebSearch admin interface when listing the collections. This is NOT the value you use to define a collection (see images below). From now on I’ll call the first Collection Names and the second Collection Queries.

websearch admin interface – note the “Tesis” collection: this is the Collection Name (the value you must use in field Collection(s))
showing properties for the “Tesis” collection in websearch – note the THE: this is the Collection Query, which is NOT the value you must use
Next fields are Phrases. I was wondering how this Phrases and collections were evaluated. This is the way it works:
1) the union of the Collection(s) you specified is taken (let’s call it A).
2) on this you apply the (at most) three condition reading them from left to right. So e.g. if you have “X and Y or Z” phrase‘s, all the records from A that match X are intersected with all the records from A that match Y. Then this is united with all the records from A that match Z.
Tip’s
1) If you want to add a phrase which involves a concrete field (ie:984) you should make sure it is already defined. To do this refer to: http://yourURLToCDSINVENIO/admin/bibindex/bibindexadmin.py/field. If it is not defined there, add the definition.
2) If you want to add a phrase which involves collections you should use the ‘Collection Query’. This is, in this case I would use “THE” instead of “Tesis”, as “Tesis” collection is defined like collection:THE (refer to previous section for further explanation).
An example: defining OAI set as a union of definitions with the same setSpec
Let’s suppose you want to define a OAI set, called ‘public’, which involves Collection (names) A,B,C and only some of the records in collection (name) D, this is an OAI set is defined as a union of definitions. The records belonging to collection D must be included only if the 984a field contains exactly the word “public”.
What you can actually do is:
(i) define a first “public” setSpec with:
Collection(s): A,B,C
(ii) define a second “public” setSpec with:
Collection(s): D
Phrase: public 984__% Exact phrase
That’s it!
If you notice any errors or still have any doubts, please leave a comment.
Related posts:
