Talk:2.2.3 INFORMATION PACKAGE VARIANTS: Difference between revisions

From wiki.dpconline.org
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 4: Line 4:


I'm not sure there is a huge problem to be solved here, but in line with the later steps in the lifecycle it would seem useful to have standard terminology for a package of content as it reaches the OAIS. This of course relates to ISO 20652:2006 and to discussions around the possible addition of a [[Pre-ingest]] stage [[User:PRWheatley|PRWheatley]] ([[User talk:PRWheatley|talk]]) 14:22, 11 July 2016 (UTC)
I'm not sure there is a huge problem to be solved here, but in line with the later steps in the lifecycle it would seem useful to have standard terminology for a package of content as it reaches the OAIS. This of course relates to ISO 20652:2006 and to discussions around the possible addition of a [[Pre-ingest]] stage [[User:PRWheatley|PRWheatley]] ([[User talk:PRWheatley|talk]]) 14:22, 11 July 2016 (UTC)
Interestingly the ISO 20652:2006 uses the 'transfer' language frequently. It may need substantial updates to support this concept (a TIP) if it were implemented in the OAIS model.
To clarify the thought behind this, it could be that most of the time submitters submit fully formed SIPs which archives/repositories turn into AIPs. But in many cases the submitter submits something that isn't really even a SIP yet and the receiving organization has to do work (e.g. appraisal/selection) to transform what they received into a SIP to be submitted to the repository to be turned into an AIP. --[[User:Euanc|Euanc]] ([[User talk:Euanc|talk]]) 15:44, 11 July 2016 (UTC)

Latest revision as of 15:44, 11 July 2016

Transfer Information Package

During discussion recently I suggested that something like a "Transfer Information Package" could be a useful concept to include in the OAIS. That would be for things being transferred to an organization that then does some additional appraisal and arrangement before creating a SIP to be ingested and turned into an AIP. I would be interested to hear if others thought this would be a useful addition or just redundant.--Euanc (talk) 14:04, 8 July 2016 (UTC)

I'm not sure there is a huge problem to be solved here, but in line with the later steps in the lifecycle it would seem useful to have standard terminology for a package of content as it reaches the OAIS. This of course relates to ISO 20652:2006 and to discussions around the possible addition of a Pre-ingest stage PRWheatley (talk) 14:22, 11 July 2016 (UTC)

Interestingly the ISO 20652:2006 uses the 'transfer' language frequently. It may need substantial updates to support this concept (a TIP) if it were implemented in the OAIS model. To clarify the thought behind this, it could be that most of the time submitters submit fully formed SIPs which archives/repositories turn into AIPs. But in many cases the submitter submits something that isn't really even a SIP yet and the receiving organization has to do work (e.g. appraisal/selection) to transform what they received into a SIP to be submitted to the repository to be turned into an AIP. --Euanc (talk) 15:44, 11 July 2016 (UTC)