Called the ‘Knowledge Bank’ – is DSpace. Content is defined by ‘institution’ – but different types of content:<\/p>\n
Knowledge Bank pushes out to other sources – e.g. ScientificCommons.org, OAISter<\/p>\n
They created a Metadata Application Profile for the KnowledgeBank, using core set of metadata elements and DC Metadate Element Set – available from KnowledgeBank website<\/p>\n
Question – does the metadata make sense when it is outside the institutional context? Example of a library newsletter – makes sense in the KnowledgeBank because it exists in a hierarchy (not sure, but I guess by collections?), so they didn’t in the firstplace bother replicating this information in the record. However, then when taken out of that hierarchy and put into OAISter (for example) – without that hierarchy information, it was impossible to tell what it was.<\/p>\n
They decided to add the relevant information back into the record (this seems really wasteful – it should have been done surely at a system level – should have been possible to automate the integration of the hierarchy information into the record without having to rekey)<\/p>\n
Mentioning problems of authority control – lots of people contributing etc – so many variations in author names, and in subjects etc. They are doing a project to clean this up for a single collection at the moment<\/p>\n
Saying that people often add keywords that are already in the title, so they don’t add information (although I’d argue that it does add information – this kind of thing could be used to help relevancy surely?)<\/p>\n
They have setup a ‘Community Metadata Application Profile’ – which is shared with all who submit material into the repository. She is showing some details on the slides, but I can’t read it.<\/p>\n
They have Customized Item Metadata display at a collection level. Also customize collection display – e.g. for journal collections, they have a ‘Table of Contents’ display which can be browsed from an ‘issue’ record.<\/p>\n
They have License Agreement in place, with an optional Creative Commons license – done each time someone submits. When submission is done by a proxy, the individual signs a permission to allow this – which is then attached to the item, though suppressed from public view.<\/p>\n
There are customized input forms for submission – again at Collection level. Can also do customized input templates with prepopulated metadata fields for repeated information.<\/p>\n
There are Item Submission Workflows – example of the speakers workflow areas – can approve\/reject\/or push back into the pool of work.<\/p>\n
Talking about batch loading of items – using (for e.g.) a spreadsheet to create the data (cols of DC data) – creates an XML file, which then loaded in batch. Using a spreadsheet means no new interface to learn for people not working with the KnowledgeBank everyday. (I’d personally prefer to see a repository that was easy to use, so this wasn’t a problem)<\/p>\n
They also repurpose MARC metadata for things that may have already been catalogued in a Library catalogue systems – transforming it into DC and loading into the KnowledgeBank.<\/p>\n