mindex

Posted by Julie Hart on 16/10/2006 15:16

Hi
Our video mindex is based on the format of items, however it seems not every item with the correct format is being included, I raised a call about this but not sure why it is happening. What I want to do now is find out which items have the correct format but aren't included in the mindex. I thought perhaps if I could find out the control numbers of works that have items attached with format VC, DD or DV and then get the control numbers of works included in the Mindex then I cross reference these and discover which works aren't being included and then I could dummy edit the works so they go through update daily access points and Ta Da!
Does anyone know how I would get the control numbers or another way of acheiving what I want to do?
Any suggestions gratefully received

mindex

The SQL for the video collection is very straight forward

select WORK_ID from ITEM
where FORMAT_ID in ("VC","DV","DD")
and WORK_ID=@work_id

So to find all the works with items that match the format you would need to run a similar piece of SQL.

However you mention that there are items that you know are not appearing. Have you passed the control number of these items through the test option in the manage_collection script? This script will list the collections that a work will appear in based on the collection select criteria.

If the works appear in the video collection when tested in manage_collection and they appear in the OPAC when the work is dummy edited the issue may be that the items are not being processed by update_daily_access_points. The update_daily_access_points script looks at works that have had rows added to the WORK_UPDATE table since the last run of the update_daily_access_points script. A row will go into the WORK_UPDATE table when a work is edited but if the item is modified then a row goes into the ITEM_UPDATE table. Changing the format of an item is not going to insert a row in WORK_UPDATE.

The update_daily_access_points script does not look at the ITEM_UPDATE table so a script needs to be run beforehand, itu_update_wku.pl which takes rows from the ITEM_UPDATE table and inserts rows in the WORK_UPDATE table to be processed by update_daily_access_points.

The itu_update_wku.pl script must be running if you have item based selection criteria for your mindexes. Be aware if you haven't run the script before it will start processing from the first row in the ITEM_UPDATE table and it may take some time to catch up. It is probably advisable to insert a row into the UTILITY_LOG table as as a one-off job to force it to run from the current date so at least all future item changes are picked up.

insert into UTILITY_LOG
(SCRIPT_NAME,
INPUT_FILENAME,
LAST_PROCESSED,
LAST_DATE,
COMPLETED_FLAG)
values
('itu_update_wku',
'ITEM_UPDATE',
0,
getdate(),
'F')

I would test this SQL and the itu_update_wku.pl script on the MIS server first. You should also be compressing the ITEM_UPDATE table using itu_compress.pl if you are not already doing so.

However the best way to ensure that all the works are processed is to run a full access points rebuild if possible. While a big job it may be less involved than trying to pick out the "missing" works.

Thanks

Brian Crampton
Developer, Talis

You are a star Brian! Many

You are a star Brian! Many thanks.