
In addition to the user tests, we have also run some dissemination activities, such as meetings and demos with interested parties. We recently had a meeting with some people in the Social Sciences division. They are working on a divisional system which will cover areas such as teaching, HR and research within their division. Most of our conversation focused on the nature of the data harvested. We discussed if the aggregation of data in the registry and the Blue Pages could change their original nature and intentions. We also talked about how the Blue Pages will make these data, which is already publicly available, more visible. The Blue Pages will enhance all the positive aspects of research within the University. However it will also make some data problems more obvious. Social Sciences participants realised that some inconsistencies could be made more obvious in the Blue Pages. As for example, wrong names or affiliations. Correcting these inconsistencies is of course not a task for BRII but for the people responsible of the original sources. However BRII can potentially help them by letting them know where these problems are, e.g. Blue Pages users can report errors in data.
We have also been working on a new Graduate Opportunities website for the Medical Sciences division. This is a second planned output of BRII. Anne Bowtell is in charge of this. She is using the BRII API and data from the registry to populate this website. These are the data Anusha is harvesting from Medical Sciences sources which of course will also be available from the Blue Pages.
On a different matter, in a couple of weeks I will attend the next JISC Innovation Exchange event. This will take place in Birmingham. One of the main events will be a kind of trade fair where we will have to sell to and buy products from other JISC Institutional Innovation projects. This sounds exciting! Now I need to think on how to sell our BRII products and need to get some updates of the status of other projects so I know in advance what will be on offer then. Print this post
No comments:
Post a Comment