I said in my last post that I'd report on technical and legal issues raised by repsondents to our questionnaire. I'm going to delay reporting on requirements for apps because I've still got a couple of things to clarify, but hope to be able to publish something about Pelagios apps next week. In the meantime, here's a few points about technical and legal issues.
Technicalrequests included the following.
That the data should be exposed via a Linked data/SPARQL endpoint (i.e. the data should not be available only via an API);
Atom feeds for sharing updates about resources associated with a given Pleiades place.
Well documented REST based APIs for all services, and more specifically, ‘JSON data via a nice RESTful API’. It would also be good to have an API from Pelagios (or at least a way of getting solely data) so that the 'widget' front end could look however you wish. Ideally the widget would be able to be styled in whatever format is needed; and
that the apps and widgets should reuse and support open standards.
Legal points made included the following suggestions and concerns.
That the license structures adopted in the first phase of the Pelagios project are adequate.
That licensing conditions should be "flagged up" - e.g. with some an icon, tool tip or other means that are visible but do not dominate the information provided
If people are adding their own data then there needs to be some discussion of the licensing of that data. Should it go into the "big pot for everyone to use, or can they choose to CC license it, etc, keep it private, etc? If this is an option, licensing will have to be worked out".
This is the second in a series of posts about users’ requirements for Pelagios apps and widgets. The first post set the scene, and this one describes some of our initial findings from the "super user" group.
what the Pelagios apps and widgets could do
e.g. specific goals they could help people achieve, tasks they should help people carry out
what sort of things different types of users might do with the apps/widgets
If there are different audiences, what will these different audiences do
barriers to exploiting Pelagios partners data
technical and legal considerations
This post summarises the findings about the target audience(s), the widgets, and the perceived barriers.
The target audience(s) for the apps and widgets
Some respondents identified "super users" as the primary target audience for the apps and widgets. However, the majority of responses suggested that non-technical users should be catered for.
Suggestions on this theme included groups of people with both a professional and/or an amateur interest in the ancient world:
- tourists who want to know about the cultural background of their vacation spot,
- historians that want to have an overview of their local history in terms of research,
- archaeologists that are interested in the findings and citations in literature related to the area of their excavations, - fiction writers who want to get abetter historical background of a setting for a story
- educators who want to give their students some background knowledge about the ancient history of a place they are looking at
- researchers that want to find things by place
and
"anybody who uses the web". What the Pelagios widgets should do
Respondents suggestions varied from general guidance about the nature of the widgets (e.g. 'nice, compact, easy-to-transit view of related linkages', 'allow people to easily add some "Pelagios context" to their own place-related web pages') to some more specific suggestions.
The specific suggestions include:
focus on a topographical spot so that once embedded into a website the widget will display contextual data for a Pleiades place, e.g. showing any literature mentioning Isica on a map, or as a list.
enable the user to search on modern place names (e.g. Mainz instead of Mogontiacum)
an API that outputs RDF/xml or plain XML of the entire Pelagios dataset, input parameters would be Pleiades-id or search string of place name
a person is viewing a web page that mentions a place; the widget that displays "other cool stuff" from the Pelagios universe related to that place
Barriers to exploiting Pelagios partners data
Concerns raised included
the projects that are linked by Pelagios use different languages
the PELAGIOS annotation spec is not complete and published. The format may change, thereby breaking any applications or queries we build around it.
The next post will be about requirements for the Pelagios apps, and technical and legal issues that were raised by respondents. By the way if you have been invited to fill out the requirements
questionnaire please do so, we are still analying responses but
would like some more before the 9th of March :-)
This is the first in a series of posts about users’ requirements for the Pelagios visualization service. The visualization service will be implemented as a set of web apps and widgets that will "enable providers, end-users and developers to find, visualize and build upon geospatial connections between openly available resources" (JISCPelagios2 project summary). To put this post in context, the project plan adds a bit more detail indicating that the web apps and widgets will provide end users with intuitive and user friendly tools to visualize data available through APIs produced by WP1 (webcrawling and indexing service) and WP2 (place/space-based APIs and contextualisation service). The end users may be subject specialists, but they will not necessarily have the technical expertise to make use of this data directly. Overall, there are three key groups of users that we will target to gather requirements from:
"Super users" - e.g. developers, digital humanities specialists typified by the Pelagios2 project partners
"End users" - people with an interest in Pelagios data, but without the technical skills necessary to exploit it e.g. ancient history students and teachers, folk who visit ancient sites on holiday
"Web site admins" - people who own administer sites that could embed Pelagios widgets. These could be museum or history related sites, and it's their technical requirements and restrictions that are the initial concern.
This first post sets out to discriminate between web apps and widgets, with the intention (and hope) that explaining the meaning of these terms will help the interpretation of future posts about the users' requirements. We're also thinking that to gather requirements from non-techie end users it will be useful to give some examples of apps and widgets that they may already be familiar with.
What is a web app? What is a web widget?
‘Web app’ and ‘web widget’ are shorthand terms to summarise some features of web based tools and applications.
We are using the term ‘app’ to refer to a application that would typically be accessed in its own web page, and allows the user to manipulate data and relationships between items of data. For example, the Flickr web app shown in this screen grab enables the Flickr user to drag pictures from the group at the bottom of the screen into the working area in the middle of the screen, and then edit data about the selected photos (title, location time taken etc.), and to group the photos into sets. (Please click on the image to open a clearer view of it).
In contrast, a ‘widget’ is an interface to a web application that can be embedded within a web page. A widget will typically offer fewer options, and less functionality, than an app to the user, because often it will occupy less screen space. A widget may meet one specific need, whereas an app may meet several, and usually a widget allows data to be displayed, whereas an app enables data to be displayed and edited.. The Flickrslide show shown below is an example of a widget. This allows the end user to embed a copy of a set of photos in their site. In this case the 'end user' is the person embedding the slide show, not the person who created it.
For media objects such as photos, videos and music, web apps typically provide a way to upload, tag and describe individual items, or how items relate to one another, or to edit the items themselves. Widgets typically provide the functionality to embed a media object in another page (or a set of objects), and allow access to a subset of the descriptive information that is available via the full app user interface.
It may be the case in Pelagios, as in other areas, that there will be a grey area between apps and widgets. Next steps
We have begun by surveying super users (including Pelagios partners) using a questionnaire, and in the next post I will describe initial feedback from this group about their requirements for Pelagios web apps and widgets. By the way, if you have received an invitation to respond to the questionnaire, we do want more responses so please do complete it and return it!
Thanks Andrew (the inept photographer responsible for the images embedded in this post)