The magic bullet holes the French made in Alicante

Well, as many of us know it doesn’t exist! This was part of my opening speech for the XV Jornadas de la Conferencia de Archiveros de las Universidades Españolas. This is the annual meeting of all Spanish university archivists. I spoke about “El perfil del archivero en el entorno digital”, or “the profile of the archivist in the digital world”. Most universities in Spain have an archivist, who also performs the role of records manager. Records manager as a profession doesn’t exist in Spain. Repositories existed in almost all universities but were on the whole in the libraries and not within the archives. There is a big divide between librarians and archivists in Spain also so not a great deal of exchange goes on between these sectors. Many questions concerned costs as well as approaches to preservation. An excellent book has been written in Spanish about digital preservation by Jordi Serra of the University of Barcelona, “Gestión de los documentos digitales: estrategias para su conservación” =” Electronic records management: strategies for long term preservation”.

A lot of discussion revolved around the struggle to convince the superiors in the organization of the importance of digial preservation; a lot of discussion about how access drives so much of what is going on, also the big problem of engaging our techy friends in the area of digital preservation and making them aware of the issue. The biggest universities such as Complutense and UNED (Universidad Nacional de Educación a Distancia.) were of course represented. UNED is the UK equivalent of the Open University with braches all over the world and is based in Madrid. A lot of discussion also took place about the involvement of non-anglo saxon countries in international fora such as ISO panels and ICA. While all these endeavours are important a certain amount of frustration is evident in relation to decision making and power!

Much talk and walking through the historical centre of Alicante, and in the interests of professional scholarship and in keeping with traditional Spanish culture I stayed awake until 3am catching the plane home the next day to rainy London.

Some of us at ULCC, and over 100 other people from around the UK, spent a couple of days this week at the Aston Business School reviewing the outcomes of JISC’s repositories and preservation programme and looking forward to what comes next. It was a useful and stimulating couple of days – the best programme meeting I’ve attended so far. The few projects that weren’t represented at the meeting missed out in a lot of ways. If you’re involved in a JISC project, make sure you, your project manager, or both of you go to a programme meeting when you are invited. You’ll learn a lot, make some useful contacts, save some time, get some useful ideas and possibly lay the groundwork for future projects or collaborations.

I began the day by chairing the final meeting of RPAG(the repositories and preservation advisory group.) We had a short meeting mainly to follow up on discussions we had been having on how the group had operated and how JISC might make use of advisory bodies in future. Those who expressed an opinion all felt it had been useful to them, but we all had concerns about how our time, and the JISC Executive’s time, might have been used more effectively. Future advisory groups may try to split responsibility for some areas into smaller working groups. All were agreed that the face-to-face meetings were invaluable, but we weren’t all agreed on which online technology would be best to use in between times. Enthusiasts for tools like ideascale were matched by those who found them unusable.

The meeting proper opened with some background and perspective from Rachel Bruce and Neil Grindley of JISC and myself. I tried – partly seriously, but without much expectation of accuracy – to give a one-line summary of what each project set out to do. But there were two things I meant to say which I failed to do. One was to look forward to the theme of day 2 (Value) and stress that repositories are not ends in themselves, but need to be thought of in terms of value, impact and benefits to someone. The second point I omitted was to remind us that , for innovation projects, failure in one sense can still mean success, as long as we understand the nature of the failure and are able to use it to improve and adapt future work. Not achieving what you set out to do is disappointing. Analysing the reasons for that and making sure others are aware of them can be of great value.

But it was the rest of the event that provided greatest interest. The discussion sessions on text mining, research data, teaching and learning repositories and more; presentations from projects from stakeholder, developer and other perspectives; posters and demos from many of the projects; and the fever of activities in the ideas room, which deployed technology ranging from post-it notes upwards to catalyse, capture and refine ideas from the attendees. These activities gave the event much more of a participatory feel – everyone became a contributor rather than being a consumer.

I learned a few things over the course of a day or two, most of them unexpected. David Flanders (via Chris Rusbridge) passed on the neat idea of feeding funding proposals through Wordle before marking them. That’s what ULCC’s AIDA project looked like. Perhaps you ought to try the same with your proposals prior to submitting them?

I learned that talking unprepared and unscripted to a video camera doesn’t produce great results unless you’ve had practice or training – neither of which I’ve had. I knew that in an abstract sense and now have the unfortunate experience to back it up. But Andy McGregor and Dave Flanders did capture some other people talking far more sense than I did and far more clearly, and you can see the results on the dev8D youtube channel.

Andrew Prescott’s overview of the Welsh Repository Network provided us with the surprising finding that smaller institutions are more, not less, likely to want to run their own repository rather than contract it out to someone else.

And via a serendipitous typo, we all contemplated whether working in a repositoire might not be an altogether more rarified and sophisticated career option than working with a repository.

What’s prompted me to write about it now is the news that the outputs from that workshop are now visible, and the ongoing process of revising and amending them is taking place in a far more public forum on pbwiki. repinf.pbwiki.com is somewhere you should visit if you are, in the words of its homepage:

…. interested in:

1. developing coordinated action plans for specific areas of repository development

2. pursuing those plans

3. coordinating that activity internationally

An international workshop in March 2009 kicked off this process, which is now open to anyone willing to contribute.

If you have an opinion on things like interoperable identifiers, citation services, streamlining deposit workflows or (most contentiously) international repository organisations, you need to take a look at these materials. The workshop that produced them was a curious and mixed event, but it certainly had some positive features. It brought together interested experts from around the world to consider things that need doing with repositories that can only happen through joined-up international action. We did our best to focus on things that could be done in a reasonable timescale and that would produce clear benefits. At the end a group of funders – many of whom clearly weren’t quite sure what was expected of them – spent an hour or two considering the ideas that came out of the 4 workshop groups and voiced their own opinions about them. Some of the ideas drew widespread support from public and commercial organisations, whilst others were not yet clearly developed enough, or were still too parochial. Generally, there was a clear willingness to take action, but some of the plans needed more work before funders could act. The wiki is the way that that work will be done (with the contentious exception noted above.)

The idea of getting joined-up thinking between doers, thinkers and funders has succeeded. Anyone can read the material on the repinf wiki site, and anyone can edit it once they ask for a userid. Do it. Do it now.

The opening paper, however, was in its own session as it won the prize for best paper of the conference: Manjula Patel and Alexander Ball’s study on the issues surrounding the preservation of engineering CAD models was a useful guide to the problems and to possible solutions. One of the things that they opened my eyes to is that CAD files aren’t just about geometry and spatial representation – there’s lots of other information possibly embedded in them or attached to them, from engineering tolerances to feedback from the manufacturing process or field maintenance.

Aaron Griffiths then spoke about the RIN report looking at attitudes to data publishing across different disciplines (To Share or Not To Share: Publication and quality assurance of research data outputs) It examined culture, infrastructure barriers, the effects of policy and overall propensity for sharing across a number of disciplines via interviews with researchers: astronomy was generally high (that is, well disposed towards sharing), social and health sciences low, for instance. Motivations included altruism and opportunities for collaboration; constraints included time, legal and ethical, competition, sense of limited rewards, and nowhere to put stuff. The report says we need incentives: evidence of benefits, standard workable mechanisms for citation, more explicit rewards that affect career progression. It also looked at issues around discovery, access and usability. and then asked researchers about processes relating to quality assurance. This didn’t get support from the researchers they spoke to, but we can’t have greater rewards for data publishing without a willingness to have QA, I feel. His presentation made it clear to me that I ought to read the report.

Amanda spencer then spoke about TNA’s web continuity project, which aims to ensure (eventually) that 404 errors on UK government websites will be a thing of the past. One detail that was new to me (we’ve covered much of this in the PoWR project) was that the TNA team followed up their original study of link persistence in Hansard answers (which found that 60% of the 4,000 URLs given in answers to parliamentary questions over the last 10 years no longer worked) with a more wide-ranging study of government sites using google webmaster tools. They wanted to check to see if PQ answers were in some way a special case: they weren’t. They are promoting the use of XML sitemaps to help in capture but these also help search engines and therefore current use of the sites.

Ronald Jantz then spoke of ideas around institutional support for authentic digital objects, starting with the assumption that “digital scholarship requies authentic digital objects”. An example he gave in support of this (attempts to recreate cold fusion experiment failed because experimental design – including location of thermometer – wasn’t available) was interesting but didn’t seem directly relevant to questions of authenticity but rather of selection or completeness. He reminded us of the useful distinction made in archival diplomatics between authenticity and reliability, but ended up proposing that the solution to the authenticity question depended on institutionally-supported key signing, together with some process like TRAC to authenticate the institution and/or its repository. I and others weren’t convinced by this argument, nor of its novelty. The issue of keys and what they attest was being dealt with at the time of the second DLM forum in 1999 by the Swedish National Archives, amongst others. Using keys to place the equivalent of wax seals on documents isn’t difficult; the complex problem is whether the trust networks exist to make the keys useful to anyone.

A presentation about the curation of weather data at NCAR provided lots of numbers and some interesting new terminology. ‘Enriched staff’ who have subject knowledge of the data they are curating. NCAR storage requirements double every 2.5 years, and are now about 6 Petabytes. A new phrase for what I think of as media refreshing – moving data between storage media without necessarily changing the format of the data – was ‘tape oozing’. This is still something that requires significant planning and coordination for large data centres to ensure that data can be moved before media become obsolete and without interfering with day-to-day access needs. NCAR’s observation is that poor curation causes more incidents of data loss than equipment failure or media failure. ‘Poor curation’ can mean both bad practice and the failure to follow established good practice. (This is true of many areas of activity, from healthcare to manufacturing, and quality management systems like ISO9000 are designed to minimise both causes of error, but they will never eliminate it.)

Mackenzie Smith then gave the day’s second paper on CAD, specifically in architecture. A fascinating collaboration with MIT’s architecture school looked at well-known achitectes like Gehry, Thom Mayne and Moshe Safdie. Data is a 3D CAD model (known as BIM – building information model) – which moves from architects to builders to owners. Targer audiences are practitioners, historians, instructors and the public. The practitioners already know they jhave a problem managing the data, so are incentivised. 10,000s of files, 100+ file formats, many gigabytes, almost no metadata: just filesystems, sometimes with spreadsheets in them that are like partial catalogues. The MIT project buildt a gui to help in automating assigning 5 properties to every file: when, where, how, why, what. “How” is generic type, such as presentation; “what” is specific format; “when” is to do with building phase rather than absolute time. Importamt stuff gets extra tags: models tell you what was built, but not why. MIT are archiving by creating 3 derivatives, all of which lack something. (STEP,dessicated shape, and web display.) One problem is that geometry is not authentic, but practiioners say much parametric stuff is tool artefact, not design intent. CAD vendors are very resistant on releasing format information. The project is exploring escrow solutions for this, which sounds like a pragmatic way forward.

In the afternoon, Stephen Abrams began with the statement that “Preservation is not a place” and went on to a wide-ranging reflection on the nature and role of repositories in a way that has relevance for many other institutions and services. Starting from first principles, Abrams’ group worked from values to services, reimagining the repository as a process, not a place (still a work in progress.) They went back to Raganathans 5 laws and also looked at archival science, particularly concerns over provenance and its importance in supporting authenticity. They identified 10 properties which they think apply to all objects (identity, viability, visibility are some.) But curation depends on a lot of human things: competency, deicsion making, analysis. They identify 13 minimal services that suppport the human endeavours: these include identity services (ark and noid), storage (pairtree), fixity/replication (ACE), catalog (relational or rdf/xml database), characterization (jhove2), transformation (at ingest, preservation dessication/migration, and use copy generation), ingest (bagit/grabit), request – metadata-based search and browse, search (lucene), publication (sitemap,rss/atom,oai-pmh), annotation (social tagging,oai-ore). Any one of those would have made an interesting paper in itself, and some of them were the subject of separate posters. He ended by thinking how simple can a curation environment be and still be effective? And also took the concept of LOCKSS a little bit further: lots of description keeps stuff meaningful, services keep stuff useful, use keeps stuff valuable.

Finally Malcolm Atkinson gave a stirring speech which began with thoughts of scientists who still go out once a month to count birds or moss species – trained volunteers are important as well as industrialised scientists. Data can have uses not envisaged when it was created nor even when it was first preserved: ships logs’ original purpose was safety. They were collected by archives to understand trade, and are now helping climate modelling because of their detailed records of such things as temperature and wind. Soon power will cost more than hardware. 1pb consumes 2.2mwh in 5 years. He talked of ‘data huggers’ who avoid competition, don’t describe, don’t expose, don’t share their data. There are also good data sharers, but at the moment incentives and disincentives aren’t well balanced. We need research on how to enable better research and data must be fundamental to this.

IDCC has been over-subscribed for 3 of its years and always offers lots of inspiration and food for thought. The linkup with CODATA, whose events cover a similar subject area, can only be a good thing. I’m already looking forward to IDCC5, expected to be in London in 2009.

John is working on the Science Commons initiative which, through projects and advocacy, is taking the Creative Commons concepts and applying them to the doing of science, as well as the publishing of its outputs. (The DCC were drawing our attention to the initiative over 3 years ago.) He began with a view[1] that science is not unlike wikipedia: they are about publishing, in the sense of disclosure, advances are made by individual action and proceed by small, discrete steps, and trust ratings accrue from peer review. He also commented on the “tyranny of the crowd” effect that general search tools like Google suffer from: someone searching for information about spears (their manufacture, use, or “spears, the carrying and chucking of”) will be somewhat overwhelmed by the number of results relating to Britney. And from this he moved to a view that science, to advance further, requires a disruptive change to its practices that it is inherently resistant to. One thing that needs to change is the notion that science is communicated through periodic papers (itself an outdated metaphor), “units of knowledge which are adverts for years of work.” He observed that, even if we still want papers, we really want them with embedded (ideally semantic) linking and tagging. Yet, although we have the technology to do this in a semi-automated way, the licenses that apply to many e-journals explicitly prevent us from doing so.

He then moved to considering ways to improve openness of journals and their content: by giving incentives such as better statistics to those who publish in open journals, and through simple but effective tools such as the scholar’s copyright and addendum tool, a really simple idea which impressed me: something which automatically adds text to a publisher’s licence from a closed journal which gives the author the necessary rights to self-publish (and hence link and annotate) their work. He demonstrated the effect of linking and the power of the semantic web through a google search on particular receptors in brain chemistry and the genes which relate to them. A google search, despite highly specific language, returned 88,400 results, most of which were papers about the receptors. But what the researcher probably wants is a list of genes and evidence for the nature of their relationship (as encoders, regulators, etc.). Their semantic web tools give exactly this, and allow the resultant RDF query to be turned into a simple (if unwieldy) hyperlink. What’s more, they were able to use google maps for brain data in a way that allows it to be annotated; one of those clever, simple ideas that makes you wonder why noone else did it before. As John made clear, one of the reasons is that the data isn’t sufficiently open.

He argued strongly that, for open science data to realise its potential, we must abandon the notion of requiring attribution and/or citation because it places too great a burden on those combining data from multiple sources. He’s doing pilot work on open data in science commons with charities funding work on rare brain diseases: the sort of thing in which the ability to link scattered data, often from other areas of research, hugely amplifies the value of the original research funding. Working with google, they’ve come to the realisation that typical data mashups or search results might involve 40,000 invididual citations if all the data sources ar taken into account. For Google that’s a burden they’re not willing to deal with. So John is arguing strongly that we should abandon the desire to have databases, or cells in databases, attributable. It was a powerful argument, although I’m concerned that it shouldn’t be forgotten that we often still need the ability to determine data provenance, sometimes at the level of an individual value in a database cell, to ensure that we know we’re comparing like with like, or applying an appropriate statistical technique. And the provenance information is often tied up with the citation information. Still, John’s argument, and that of the science commons, seems very persuasive: huge benefits can be gained from making data completely open (as in public domain) and we will not realise those benefits if we cling to attribution or citation. He also made that point that although data growth is exponential, our brain capacity remains constant, and that the only human factor increasing along with data is population. People-driven annotation and sharing therefore helps us process increasing volumes of information (I think.)

Cameron Neylon has also written about John’s talk and that crucial distinction between attribution and citation. (His blog post also contains a link to his presentation from Tuesday morning, which makes a great case for the need to curate networks of science, not digital objects per se. I’m sorry I missed the talk.) John points out that many people confuse the need to attribute with the need to cite; attribution is a legal requirement, bound up with copyright and licences (even in the open world of creative commons) and failure to attribute material puts you legally in the wrong. Citation is merely a social convention or an ethical obligation, something we ought to do; failure to cite leads to the disapproval of your peers and is called plagiarism, at least when you attempt to pass off the ideas of others as your own. And that leads to the conclusion that, for an academic, the consequences of not meeting that social obligation are potentially much worse than the consequences of falling foul of copyright law. The latter may, at worst, lead to a financial penalty which is unpleasant but survivable, whereas plagiarism can lead to the loss of reputation, job and career – despite no laws having been broken.

But that was a minor cororollary of the Science Commons thesis, which appears to be that we have to be willing to really let go of data, in a way that we haven’t done before, to allow science to proceed in a way that permits disruptive, rather than incremental, change.

Tuesday morning saw Martin Lewis, university librarian at Sheffield, look at the role libraries need to play in supporting research. His talk had two threads: one a reflection on how libraries are still agile, capable of change and sensitive to the needs of scolars and learners, and one a summary of the findings and consequences of the UKRDS report, which at present is still in draft. He used new library buildings at Sheffield and Glasgow Calendonian to illustrate that libraries now create very different sorts of spaces for learners and as a result still attract students to congregate there. Capping of collection size is now commonplace – they recognise that most collections cannot continue to consume more space indefinitely. He reflected that UK university libraries had been devoting too much attention to learning and teaching and had, as a result, neglected the needs of researchers. And thus he moved to his assertion that university library services were best placed to meet the needs that the UKRDS feasibility study would identify. Martin says that they can raise awareness of data issues, lead policy on data management, provide advice to researchers early in the data lifecycle, and work with IT services to develop appropriate local capacity.

Martin’s talk was entertaining, informative and well-argued in equal measure, but I am not entirely persuaded by it. University libraries certainly have a place to play here, and in some institutions they may well need to adopt a central role. But just because they can do all of the things that Martin describes does not mean that they are the only people who can, nor that they are the best-placed to do so in every case. His argument put up a number of straw men, one of which seemed to see future RDS provision as a choice between a library-led service and an computing services-led one. It was a cheap dig (“How many university computing services have a ‘friends’ organisation?”) and sets up a false dichotomy. This won’t be a simple either/or choice and there are many other routes to the intended end of a federated shared service of some sort. He emphasised that the UKRDS study was primarily a political act to keep the issue of research data management high on the agenda and that it should be seen in that light. I’m in complete agreement with that, and that’s the very reason I don’t see that it’s useful to engage in a turf war about which part of the university takes this forward.

That takes us to just over halfway at iDCC4, and it’s enough for one blog post. The rest will follow in a day or two, and there’s lots more of interest to write about.

—————————————–

[1] – which he credited to someone else that sounded like Jean-Pierre Galdon, but wasn’t

He began by illustrating the changes in health, disease and knowledge of causes that lie behind some of his work. Changes in scottish demography illustrate this: in 1911 everyone is young, numbers decline with age in a smooth curve. After WWII, in 1951, there is a flat bulge from ages 10 to 50 with a decline thereafter, whereas 2001 and 2031 sees a bulge in pensioners. There is a consequent rise in chronic disease: disease that treatments of today are not very effective for, unlike the killers of the past, where effective treatments contributed to the changes in age profile in the population that we are now seeing. He illustrated this with reference to the grim reapers road map: an atlas of mortality in the UK (and, as he said, a fine book title.) It showed cancer, heart and lung disease unequally distributed over the UK. Glasgow is particularly bad. Why? Nature and nurture both play a part, but other than smoking, we have very little evidence for the real effects underlying nurture causes such as diet variation. So his research concentrates on the nature aspect: what difference our genetic inheritance plays.

He then looked at changes in sequencing costs. From 1990-2003 the human genome project spent $3bn to do the first with machines spread over aircraft hangers; now one machine can do a genome for 500k, in the next year 5k. completegenomics plans 20,000 genomes at $5k each in 2010 using 60,000 processors and 30Pb of storage. One goal of all this is personalised medicine – drugs that work for your genetic makeup. In the USA, adverse drug reaction is 4th leading cause of hospital mortality (but I’m thinking that only some of this is genome-related; some of it must surely be because some drugs are just downright toxic, with prescription involving balanced risk that sometime doesn’t go the way we want, and because prescribing errors are still all too frequent.) Bringing together mass genomics and automated drug screening is key, involves two big sets of data. Generation Scotland plans to do this: a competitive advantage is an unhealthy, stable population. Large scale family-based studies possible, supportive attitude in Scotland to doctors and medical schools. Expertise in health informatics and ethical, legal, social science essential. It’s all volunteer-based (striking contrast to Iceland and UK genome bank); grandmothers are key influencers. Recruits have blood, serum and uurine samples and tests of lung, bone, etc. and mental health status, so it’s more than just aggregating health records. Mental health is one where drugs generally don’t work and interaction between nature, nurture, aetiology and drugs needs to be explored in much more depth. System is linked to medical records; subjects have right to withdraw.

10 years of consultation before it started. but then there’s google health and google health trends – both ways of using large amounts of data to gain knowledge which work in different ways.

I missed the next morning sessions because I had to attend another meeting, and rejoined to see the minute-madness presentations for the posters, about which I hope to write later this week.

After lunch we had Dr Bryan Lawrence of STFC talk about big science data curation at the STFC environmental data archive. There were lots of numbers in this presentation and I only capture some of them: petabytes of data overall, 50TB from met office, 4000 years work to ‘look’ at it all. That’s why you need metadata, because you can’t examine it all at ingest. 2 minutes to find and do something simple: 60,000 images/year/person. So need to automate metadata creation and extraction. Google needs this metadata to help; it can’t deal with non-cited data directly. Most data mining processes text, not image data. We find data with discovery and ontology metadata; then look at context, character and discipline stuff; then also archival metadata. He mentions ISO 19115, should be derived from browse metadata. (There was a much more formal classification of metadata in his presentation which I haven’t captured in these notes.)

Data scientists can’t do their job unless the scientist has done theirs. They can choose not to take stuff, though, because the scientist hasn’t done their job. But even not taking something consumes resources to make the assessment and decision. Makes point that you can automate streams, but you can’t automate jobs away (10 things still need to be done, even if they are automated, so there’s still a linear resource relationship to the number of objects.)

A charge for 3 years storage up-front at ingest time which if volumes continue to grow, historical data storage lives on the margins from current business. Core budget pays for management and access systems , data management, network access, etc. then per data stream costs charged to projects. Core covers some projects already, with 25 FTE can supoport 10 new types of data per year, 100 things of a few hours work, 1000 things of a few minutes work, beyond that it must be automated. Next IGPCC requirements changes scale and thus the cost models. Interesting problems are in browse ontology and extra metadata space. Preserving metadata now presents its own challenges; real data publication is the way forward. In questions we determine that the deluge is necessary for the cost model, as is storage cost reduction. And at the moment it isn’t worth bothering about things to throw away, but that could change if those cost assumptions aren’t true (such as if storage costs plateau at some point.)

Neal Beagrie then speaks about research data costs. 4 case studies, 12 interviews, literature review, detailed look at 2 cost models against OAIS and UKHE TRAC led to the report. Produced a 3-part activity model which supports a cost framework (pre-archive, archive, support services.) There are key cost variables, a resource template. separate economic adjustments from service adjustments. He contrasts repository costs for publications with costs for data repositories, and data from elsewhere about much bigger cost of repairing metadata later on as opposed to doing it right at creation. It looks at efficiency curve effects, economies of scale and problems with first mover costs. He mentions the ADS 20-year rule (that all-time costs of preservation are essentially accounted for in the first 20 years), but points out there are a number of assumptions behind that. Points out usefulness of NSB/NSF distinction between research, community and reference collections. The study is new in using FEC (full economic costs, a UK HE funding model which comes from TRAC – transparent approach to costing (not trustworthy archive certification!)

The study is not just about DIY, can account for partial or full outsourcing. OSI study shows that 1.4% or 1.5% of research funding goes on data preservation and access.

Brian Lavoie talks about economic sustainability, from the blue ribbon task force. Resources aren’t just ‘available’: meaningful engagement is necessary. They need to be comprehensive (or at least a critical mass), actionable and sustainable (hence persistent.) Sustainability is economic, technical and social. Task force supported by NSF, Mellon, LoC, JISC, CLIR, NARA. Mission to frame digital preservation as a sustainable economic activity. Need to articulate benefits and incentives for decision makers (parallels with PoWR and digital preservation policy study.) First gives a willingness to pay, second a willingness to provide.

Need selection and efficiency, and reliable predictability. Then need to choose organisational form and governance. Org may be no interest( 3rd party provider), private interest (university library/archive), statutory/mandate interest (national library/archive). Issues: separating costs of access now vs access in the future. Monetizing public good. He mentions “spend now for future value” which appears to resonate with the DELOS/NSF “Invest to Save” message (in which I must declare an interest.) First report due this month.

At this point my laptop battery gave up the ghost. The final presentation from John Willbanks was a real highlight in many ways, but it will take until tomorrow for me to transcribe my handwritten notes.

Day 1 ended with a conference dinner in the splendid setting of Edinburgh Castle. The harpist was a particularly fine touch.