Menu
▾
▴
[Xena-devel] [ xena-Feature Requests-1181179 ] Take a wrapped bitstream and normalise it
|
From: SourceForge.net <no...@so...> - 2009-12-11 00:13:55
|
Feature Requests item #1181179, was opened at 2005-04-12 11:26 Message generated for change (Comment added) made by vombatus You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=577092&aid=1181179&group_id=85722 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Normaliser Group: None Status: Open Resolution: Remind Priority: 3 Private: No Submitted By: Chris Strusz (chrissnaa) Assigned to: Michael Carden (mcarden) Summary: Take a wrapped bitstream and normalise it Initial Comment: - User must be able to select one or more Xena packages that are base64 normalised (ie wrapped bitstreams) and tell Xena to normalise them. - They should be able to do this with a minimum amount of user input. - AIPs produced during renormalisation will have new ids assigned. - XenaInputSource+getSystemId() will return the filename of the binary AIP being renormalised (e.g. something.xena) which will become the source parameter in NormaliserManager+newInputSource(...) BACKGROUND NAA generates a XML wrapped and a normalised version of each data object processed. If a normaliser is not available at the time of initial preservation processing, only a XML wrapped AIP is generated. XML wrapped AIPs may be reprocessed when a normaliser becomes available. NAA may also reprocess XML wrapped AIPs to generate a replacement normalised version. Replacement normalised versions may be requested to replace faulty normalisers, harvest additional metadata or for other reasons. The previous normalised version is replaced in the repositories and is no longer available. This RFE is designed to enable Xena to meet these criteria. ---------------------------------------------------------------------- >Comment By: John (vombatus) Date: 2009-12-11 11:13 Message: This feature request appears to be initially squarely aimed at the issue of reprocessing. Do we still need the request to be open? I came across this when looking for a request about handling VERS encapsulated objects which I was sure was in here somewhere (but I couldnt find it). It is possible that we could receive documents which comprise a bitstream wrapped in metadata (eg a VEO). we would need to strip the metadata from the object, normalise the file represented by the bitstream and do something with the metadata (probably create a text file and dump the metadata into it) I am happy to raise a new feature request if necessary ---------------------------------------------------------------------- Comment By: Michael Carden (mcarden) Date: 2006-11-30 15:32 Message: Logged In: YES user_id=1277767 Originator: NO The original request should be reworded for clarity. Rather than binary normalising an object twice, the need is to export a binary normalised object, then normalise it to a preservation format. This, as Justin suggests, has been implemented in DPR. There may still be a separate need to look at having a renormalise API method in Xena though. ---------------------------------------------------------------------- Comment By: Justin Waddell (jwaddell) Date: 2006-11-30 10:54 Message: Logged In: YES user_id=1417827 Originator: NO Reprocessing has been implemented successfully in DPR so this is no longer crucial. However it could be useful to have a "renormalise" API method available in Xena, Discussion required. ---------------------------------------------------------------------- Comment By: Chris Bitmead (chrisbitmead) Date: 2005-05-19 16:28 Message: Logged In: YES user_id=223792 Can you fill me in on why the source would be reported incorrectly? ---------------------------------------------------------------------- Comment By: Chris Strusz (chrissnaa) Date: 2005-05-19 15:31 Message: Logged In: YES user_id=793594 This RFE is crucial for reprocessing. DPR requires that it be done, otherwise the source will be reported incorrectly unless we do a very clunky workaround. Because of this, this RFE is approved as the first post Xena 2.0 RFE. ---------------------------------------------------------------------- Comment By: Chris Strusz (chrissnaa) Date: 2005-04-18 14:19 Message: Logged In: YES user_id=793594 This is no longer a 2.0 item, but is kept in as a 2.1.x item. There is a workaround in the process this item is for, so we don't need it for 2.0, however we will want to implement it soon thereafter. hence it is a 2.1.x item. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=577092&aid=1181179&group_id=85722 |