I've just got my hands on another arts and humanities data set. This one's smaller than most of the others I've been looking at, and it's been put together in an MS Access application. Fortunately, the owners are aware that that's not a maintainable approach, and want a method of publishing it on the Web. Also, rather nicely, they've been aware of a number of data issues, such as regularisation of text fields: they've partially normalised the data, and effectively have a good ontology for their data.
Sadly, it's not all rosy:
Earlier this month I took part in a workshop:The Influence and Impact of Web 2.0 on Various Applications, at the Edinburgh e-Science Institute (eSI) this event was part of a thematic programme looking at
The Influence and Impact of Web 2.0 on e-Research Infrastructure, Applications and Users.
One of the major problems with building a distributed system is that it's distributed. This means that the parts of the system need to talk to each other. Of course, these days, networks are viewed by most large network operators (e.g. universities) as hostile environments, where anything even remotely risky is split out, preferably into its own little subnet.
Today I presented at the e-Science Institute in Edinburgh event "The Influence and Impact of Web 2.0 on Various Applications". Following that an attendee pointed me towards ICST (The Institute for Computer Sciences, Social Informatics and Telecommunications Engineering) http://icst.org and their MyBoard project http://icst.org/myboard/ which has some overlapping aims with LinkSphere.
A Brief introduction to one of the UCLDH projects
I’m the research assistant (Claire Ross) on project LinkSphere, which is a joint research project with the University of Reading , funded by the JISC Virtual Research Environment 3 programme. The project is aiming to develop a virtual research environment (VRE) which will allow cross-repository searching across [...]
When we started this project many moons ago, we started with 10 identified repositories that we wanted to work with. Of those, two were new systems, being planned or put in. And therein lies the rub… It's hard to write and test code against something that doesn't exist yet (or which is partly set-up and has little data in it). It's even harder to do when the configuration changes under you as they modify their testbed.
Twitter is everywhere. It is one of the key web 2.0 applications that grown hugely in the last year and is now being is being used by everyone and anyone. But does it have any use in academia? Or is it just narcissistic twaddle?
Last year I attended the excellent Museums and [...]
After a project meeting today, it was suggested that I keep a note of all of the "interesting" issues that I encounter with the various data repositories I encounter on the project. So, here's the first of them.