Using the search interface (or interfaces) to search the repository for different types of content.
December 17, 2008 Leave a comment
The search interface – http://repository.leedsmet.ac.uk/main/index.php – is now returning results in a manner appropriate to published, peer reviewed research papers which is fine as far as it goes but what about other types of content that we may want to expose externally? I was already dimly aware of the issue with respect to conference papers, for example, which will require slightly different metadata within intraLibrary and which will then need to be formatted appropriately when returned by the search interface. However, the issue was thrown into relief at a preliminary meeting yesterday to discuss using the repository for heritage photographs and other digitised content from the library archives and special collections which will require entirely different metadata.
After the meeting I promptly defined a new collection and uploaded a photo with minimal metadata – just title and description, not even bothering with classification at this stage, I’ve also exposed the collection to external search so it is being returned by the search interface which is obviously trying to format according to Mike’s research metadata template which is frankly gobbledegook.
So…I need to establish whether we can identify different types of content (probably by collection or by an appropriate metadata field) such that, say, the search interface ONLY returns research papers, then if photos are in their own collection can we filter out that collection so that it will not be returned by http://repository.leedsmet.ac.uk/main/index.php at all i.e they won’t be returned by any keywords in the metadata etc? Then we could, say, implement a second interface configured to search the ‘Heritage photos’ collection only and return results in an appropriate format i.e it would not return any research results as those collections would be filtered out?
OR might we want to search the whole repository from a single interface and could we perhaps apply different templates to different types of resource from a common interface? (My initial reaction is that separate interfaces would be better.)
So I’m hoping Mike will tell me this is dead easy and not impossible!