It was obvious. I did run build_oai_sets.pl Bottom line: a record cannot be in two oai sets that use the same indexed MARC tag. i.e. ... 590 a SET1 590 a SET2 ... This record will be in the oai dataset SET1 but will not be in SET2. Only the first occurrence of the 590a is used to create oai datasets. Steve On 8/25/2014 3:17 AM, Magnus Enger wrote:
Sorry for the late reply!
You did not mention running misc/migration_tools/build_oai_sets.pl. I guess there might be two reasons for that: - you don't know about it - it's so obvious you did not mention it
My apologies if it is the latter. If it is the former, you might want to have a look at the documentation for that script: http://perldoc.koha-community.org/misc/migration_tools/build_oai_sets.html
Best regards, Magnus
On 30 July 2014 17:36, Steve Sowder <sowder@andrews.edu> wrote:
This is what I know.
I have read again the info at http://www.openarchives.org/OAI/openarchivesprotocol.html#Set
It now makes more sense to me.
OAI databases are created with the full records of the database. In our case that is about 190,000 records.
SetSpecs are subsets of the database (for "Selective Harvesting").
Any record can be in zero or more SetSpecs.
In Koha, when an OAI set is defined that new SetSpec will appear in the ListSets. (i.e. http://koha.andrews.edu/cgi-bin/koha/oai.pl?verb=ListSets) without rerunning the program build_oai-set.pl. At least, it appears after overnight.
However, there are still no records (should be 70,000) in either of the SetSpecs. Which is what I don't understand.
The mapping follows the instructions given in the documentation.
So, questions: Is mapping only available to certain MARC tags? Indexed tags only?
For those of you that have SetSpecs with records please send me examples of your set mapping.
Thanks
Steve sowder@andrews.edu
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha