A user must be able to give xena a URL and have xena
retrieve the resource reference by the URL. If the
resource is 'un-normalised', xena must begin the
normalisation process. If the resource is a xena
instance, xena must render the resource in its default
View.
Logged In: YES
user_id=793594
Could you please provide a reason for this enhancement.
What purpose would it serve and where would it be used.
Logged In: YES
user_id=613640
Amendment to the enahncement: it should be URI not URL.
This enahncement would be useful:
- Anytime you had a Xena package that was to be accessed
by a URL. There are two occassions where such a feature
might be used at NAA: (1) if the Digital Repository used an
open source digital repository application that only provided
access via a URI (such as Dspace or Fedroa, the two leading
open source repository systems) or (2) if NAA provided Xena
packages to a researcher via RecordSearch (due to
RecordSearch's web interface such DIPs could be downloaded
and viewed directly from Xena without having to download,
save to disk, and then open in Xena from the filesystem).
- Anytime you wanted to normalise something from a URL,
such as harvesting web resources or, indeed, any other
record directly from another system (that exposed records via
URI). For an example of the latter, with a TRIM system that
has the WebDrawer interface enabled, it would be possible to
normalise directly from Xena by plugging the WebDrawer URI
into Xena and then Xena collecting and normalising the
rercord. A much cleaner way of working than exporting stuff
to a filesystem.
Logged In: YES
user_id=1417827
Originator: NO
Discussion required to see if this feature is still wanted.
Logged In: YES
user_id=1277767
Originator: NO
Discuss in the context of web normalising.
Is this request still valid?
I wouldnt think that we would use Xena directly to pull information from a website or URI, but rather have some other tool do that prior to feeding the documents into Xena
Not required.