<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.blsp-spelling-error
{mso-style-name:blsp-spelling-error;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1402363746;
mso-list-type:hybrid;
mso-list-template-ids:-1332966880 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Esther and everyone else<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I was about to send a reply which made the same point about Frameworks vs Processes – a Framework is something that provides a structure into which more detailed,
specific, processes can be fitted.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I agree that a Framework would be what we should aim for initially if we want something that is<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Doable in the time available (a couple of years max) – bearing in mind the time that OAIS and ISO 16363 took!<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Is widely applicable – bearing in mind that there will be so many details which are different when one moves from one domain to another.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">That was the purpose behind the simplified spreadsheet.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The Process model(s) would follow on and may be several separate documents tailored to different domains.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hence the plan for more detailed spreadsheets<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">With regard to preservation activities vs other activities – I think it is a useful distinction in that the preservation activities seem to me to be reasonably
general at all but the most detailed levels whereas the other activities are, at all but the highest levels, very disparate. However I agree with Esther that even the simplified spreadsheet does mention many different things – however this is only at a high
level and really only in order to provide a context for the preservation activities.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">By the way, is there a telecom of any sort today?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">..David<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Conway, Esther (STFC,RAL,RALSP)
<br>
<b>Sent:</b> 25 March 2015 12:36<br>
<b>To:</b> John Garrett; Giaretta, David (STFC,RAL,RALSP); moims-dai@mailman.ccsds.org<br>
<b>Cc:</b> Daniele.Boucon@cnes.fr; donaldcarolann@me.com; tahoe_mike@sbcglobal.net; rdowns@ciesin.columbia.edu; sawyer@acm.org<br>
<b>Subject:</b> some useful definitions<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Hi All,<br>
<br>
I thought it myself be usefull to circulate some useful definitions of the different models we are looking (mostly pulled from web in a hurry but usefull to base discussions around)<br>
<br>
.......................................................<br>
A <b>workflow</b> consists of an orchestrated and repeatable pattern of business activity enabled by the systematic organization of resources into processes that transform materials, provide services, or process information.[1] It can be depicted as a sequence
of operations, declared as work of a person or group,[2] an organization of staff, or one or more simple or complex mechanisms.<br>
<br>
>From a more abstract or higher-level perspective, workflow may be considered a view or representation of real work.[3] The flow being described may refer to a document, service or product that is being transferred from one step to another.[4]<br>
<br>
So what we have from<b> LTDP </b>is a domain specific <b>workflow</b> the stages of which can be abstracted into a
<b>Framework </b><br>
.......................................................<br>
<br>
A Framework is a structure, a logical way to classify, segment, categorize, or maintain something.
<br>
Frameworks are by definition a little loose. They exist to provide structure and direction on a preferred way to do something without being too detailed or rigid. In essence, frameworks provide guidelines. They are powerful because they provide guidance while
being flexible enough to adopt to changing conditions or to be customized for your company while utilizing vetted approaches.
<o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">The Idea
<span class="blsp-spelling-error">Lifecycle</span> Matrix mentioned is an example of a framework and is very loose adoption of the more well known
<a href="http://en.wikipedia.org/wiki/Capability_Maturity_Model">Capability Maturity Model</a> or
<a href="http://tladictionary.com/index.php?title=C#CMM"><span class="blsp-spelling-error">CMM</span></a>. Truthfully you probably won’t be that rigid about your ideas but it was meant to be an applicable example.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><br>
...............................................................<br>
<br>
Processes are probably the easiest to understand since we all work with them daily, even when we don’t know it. A process is simply a well defined set of steps and decisions points for executing a specific task. Well planned and deeply understood processes
are essential to your ability to automate business tasks (our archival tasks). This is really where that magic happens, a the process level. Generally speaking, processes are highly repeatable and if it can be repeated it can be automated (with exceptions
or occasional human intervention of course).<br>
<br>
We do need to go to this level to produce something which can be practically implemeted (good stuff fro H2020 or Belmount Forum type Bid)<br>
<br>
Best Regards<br>
<br>
Esther <br>
<br>
<br>
<br>
<br>
<br>
<br>
________________________________________<br>
From: Conway, Esther (STFC,RAL,RALSP)<br>
Sent: 24 March 2015 15:16<br>
To: John Garrett; Giaretta, David (STFC,RAL,RALSP); <a href="mailto:moims-dai@mailman.ccsds.org">
moims-dai@mailman.ccsds.org</a><br>
Cc: <a href="mailto:Daniele.Boucon@cnes.fr">Daniele.Boucon@cnes.fr</a>; <a href="mailto:donaldcarolann@me.com">
donaldcarolann@me.com</a>; <a href="mailto:tahoe_mike@sbcglobal.net">tahoe_mike@sbcglobal.net</a>;
<a href="mailto:rdowns@ciesin.columbia.edu">rdowns@ciesin.columbia.edu</a>; <a href="mailto:sawyer@acm.org">
sawyer@acm.org</a><br>
Subject: Framework vs Process Models<br>
<br>
Hi All,<br>
<br>
Did a lot of thinking last night .Just a couple of thought in relation to the terminolgy we are using and the structure of the spreadsheet.<br>
<br>
The spreadsheet contain stages , actors, activities , output , standards , actuvities use cases<br>
<br>
<br>
The spreadsheet while bring a extra of clarity I think is mashing a number of concepts that of a Framework , Process Model and Activity Model/Systems Use Case<br>
<br>
The Stages and Standards support an approach to createing and Extended OAIS Framework supported by standards<br>
<br>
Inputs Activies Outputs , in conjuction with Actors as decision makers support the creation of a Process model ( which I could adapt a BPM methododlogy to do ).<br>
<br>
Actors and Activities can be used to develop activity model and/or systems use case<br>
<br>
<br>
This is evidenced by the change of name from ICLP to ILF . Problems are going to arise becuse processes will cross Framwork stages . This became quite clear to last night as I was trying to forces models input in stages where the stage divides do not naturally
exist . Also what relation actors have to and why differentiate between activities and preservation activities(doesnt make a lot of sense in modelling terms,<br>
<br>
Would suggest a decision needs to clearly to be made as to whether we are devleoping a Framwork or Proceess, We amay wind up in a mess if we try to to mash the two togher.<br>
<br>
I get the feeling that Mike is focussing on lifecysle stage and framework standard, and I have been doing a lot of detailed process stuff as evidenced by the very detailed document I sent round last night which only covered the process input aspects.<br>
<br>
However this isn't nescessarily a problem as a group there is natiral realtionship and progression between these things. Forcing me look things from a framework point of view has aleeady caused me to adapt the CEDA/LTDP process models<br>
<br>
Lifecyle Curation Framework Model -----> Lifecycle Curation Process Model -----> Activity Model/Use Case (which will included active data mangement Planning functionality) ------> Systems Implementaion (where we can lock things into a Dynamic Data Management
tool which would include planning functionailty)<br>
<br>
This also means we can follow formal metgodolgies to develop these things . Whille I was keen to leap into the process stuff the natural jumping off point for us should be the frawork model. It also would give us little more to to gather intersested people
to enrich the group.<br>
<br>
Best Regards<br>
<br>
Esther<br>
<br>
<br>
________________________________________<br>
From: John Garrett [garrett@his.com]<br>
Sent: 24 March 2015 07:51<br>
To: Conway, Esther (STFC,RAL,RALSP); Giaretta, David (STFC,RAL,RALSP); <a href="mailto:moims-dai@mailman.ccsds.org">
moims-dai@mailman.ccsds.org</a><br>
Cc: <a href="mailto:Daniele.Boucon@cnes.fr">Daniele.Boucon@cnes.fr</a>; <a href="mailto:donaldcarolann@me.com">
donaldcarolann@me.com</a>; <a href="mailto:tahoe_mike@sbcglobal.net">tahoe_mike@sbcglobal.net</a>;
<a href="mailto:rdowns@ciesin.columbia.edu">rdowns@ciesin.columbia.edu</a>; <a href="mailto:sawyer@acm.org">
sawyer@acm.org</a><br>
Subject: RE: Expanded Spreadsheet Attached<br>
<br>
Hi,<br>
<br>
Apologies if this is a duplicate message.<br>
I tried to send it out at end of today's meeting, but I can't find it again<br>
so I don't think it made it out.<br>
<br>
Daniele and I continued work on the ILF Spreadsheet starting with David's<br>
simplified version and Ester's comments and the brief discussion at the<br>
telecon today.<br>
Tuesday discussions will focus on PAIS GB.<br>
We will be discussing ILF again on Wednesday.<br>
<br>
Live, Laugh, Love, and Work for Peace,<br>
-JOhn<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:esther.conway@stfc.ac.uk">esther.conway@stfc.ac.uk</a> [<a href="mailto:esther.conway@stfc.ac.uk">mailto:esther.conway@stfc.ac.uk</a>]<br>
Sent: Friday, March 20, 2015 10:51 AM<br>
To: <a href="mailto:david.giaretta@stfc.ac.uk">david.giaretta@stfc.ac.uk</a>; <a href="mailto:garrett@his.com">
garrett@his.com</a>; <a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a><br>
Cc: <a href="mailto:Daniele.Boucon@cnes.fr">Daniele.Boucon@cnes.fr</a>; <a href="mailto:donaldcarolann@me.com">
donaldcarolann@me.com</a>; <a href="mailto:tahoe_mike@sbcglobal.net">tahoe_mike@sbcglobal.net</a>;<br>
<a href="mailto:rdowns@ciesin.columbia.edu">rdowns@ciesin.columbia.edu</a>; <a href="mailto:sawyer@acm.org">
sawyer@acm.org</a><br>
Subject: RE: Expanded Spreadsheet Attached<br>
<br>
Hi All,<br>
<br>
I have added some commets to David's spreasheet (only about half way<br>
through , as only go this yesterday) in advance of todays ICLP process<br>
telecon<br>
<br>
Esther<br>
________________________________<br>
From: Giaretta, David (STFC,RAL,RALSP)<br>
Sent: 19 March 2015 17:10<br>
To: John Garrett; 'MOIMS DAI List'<br>
Cc: 'Boucon Daniele'; <a href="mailto:donaldcarolann@me.com">donaldcarolann@me.com</a>; 'Mike Martin'; Conway, Esther<br>
(STFC,RAL,RALSP); <a href="mailto:rdowns@ciesin.columbia.edu">rdowns@ciesin.columbia.edu</a>; 'Don Sawyer'<br>
Subject: RE: Expanded Spreadsheet Attached<br>
<br>
Apologies if I have misunderstood but I was confused about the things in the<br>
spreadsheet so I attach a simplified one which is, I think, domain<br>
independent. I tried to separate out the very specifically preservation<br>
related activities from the other activities.<br>
I think it maps to the more detailed things in the other spreadsheets.<br>
<br>
I hope this helps.<br>
<br>
..David<br>
<br>
From: John Garrett [<a href="mailto:garrett@his.com">mailto:garrett@his.com</a>]<br>
Sent: 11 March 2015 07:45<br>
To: 'MOIMS DAI List'<br>
Cc: 'Boucon Daniele'; <a href="mailto:donaldcarolann@me.com">donaldcarolann@me.com</a>; 'Mike Martin'; Conway, Esther<br>
(STFC,RAL,RALSP); Giaretta, David (STFC,RAL,RALSP);<br>
<a href="mailto:rdowns@ciesin.columbia.edu">rdowns@ciesin.columbia.edu</a>; 'Don Sawyer'<br>
Subject: RE: Expanded Spreadsheet Attached<br>
<br>
Hi,<br>
<br>
I'm attaching an updated version of the spreadsheet incorporating the<br>
updates from the LTDP Preservation Workflow v1.0. Updates to the LTDP<br>
sheets are identified in Blue. A couple comments/questions/updates from me<br>
are in Red.<br>
<br>
Live, Laugh, Love, and Work for Peace,<br>
-JOhn<br>
<br>
From: John Garrett [<a href="mailto:garrett@his.com">mailto:garrett@his.com</a>]<br>
Sent: Tuesday, March 10, 2015 4:01 AM<br>
To: 'MOIMS DAI List'<br>
Cc: 'Boucon Daniele'; 'donaldcarolann@me.com'; 'Mike Martin';<br>
'esther.conway@stfc.ac.uk'; 'david.giaretta@stfc.ac.uk';<br>
'rdowns@ciesin.columbia.edu'<br>
Subject: Expanded Spreadsheet Attached<br>
<br>
Hi,<br>
<br>
I've added sheets to the spreadsheet that record the activities, inputs and<br>
outputs according the current LTDP Process Workflow. Two sheets were added.<br>
The first is the content of the high-level figure. The second added sheet<br>
is the descriptions, inputs, and outputs detailing the phase activities.<br>
<br>
We'll have to see if this format is helpful to us as we try to harmonize our<br>
efforts with theirs.<br>
<br>
I think some work could be done assigning activities identified in by LTDP<br>
to our phases so we can generate a crosswalk between our views. We could<br>
also look at the inputs and outputs from LTDP and try to decide where they<br>
show up in our framework.<br>
<br>
Live, Laugh, Love, and Work for Peace,<br>
-JOhn<o:p></o:p></span></p>
</div>
</div>
</body>
</html>