Re: [VuFind-Tech] Bugs in VuFindIndexer.getFormat?

[Demian K. <dem...@vi...>]

The built-in getFormat function definitely has many flaws...  and people keep talking about replacing it with something better, but I've never gotten a polished submission to use for updating the default distribution.  (Villanova uses a custom routine that gets better results but is not pretty code...  I can send you a copy if you are interested).  This is probably something worth bringing up on a future developers call (once I'm back in the office) -- maybe we can finally make better progress on the issue!

- Demian
________________________________________
From: Servilio Afre Puentes [afr...@mc...]
Sent: Friday, August 12, 2011 12:48 PM
To: VuFind Tech
Cc: Wade Wyckoff
Subject: [VuFind-Tech] Bugs in VuFindIndexer.getFormat?

Hi,

Troubleshooting and issue with journal title searches not including
electronic versions, besides the cause for this other issues were
spotted by my co-worker Wade Wycoff.

Instead of directly creating tickets for these, I would like have a
discussion in the list as the actions might be different in each
case. This way would make it faster and easier to include Wade in the
discussion.

The issues found are:

1. Once a format is identified no further inspection is done, resulting
   in our case caused many journals to be classified as just electronic
   resources.
2. Archival material was classified as a "Kit"
3. Integrated resources were not taken into account
4. Neither were websites

Attached is the diff showing our changes to format.bsh solving these
issues.

Servilio