Overview of content related to 'sharepoint'

The ARK Project: Analysing Raptor at Kent

lisrw — Tue, 04 Dec 2012 17:21:49 +0000

Leo Lyons describes how University of Kent librarians are benefitting from Raptor's ability to produce e-resource usage statistics and charts.

It is indisputable that the use of e-resources in university libraries has increased exponentially over the last decade and there would be little disagreement with a prediction that usage is set to continue to increase for the foreseeable future. The majority of students both at undergraduate and post-graduate level now come from a background where online access is the de facto standard.

23rd International CODATA Conference

lisrw — Sat, 15 Dec 2012 12:41:16 +0000

Alex Ball reports on a conference on ‘Open Data and Information for a Changing Planet’ held by the International Council for Science’s Committee on Data for Science and Technology (CODATA) at Academia Sinica, Taipei, Taiwan on 28–31 October 2012.

CODATA was formed by the International Council for Science (ICSU) in 1966 to co-ordinate and harmonise the use of data in science and technology. One of its very earliest decisions was to hold a conference every two years at which new developments could be reported. The first conference was held in Germany in 1968, and over the following years it would be held in 15 different countries across 4 continents.

Hydra UK: Flexible Repository Solutions to Meet Varied Needs

lisrw — Thu, 13 Dec 2012 19:24:07 +0000

Chris Awre reports on the Hydra UK event held on 22 November 2012 at the Library of the London School of Economics.

Hydra, as described in the opening presentation of this event, is a project initiated in 2008 by the University of Hull, Stanford University, University of Virginia, and DuraSpace to work towards a reusable framework for multi-purpose, multi-functional, multi-institutional repository-enabled solutions for the management of digital content collections [1]. An initial timeframe for the project of three years had seen all founding institutional partners successfully implement a repository demonstrating these characteristics. Key to the aims of the project has always been to generate wider interest outside the partners to foster not only sustainability in the technology, but also sustainability of the community around this open source development. Hydra has been disseminated through a range of events, particularly through the international Open Repositories conferences [2], but the sphere of interest in Hydra has now stimulated the holding of specific events in different countries: Hydra UK is one of them.

The Hydra UK event was held on 22 November 2012, kindly hosted by the Library at the London School of Economics. Representatives from institutions across the UK, but also Ireland, Austria and Switzerland, came together to learn about the Hydra Project, and to discuss how Hydra might serve their digital content collection management needs. 29 delegates from 21 institutions were present, representing mostly universities but also the archive, museum and commercial sectors. Five presentations were given on Hydra, focusing on the practical experience of using this framework and how it fits into overall system architectures, and time was also deliberately given over to discussion of more specific topics of interest and to allow delegates the opportunity to voice their requirements. The presentations were:

Introduction to Hydra
Hydra @ Hull
Hydra @ Glasgow Caledonian University
Hydra @ LSE
Hydra @ Oxford

Introduction to Hydra

Chris Awre from the University of Hull gave the opening presentation. The starting basis for Hydra was mutual recognition by all the founding partners that a repository should be an enabler for managing digital content collections, not a constraint or simply a silo of content. Digital repositories have been put forward and applied as a potential solution for a variety of use cases over the years, and been used at different stages of a content lifecycle.

Figure 1: LSE Library
(Photo courtesy of Simon Lamb, University of Hull.)

To avoid producing a landscape of multiple repositories all having to be managed to cover these use cases, the Hydra Project sought to identify a way in which one repository solution could be applied flexibly to meet the requirements of different use cases. The idea of a single repository with multiple points of interaction came into being – Hydra – and the concept of individual Hydra ‘head’ solutions.

The Hydra Project is informed by two main principles:

No single system can provide the full range of repository-based solutions for a given institution’s needs,
o …yet sustainable solutions require a common repository infrastructure.
No single institution can resource the development of a full range of solutions on its own,
o …yet each needs the flexibility to tailor solutions to local demands and workflows.

The Hydra Project has sought to provide the common infrastructure upon which flexible solutions can be built, and shared.

The recognition that no single institution can achieve everything it might want for its repository has influenced the project from the start. To quote an African proverb, ‘If you want to go fast go alone, if you want to go far, go together’. Working together has been vital. To organise this interaction, Hydra has structured itself through three interleaving sub-communities, the Steering Group, the Partners and Developers, as shown by Figure 2.

Figure 2: Hydra community structure

The concept of a Hydra Partner has emerged from this model of actively working together, and the project has a Memorandum of Understanding (MoU) process for any institution wishing to have its use of, and contribution and commitment to Hydra recognised. Starting with the original four partners in 2008, Hydra now has 11 partners, with two more in the process of joining. All have made valuable contributions and helped to make Hydra better. Hydra partnership is not the only route to involvement, though, and there are many in the Hydra developer community who are adopters of the software, but who have not reached a stage where partnership is appropriate.

The technical implementation of Hydra was supported through early involvement in the project by MediaShelf, a commercial technical consultancy focused on repository solutions. All Hydra software is, though, open source, available under the Apache 2.0 licence, and all software code contributions are managed in this way. The technical implementation is based on a set of core principles that describe how content objects should be structured within the repository, and with an understanding that different content types can be managed using different workflows. Following these principles, Hydra could be implemented in a variety of ways: the technical direction taken by the project is simply the one that suited the partners at the time.

Hydra as currently implemented is built on existing open source components, and the project partners are committed to supporting these over time:

Fedora: one of the digital repository systems maintained through DuraSpace [3]
Apache Solr: powerful indexing software now being used in a variety of discovery solutions [4]
Blacklight: a next-generation discovery interface, which has its own community around it [5]
Hydra plugin: a collection of components that facilitate workflow in managing digital content [6]
Solrizer: a component that indexes Fedora-held content into a Solr index

These components are arranged in the architecture shown in Figure 3.

Figure 3: Hydra architecture

A common feature of the last three components in the list above is the use of Ruby on Rails as the coding language and its ability to package up functionality in discrete ‘gems’. This was consciously chosen for Hydra because of its agile programming capabilities, its use of the MVC (Model–View–Controller) structure, and its testing infrastructure. The choice has been validated on a number of occasions as Hydra has developed. However, it was noted that other coding languages and systems could be used to implement Hydra where appropriate. This applies to all the main components, even Fedora. Whilst a powerful and flexible repository solution in its own right, Fedora has proved to be complex to use: Hydra has sought in part to tap this capability through simpler interfaces and interactions.

Book Review: Getting Started with Cloud Computing

lisrw — Sat, 28 Jul 2012 22:42:54 +0000

Martin White reviews a collection of essays on cloud computing that attempts to clarify the technology and its applications for librarians and information professionals.

I will admit to having read very little in the way of fiction writing over the last half-century though perhaps as a chemist by training I do enjoy science fiction from authors such as Arthur C. Clarke, Isaac Asimov and Fred Hoyle. All were distinguished scientists, none more so than Fred Hoyle, who was Plumian Professor of Astronomy and Experimental Philosophy at the University of Cambridge.

The CLIF Project: The Repository as Part of a Content Lifecycle

lisrw — Fri, 09 Mar 2012 14:06:59 +0000

Richard Green, Chris Awre and Simon Waddington describe how a digital repository can become part of the technical landscape within an institution and support digital content lifecycle management across systems.

At the heart of meeting institutional requirements for managing digital content is the need to understand the different operations through which content goes, from planning and creation through to disposal or preservation. Digital content is created using a variety of authoring tools. Once created, the content is often stored somewhere different, made accessible in possibly more than one way, altered as required, and then moved for deletion or preservation at an appropriate point.

Editorial Introduction to Issue 68

lisrw — Mon, 12 Mar 2012 15:17:06 +0000

The editor introduces readers to the content of Ariadne issue 68.

I am pleased to introduce you to the content of Issue 68, and to have the opportunity to remind you that you have a far larger number of channels into the publication’s content.

International Digital Curation Conference 2010

editor — Sun, 30 Jan 2011 00:00:00 +0000

Alex Ball reports on the 6th International Digital Curation Conference, held on 7-8 December 2010 in Chicago.

The International Digital Curation Conference has been held annually by the Digital Curation Centre (DCC) [1] since 2005, quickly establishing a reputation for high-quality presentations and papers. So much so that, as co-chair Allen Renear explained in his opening remarks, after attending the 2006 Conference in Glasgow [2] delegates from the University of Illinois at Urbana-Champaign (UIUC) offered to bring the event to Chicago.

Developing Infrastructure for Research Data Management at the University of Oxford

editor — Fri, 29 Oct 2010 23:00:00 +0000

James A. J. Wilson, Michael A. Fraser, Luis Martinez-Uribe, Paul Jeffreys, Meriel Patrick, Asif Akram and Tahir Mansoori describe the approaches taken, findings, and issues encountered while developing research data management services and infrastructure at the University of Oxford.

The University of Oxford began to consider research data management infrastructure in earnest in 2008, with the 'Scoping Digital Repository Services for Research Data' Project [1]. Two further JISC (Joint Information Systems Committee)-funded pilot projects followed this initial study, and the approaches taken by these projects, and their findings, form the bulk of this article.

Institutional Web Management Workshop 2010

editor — Thu, 29 Jul 2010 23:00:00 +0000

Keith Doyle provides a personal perspective on a conference organised by UKOLN for those involved in the provision of institutional Web services.

This was the 13th Institutional Web Management Workshop [1] to be organised by UKOLN [2] held at the University of Sheffield from 12 to 14 July 2010. The theme was 'The Web in Turbulent Times' [3]. As such, there was a healthy balance of glass-half-empty-doom-and-gloom, and glass-half-full-yes-we-can.

Intranet Management: Divine Comedy or Strategic Imperative?

editor — Sat, 30 Jan 2010 00:00:00 +0000

Martin White suggests that a failure to recognise the value of intranets is a symptom of a failure to recognise information as a strategic asset.

According to Dante in his Divine Comedy the inscription above the door to Hades reads "Abandon hope all ye who enter here". For many this could also be the sign on the home page of their organisation's intranet as, with business-critical decisions to make, they begin the daily hunt for information that they are sure should be somewhere in the application. It could just as easily be the sign on the door of the intranet manager of the organisation, though this door usually also carries a number of other job descriptions, all of which seem to be given more priority by the organisation than the care and development of the intranet. Most organisations of any size will have a full-time web manager, often with a support team, but this is rarely the case with the intranet.

There are a substantial number of intranets in the UK. Statistics from the Office for National Statistics indicate that 22% of all businesses have an intranet [1]. As the size of the business increases so does the level of penetration, and most businesses of more than 500 people will now have some form of intranet. Given the number of businesses in the UK the author estimates that there are probably around 300,000 intranets in the commercial sector, and at a guess a further 100,000 in the public sector, charities, Higher Education institutions (HEIs) and other organisations. Only over the last few years has any reliable statistical information become available on intranet use and development, and this is a in-depth global survey of only around 300 intranets [2]. In the UK HEI sector a major opportunity was lost in a survey commissioned in 2009 by Eduserv into the management of web content in the HEI sector as no account of intranet use of CMS applications was included in the scope of the survey [3]. A survey of SharePoint use in HEIs undertaken for Eduserv in late 2009 [4] did indicate that a number of institutions were using SharePoint for intranet applications but the survey did not look in detail at intranet implementation.

It is also only over the last few years have forums been set up in which intranet managers are able to share experiences and challenges with others. The work of the Intranet Benchmark Forum [5] is focused on providing services to large organisations, but there are also other virtual and physical discussion forums, such as the Intranet Forum [6] run by UKeiG for its members. It is probably reasonable to suggest that the majority of intranet managers have seen very few intranets from which to gain a sense of good practice, whereas web managers have an almost unlimited supply of sites from which to gain ideas for their own use. This is as true in the HEI sector as in other sectors. Given the installed base of intranets in the UK it is also surprising that there is no 'intranet conference' event even though intranet management does feature in events such as Online Information [7]. Most countries in northern Europe have an intranet conference [8], often with several hundred delegates, so why there is no equivalent in the UK is a mystery.

Intranets Are Different

All too often an intranet is regarded as an internal web site. The reality is that about the only commonality between an intranet and a web site is the use of web browser technology. Many very successful intranets do not even use a web content management application but instead are based on Notes technology or portal applications. Intranet content contribution is usually highly distributed, with individual members of staff publishing content direct to the intranet perhaps only a few times a year. This means that the web content management system has to be highly intuitive, and enable Word documents to be rendered into clean HTML code to create web pages. The teams supporting public web sites are using the systems every working day, working often in HTML and having a much more limited range of content to cope with. Many of the problems that arise in keeping content current on an intranet are a result of staff having to use a complex Web publishing system that was specified for Web site management and not intranet management.

Another factor to be considered is that increasingly intranets are federated applications [9]. This is often the situation in HEIs where each department wants to have its own intranet, and on top of all these individual intranets there is some form of top-level 'corporate' home page and navigation. Often there is no central coordination of these intranets, and so each adopts some or none of the visual design standards of the HEI.

As far as enterprise applications are concerned, intranets are different because they are not based on business processes or work-flow. Finance, registry, personnel and most other applications support well-defined processes, usually within a specific department, and where the content requirements are usually specified in database terms. Anything approaching text content is usually relegated to a single field in the database. Intranets exist because there is a substantial amount of information in any organisation that is not based on business processes and cannot be managed within a formal database structure, such as policies, procedures, campus maps, events, staff notices and hundreds of other information formats produced by every department and location within the organisation.

As a result the intranet becomes an information dumping ground. Under-resourced intranet managers do not have the resources to maintain content quality, and so multiple versions of documents with no visible ownership or provenance proliferate. Employees leave or change responsibility but the intranet is based on a 'file-and-forget' principle and no effort is taken to ensure that document ownership is transferred to another member of staff. Very quickly the information architecture of the intranet, based usually on the structure of the organisation at the time of the last WCMS (Web content management system) deployment, is not fit for purpose. The decision is taken to implement a search engine, and only then does the scale of the problem of information decay become apparent. It can also be an interesting exercise to search for 'Confidential' and see just how many documents are returned!

News and Events

editor — Wed, 29 Jul 2009 23:00:00 +0000

Ariadne presents a brief summary of news and events.

JISC Digital Media Course: Introduction to Image Metadata

ILRT, 8-10 Berkeley Square, Bristol, BS8 1HH
Wednesday 9 December 2009
Full-day course: 10.00 - 16.30
http://www.jiscdigitalmedia.ac.uk/training/courses/introduction-to-image-metadata/

Book Review: Web Accessibility

editor — Tue, 29 Jul 2008 23:00:00 +0000

Martin White reviews a book that provides advice for managers on how to ensure that Web sites, intranets and library services are fully compliant with guidelines and legislation on accessibility.

There are many books on Web accessibility but they tend to come at the subject from quite a narrow area of Web design. This is especially true of books published in the USA, a country which has quite limited Federal legislation on the need to implement accessible Web sites and intranets. It is a subject that should be of passionate interest to our profession in its commitment to providing access to information to all who request it. We not only have a duty under legislation to provide accessible access but, as the back cover of the book highlights, also a moral duty.

News and Events

editor — Tue, 29 Apr 2008 23:00:00 +0000

Ariadne presents a brief summary of news and events.

UKeiG Courses over May – October 2008

Searching the Internet: Google and Beyond

Karen Blakeman
Friday 16 May 2008
University of Liverpool
http://www.ukeig.org.uk/training/2008/May/beyondgoogle.html

Searching the Internet: Google and Beyond

Karen Blakeman
Wednesday 11 June 2008
King's College London, Guy's Campus
http://www.ukeig.org.uk/training/2008/June/beyondgoogle.html

The DARE Chronicle: Open Access to Research Results and Teaching Material in the Netherlands

editor — Tue, 30 Oct 2007 00:00:00 +0000

Leo Waaijers reflects on four years of progress and also looks ahead.

While Cream of Science (Keur der Wetenschap), Promise of Science and the HBO Knowledge Bank (HBO Kennisbank) are among the inspiring results of the DARE Programme for the period 2003-06, what is more important in the long run is the new infrastructure that enables Dutch Higher Education and research institutions to provide easy and reliable open access to research results and teaching material as quickly as possible. Such open access ought to be the standard in a knowledge-driven society, certainly if the material and data have been generated with public funding.