Identifying Web Content for Long Term Access

Persistently identifying Web site content Future-proofing Institutional Web sites DCC and Wellcome Library workshop

Contents ,[object Object],[object Object],[object Object],[object Object],[object Object]

Context – institutional Web sites ,[object Object],[object Object],[object Object],[object Object],[object Object]

Context – man vs. machine ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Context – what is being identified ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Context - works vs. manifestations ,[object Object],[object Object],[object Object],[object Object],“ Crystal Studio is a recommended resource for the teaching of crystallography at undergraduate level.“ "To perform this exercise you will need a copy of Crystal Studio version 5.0 (versions 4.0 Lite and 4.0 Professional do not support the required options)."

Functional requirements… ,[object Object],Every significant item that is made available through a JISC IE network service should be assigned a URI that is reasonably persistent. This means that item URIs should not be expected to break for a period of 10-15 years after they have first been used. For this reason, JISC IE service components should not hardcode file format, server technology, service organisational structure or other information that is likely to change over a 10-15 year period into item URIs. If items become unavailable during that period, then the URI should resolve to a Web page that explains why the item is no longer available and what actions the end-user can take to obtain a copy of the item or similar resources. Furthermore, item URIs should not contain end-user-specific information, i.e. all item URIs should work for all end-users (albeit allowing for appropriate authentication challenges to be inserted into the process by which the URI is resolved). http://www.ukoln.ac.uk/distributed-systems/jisc-ie/arch/standards/ Every significant item that is made available through a JISC IE network service should be assigned a URI that is reasonably persistent. This means that item URIs should not be expected to break for a period of 10-15 years after they have first been used. For this reason, JISC IE service components should not hardcode file format, server technology, service organisational structure or other information that is likely to change over a 10-15 year period into item URIs. If items become unavailable during that period, then the URI should resolve to a Web page that explains why the item is no longer available and what actions the end-user can take to obtain a copy of the item or similar resources. Furthermore, item URIs should not contain end-user-specific information, i.e. all item URIs should work for all end-users (albeit allowing for appropriate authentication challenges to be inserted into the process by which the URI is resolved).

What should be identified? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

What does ‘reasonably persistent’ mean? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

What does ‘break’ mean? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Usability issues ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Interim conclusions… ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

‘ http’ URI problems? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

How indirection works (or not?) ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

What about uniqueness? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

ARK system ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Anatomy of ‘http’ URIs http:// www.somewhere.ac.uk/physics/index.cfm ? name=about http:// www.somewhere.ac.uk/chemistry/report.rtf ‘ http’ URI scheme – URI persistence not reliant on HTTP protocol, but is reliant on continued registration and management of the scheme (and of the URI spec. itself!) DNS domain name – persistence reliant on continued ownership and management of the DNS domain name (and the DNS!) Component hierarchy, often organisationally based – persistence reliant on continued management of component structure, i.e. not re-using old components Server technology – change of technology may enforce change of URI, leading to multiple URIs for same resource (with no simple mechanism for determining equivalence) File format – inappropriate if identifier is for the ‘work’ rather than the ‘manifestation’ - because changing the format will result in a new URI

Improving persistence of ‘http’ URIs ,[object Object],[object Object],[object Object],[object Object],[object Object]

Conclusions and recommendations ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Identifying Web Content for Long Term Access

Recommended

Recommended

More Related Content

Similar to Identifying Web Content for Long Term Access

Similar to Identifying Web Content for Long Term Access (20)

More from Andy Powell

More from Andy Powell (20)

Recently uploaded

Recently uploaded (20)

Identifying Web Content for Long Term Access