Methods of Populating BibApp Researcher Pages, Reverse population of BibApp with the contents of a repository
Presented by Michael GUTHRIE
Session: Posters session
Track: Poster Session
BibApp is Open Repository's new Enhanced Researcher Pages. It serves as a web based central destination for showcasing an institution's researchers and their associated published works, as well as highlighting collaborations among an institution's researchers. Context with an Institutional Repository (IR) BibApp currently integrates with an IR by being able to discover the location of a full text article digital asset and then push it into an IR by way of SWORD. New Features Populating BibApp The methods for populating BibApp can be cumbersome in that they require adding people or works one by one to the application. What is desired is to allow the population of BibApp by a reverse mechanism whereby BibApp can be populated by the IR in a variety of methods: 1. Batch process 2. Singly 3. Listening for new items in the IR Batch Process As is often the case, when BibApp is first set up the IR is already populated with perhaps thousands of items. It would be highly desirable that BibApp could be populated in a batch process method. Questions and ideas: • What if some of the items in the IR were not necessarily works of researchers? • What if some of the researchers that authored items in the IR were no longer working or part of the institution? Would these people be represented in BibApp? • Perhaps an “alumni” group could be in BibApp. • A lookup could be done by the reverse population mechanism that checks to see if a person is part of the BibApp and if so then attributes an article that has them as an author in the metadata to their listing in BibApp. This mechanism would have to check against all listed authors in the item's IR metadata. Singly When logged into the IR, as an admin, it would be desirable that a single item could have a button that would say “Add to BibApp”. The mechanism would check for the authors and check to see if the item already existed for any of them, and if not, would attribute it to the and add the item to BibApp and the authors listing there. If the author did not exist, a sub workflow process could be performed to allow adding the author to BibApp, or at the very least and in the short term, notify the admin that the person does not exist in BibApp and would need to be added first, and provide a link to BibApp. Listening for new items in the IR When an item is deposited into an IR, BibApp needs to be able to be populated with that item. In this regard, the Work needs to be Added and Attributed to an Author, or at least added to the Verification workflow. The purpose of this poster will be to demonstrate both the methods of populating BibApp as they currently are and also the innovation of populating BibApp in reverse, with the contents of a repository.