[Xena-devel] Xena - website normaliser - comments needed

[Chris S. <chr...@na...>]

Hi everyone,
one of the normalisers we're building for Xena 2.0 is a website normaliser. 
This normaliser will enable us to preserve snapshots of websites, which,
under the AFDA are Retain as National Archives (see
http://naa.gov.au/recordkeeping/disposal/authorities/GDA/AFDA/PDF/Publicatio
n.pdf, Publication - Production, Entry No. 1935).

while originally we were looking at having a web package document for this
(see
https://sourceforge.net/tracker/index.php?func=detail&aid=1046746&group_id=8
5722&atid=577092), on further reflection I think that we should instead have
a series of user stories to test against. So here they are.

Can I please have your comments by the 23rd of February,
thanks
Chris



User stories for Xena Website normaliser
These user stories describe what the Xena website normaliser is to be
capable of.
1.	The user must be able to normalise a snapshot of a website stored on
a piece of media, eg CD, USB hard drive, etc.
2.	The user must be able to normalise a live website over a network
(including the internet).
3.	The user should be able to navigate around the normalised website
using the links within the website, ie the links within a normalised website
should work.
4.	The user does not need to be able to link to external websites.
5.	The user should be able to see the URL that a link points to easily,
ie without having to see the source code.
6.	The user should be able to view the normalised website using their
own browser, just like you can with normalised HTML documents now.
7.	The look and feel of a website should be retained as much as
possible when viewing it through a browser. 
8.	The native view within Xena does not need to retain look and feel,
however it must present all the text and an indication of embedded images
(eg, an icon that says, 'there is an image here')
9.	Font substitution is allowed (many fonts are licensed)
10.	The user must be able to tell what is a heading and what is text.
Different levels of headings should also be clear.
11.	The absolute font size is not critical. It would be preferred if
relative font sizes were retained - but this might be covered by headings.
12.	When normalising a website, while it is allowed to normalise each
item separately, it must be possible to create an output that can be
discretely identified as being the normalised website; eg, all the
normalised files are placed in a single directory.
13.	Where Xena cannot normalise a data object within a website, then it
binary wraps that data object.
14.	When asked to perform a binary wrapped data object within the
website, if Xena can't display it, Xena should show a message that states
that the object cannot be viewed and why.
15.	It should be possible to extract a binary wrapped object from within
the preserved website, such that the user can try to view it using software
installed on their computer or normalise it as a separate data object.