Page History

* CEEPR
* Communications Forum (start with this story)

* RLE
* Whirlwind
* Vail Balloon Prints

By walking through these cases we can identify workflows that can be finalized.

----
File naming conventions (focus on this topic 3/24) (/)
* see information saved in the Research section of this wiki
* see file naming scheme page
* see file naming quick reference page (will add to libstaff website)

----
Workflows - how do we organize these workflows?
* Barton - DSpace/DOME
* Barton - OCA - DSpace/DOME
* IRIS - DOME
* Working Papers/Technical Reports - DSpace/DOME
* Archivist Toolkit - DOME
* Filemaker Pro - DSpace/DOME
* Also, possibly by stages and steps (outline practices):Metadata, Scanning, Preservation, Ingest, Flickr, Interim Storage for scanning outputs, end processing, storage, shipping, picklist

----
Policy on archival masters(/)
* see file disposition page

----
Role and Responsibilities
* Who is responsible for tasks or set of tasks in each workflow, for example:
** Who makes Thumbnails - {color:#990033}DOME automatically creates or Document Services/Image Magik{color}
** Who builds Filemaker databases - {color:#990033}for now Rob & company will be responsible{color} is {color:#990033}there another tool besides xml editor or Filemaker can we modify Curator's Workbench for our purposes (FACADE){color}
** Who is responsible for loading data into or exporting data out from filemaker databases - {color:#990033}Carl{color}
** Who maintains DSpace Images (puts stuff up there, takes stuff down, grants access rights)These are just the roles questions that impact me (RW), but I know that there are a number of tasks that have been done by a different person on each project. - {color:#990033}\[{color}{color:#990033}\[See file disposition workflow{color}\|LIBDOME:File disposition\]\]
----
<!--  /* Font Definitions */  @font-face 	{font-family:"Cambria Math"; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:roman; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face 	{font-family:Calibri; 	panose-1:2 15 5 2 2 2 4 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:swiss; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1073750139 0 0 159 0;}  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-parent:""; 	margin-top:0in; 	margin-right:0in; 	margin-bottom:10.0pt; 	margin-left:0in; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} .MsoChpDefault 	{mso-style-type:export-only; 	mso-default-props:yes; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} .MsoPapDefault 	{mso-style-type:export-only; 	margin-bottom:10.0pt; 	line-height:115%;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.0in 1.0in 1.0in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} -->

As technologies evolve pdf would not be the best way to display the images.&nbsp; We would need to go back to the original tiff files.&nbsp;

Non-prop&nbsp; software, wouldn’t require any legal breaks to preserve item

DSpace is creating a file format plan

Tiff files serve as our second copy and our master digital file.&nbsp;