Visualizing OAIS – Revised functions diagram proposal - Revision history

Eld at 10:33, 7 February 2017

2017-02-07T10:33:20Z

← Older revision		Revision as of 10:33, 7 February 2017
Line 1:		Line 1:
	''~~Below~~ headers correspond to fields on submission from via http://review.oais.info''		Registered on the OAIS review wiki ([http://review.oais.info http://review.oais.info]) in issues:
			*[http://review.oais.info/show_bug.cgi?id=141 http://review.oais.info/show_bug.cgi?id=141] Suggested Change 141 - Revised/corrected Figure A-1 "Composite of Functional Entities"

			''Originally the below headers correspond to fields on submission from via http://review.oais.info''

	==[http://review.oais.info/page.cgi?id=fields.html#product Product:] (from selected product)==		==[http://review.oais.info/page.cgi?id=fields.html#product Product:] (from selected product)==

Eld at 16:16, 28 November 2016

2016-11-28T16:16:45Z

← Older revision		Revision as of 16:16, 28 November 2016
Line 27:		Line 27:
	==[http://review.oais.info/page.cgi?id=fields.html#short_desc Summary:]==		==[http://review.oais.info/page.cgi?id=fields.html#short_desc Summary:]==
	Correction of various errors and inconsistencies:		Correction of various errors and inconsistencies:
	*''Lines with information packages are made more thick'' <br>		*''Lines with information packages are made more thick'' <br> This is an idea that Ulla Bøgvad Kejser came up with, to make the flow of the information package(s) in the OAIS, Eld Zierau has made the update information package flow a bit thinner in order to distinguish this from the main flow.
	This is an idea that Ulla Bøgvad Kejser came up with, to make the flow of the information package(s) in the OAIS, Eld Zierau has made the update information package flow a bit thinner in order to distinguish this from the main flow.		*''Repetition of arrow markings and arrow text on the arrows have been omitted'' <br> as it was not used consistently and it did not add any value, and at the same time it contributed to a blurring and confusion. Instead all text is only placed at the end of the arrow – as the description of the information that is carried to an entity. This is done consistently, so no confusion should be possible.
	*''Repetition of arrow markings and arrow text on the arrows have been omitted'' <br>		*''All descriptions now start with a capital letter'' <br> This also commands in Archival Storage for the Manage Storage Hierarchy function.
	as it was not used consistently and it did not add any value, and at the same time it contributed to a blurring and confusion. Instead all text is only placed at the end of the arrow – as the description of the information that is carried to an entity. This is done consistently, so no confusion should be possible.		*''Lines have been untangled'' <br> This includes aligning related arrows (e.g. report request from different places) by placed next placing then next to each other
	*''All descriptions now start with a capital letter'' <br>		*''Ingest is not called Access'' <br> which is an error in the present diagram
	This also commands in Archival Storage for the Manage Storage Hierarchy function.		*''Arrows that are part of the same transmission of data are merged to one'' <br> This is done in order to make it more readable and more consistent with e.g. the arrow for the submission. This is e.g. the case for arrow(s) between the functions Provide Data and Generate DIP
	*''Lines have been untangled'' <br>		*''Final Ingest report arrows in Administration have been fixed'' <br>
	This includes aligning related arrows (e.g. report request from different places) by placed next placing then next to each other		*''Number of corrections according to the actual descriptions of the functional entities'' <br> For example all arrows from the Access functional entity to the functions Customer service and Establish Standards and Policies is in the Administration functional entity are now in the diagram. The same is the case for some of the Preservation Planning functions and there have been some tidying up with the Access functional entity as well.
	*''Ingest is not called Access'' <br>
	which is an error in the present diagram
	*''Arrows that are part of the same transmission of data are merged to one'' <br>
	This is done in order to make it more readable and more consistent with e.g. the arrow for the submission. This is e.g. the case for arrow(s) between the functions Provide Data and Generate DIP
	*''Final Ingest report arrows in Administration have been fixed'' <br>
	*''Number of corrections according to the actual descriptions of the functional entities'' <br>
	For example all arrows from the Access functional entity to the functions Customer service and Establish Standards and Policies is in the Administration functional entity are now in the diagram. The same is the case for some of the Preservation Planning functions and there have been some tidying up with the Access functional entity as well.


	==Description of requested change:==		==Description of requested change:==

Eld at 16:15, 28 November 2016

2016-11-28T16:15:32Z

← Older revision		Revision as of 16:15, 28 November 2016
Line 5:		Line 5:

	==[http://review.oais.info/page.cgi?id=fields.html#reporter Reporter:] (from login)==		==[http://review.oais.info/page.cgi?id=fields.html#reporter Reporter:] (from login)==
			elziATTkb.dk

	==[http://review.oais.info/describecomponents.cgi?product=OAIS%20June%202012 Component:] (from list)==		==[http://review.oais.info/describecomponents.cgi?product=OAIS%20June%202012 Component:] (from list)==
			Section Annexes

	==Component Description (fixed from selection of 'Component'):==		==Component Description (fixed from selection of 'Component'):==
			Various Annexes

	==[http://review.oais.info/page.cgi?id=fields.html#version Version:] (from selected product) ==		==[http://review.oais.info/page.cgi?id=fields.html#version Version:] (from selected product) ==
Line 14:		Line 17:

	==[http://review.oais.info/page.cgi?id=fields.html#bug_severity Category of change:] (from list)==		==[http://review.oais.info/page.cgi?id=fields.html#bug_severity Category of change:] (from list)==
			Updates to matters of fact

	==[http://review.oais.info/page.cgi?id=fields.html#rep_platform Are there issues of backward compatibility?:] (from list)==		==[http://review.oais.info/page.cgi?id=fields.html#rep_platform Are there issues of backward compatibility?:] (from list)==
			No

	==[http://review.oais.info/page.cgi?id=fields.html#op_sys Is this a conformance issue?:] (from list)==		==[http://review.oais.info/page.cgi?id=fields.html#op_sys Is this a conformance issue?:] (from list)==
			No

	==[http://review.oais.info/page.cgi?id=fields.html#short_desc Summary:]==		==[http://review.oais.info/page.cgi?id=fields.html#short_desc Summary:]==
			Correction of various errors and inconsistencies:
			*''Lines with information packages are made more thick'' <br>
			This is an idea that Ulla Bøgvad Kejser came up with, to make the flow of the information package(s) in the OAIS, Eld Zierau has made the update information package flow a bit thinner in order to distinguish this from the main flow.
			*''Repetition of arrow markings and arrow text on the arrows have been omitted'' <br>
			as it was not used consistently and it did not add any value, and at the same time it contributed to a blurring and confusion. Instead all text is only placed at the end of the arrow – as the description of the information that is carried to an entity. This is done consistently, so no confusion should be possible.
			*''All descriptions now start with a capital letter'' <br>
			This also commands in Archival Storage for the Manage Storage Hierarchy function.
			*''Lines have been untangled'' <br>
			This includes aligning related arrows (e.g. report request from different places) by placed next placing then next to each other
			*''Ingest is not called Access'' <br>
			which is an error in the present diagram
			*''Arrows that are part of the same transmission of data are merged to one'' <br>
			This is done in order to make it more readable and more consistent with e.g. the arrow for the submission. This is e.g. the case for arrow(s) between the functions Provide Data and Generate DIP
			*''Final Ingest report arrows in Administration have been fixed'' <br>
			*''Number of corrections according to the actual descriptions of the functional entities'' <br>
			For example all arrows from the Access functional entity to the functions Customer service and Establish Standards and Policies is in the Administration functional entity are now in the diagram. The same is the case for some of the Preservation Planning functions and there have been some tidying up with the Access functional entity as well.


	==Description of requested change:==		==Description of requested change:==
	''(Use From: "..." To "..." format)''		''(Use From: "..." To "..." format)''
			Change Figure A-1 with attached drawing

	==Attachment:==		==Attachment:==

	===File:===		===File:===
			''<File will have contents as given in section "Attachment File contents" below>''

	===Description:===		===Description:===
			Contents of new Figure A-1

			==[http://review.oais.info/page.cgi?id=fields.html#cf_organisation Organisation of the submitter:]==
			The Royal Library of Denmark (reviewed via [http://wiki.dpconline.org/index.php?title=OAIS_Community OAIS Community]

	==[http://review.oais.info/page.cgi?id=fields.html#~~version Organisation~~ of the ~~submitter~~:]==		==[http://review.oais.info/page.cgi?id=fields.html#cf_supporting_analysis_of_change Explanation of the reason for the suggested change:]==
			To have a correct and readable diagram.

	~~==[http://review.oais.info/page.cgi?id=fields.html#version Explanation~~ of ~~the reason~~ for ~~the suggested change:]==~~		Note that the figures in the attachment are following other suggestions and may need adjustments according to decisions on whether to include these other suggestions (Preservation Storage instead of Archival Storage, Visual OAIS – Symbols for functional entities, Visual OAIS – re-introducing coulours for functional entities).

	==Attachment File contents:==		==Attachment File contents:==

Eld: /* Attachment File contents: */

2016-11-28T15:52:26Z

Attachment File contents:

← Older revision		Revision as of 15:52, 28 November 2016
Line 36:		Line 36:

	==Attachment File contents:==		==Attachment File contents:==
			[[File:OAIS_functions.jpg\|1000px]]

			[[File:OAIS_legend.jpg\|400px]]

Eld at 13:54, 28 November 2016

2016-11-28T13:54:00Z

← Older revision		Revision as of 13:54, 28 November 2016
Line 22:		Line 22:

	==Description of requested change:==		==Description of requested change:==
			''(Use From: "..." To "..." format)''


			==Attachment:==

			===File:===
			===Description:===


			==[http://review.oais.info/page.cgi?id=fields.html#version Organisation of the submitter:]==

			==[http://review.oais.info/page.cgi?id=fields.html#version Explanation of the reason for the suggested change:]==

			==Attachment File contents:==

Eld: Created page with "''Below headers correspond to fields on submission from via http://review.oais.info'' ==[http://review.oais.info/page.cgi?id=fields.html#product Product:] (from selected prod..."

2016-11-28T13:51:07Z

Created page with "''Below headers correspond to fields on submission from via http://review.oais.info'' ==[http://review.oais.info/page.cgi?id=fields.html#product Product:] (from selected prod..."

New page

''Below headers correspond to fields on submission from via http://review.oais.info''

==[http://review.oais.info/page.cgi?id=fields.html#product Product:] (from selected product)==
OAIS June 2012

==[http://review.oais.info/page.cgi?id=fields.html#reporter Reporter:] (from login)==

==[http://review.oais.info/describecomponents.cgi?product=OAIS%20June%202012 Component:] (from list)==

==Component Description (fixed from selection of 'Component'):==

==[http://review.oais.info/page.cgi?id=fields.html#version Version:] (from selected product) ==
June 2012

==[http://review.oais.info/page.cgi?id=fields.html#bug_severity Category of change:] (from list)==

==[http://review.oais.info/page.cgi?id=fields.html#rep_platform Are there issues of backward compatibility?:] (from list)==

==[http://review.oais.info/page.cgi?id=fields.html#op_sys Is this a conformance issue?:] (from list)==

==[http://review.oais.info/page.cgi?id=fields.html#short_desc Summary:]==

==Description of requested change:==