<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://jhagmann.twoday.net/rss2html.xsl" type="text/xsl"?>
<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:cc="http://web.resource.org/cc/"
  xmlns="http://purl.org/rss/1.0/"
> 

  <channel rdf:about="http://jhagmann.twoday.net/">
    <title>Records Mgmt  &amp; Archiving : Rubrik:Definitions</title>
    <link>http://jhagmann.twoday.net/</link>
    <description></description>
    <dc:publisher>jhagmann</dc:publisher>
    <dc:creator>jhagmann</dc:creator>
    <dc:date>2008-08-18T11:26:51Z</dc:date>
    <dc:language>en</dc:language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <sy:updateBase>2000-01-01T00:00:00Z</sy:updateBase>
    
    <image rdf:resource="http://static.twoday.net/icon.gif" />
    <items>
      <rdf:Seq>
            <rdf:li rdf:resource="http://jhagmann.twoday.net/stories/5130169/" />
            <rdf:li rdf:resource="http://jhagmann.twoday.net/stories/4589701/" />
            <rdf:li rdf:resource="http://jhagmann.twoday.net/stories/4269557/" />
            <rdf:li rdf:resource="http://jhagmann.twoday.net/stories/3765480/" />
            <rdf:li rdf:resource="http://jhagmann.twoday.net/stories/3714059/" />
            <rdf:li rdf:resource="http://jhagmann.twoday.net/stories/2301785/" />
            <rdf:li rdf:resource="http://jhagmann.twoday.net/stories/2264096/" />
            <rdf:li rdf:resource="http://jhagmann.twoday.net/stories/2258030/" />
            <rdf:li rdf:resource="http://jhagmann.twoday.net/stories/1351350/" />
            <rdf:li rdf:resource="http://jhagmann.twoday.net/stories/1348465/" />

      </rdf:Seq>
    </items>
  </channel>

  <image rdf:about="http://static.twoday.net/icon.gif">
    <title>Records Mgmt  &amp; Archiving</title>
    <url>http://static.twoday.net/icon.gif</url>
    <link>http://jhagmann.twoday.net/</link>
  </image>

  <item rdf:about="http://jhagmann.twoday.net/stories/5130169/">
    <title>Online dictionary for library &amp; information science</title>
    <link>http://jhagmann.twoday.net/stories/5130169/</link>
    <description>Good reference:&lt;br /&gt;
ODLIS: Online Dictionary for Library and Information Science was created by Joan M. Reitz, Associate Librarian for Instruction at the Ruth A. Haas Library, Western Connecticut State University (WCSU) in Danbury, CT. Ms. Reitz holds a B.A. degree (1972) from Reed College in Portland, Oregon; an M.L.I.S. degree (1991) from the University of Washington, Seattle; and an M.A. degree (1998) in European History from Western Connecticut State University. Her primary academic interests are the history of the book and publishing, the history of political and social revolutions, and art history. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Go to:&lt;br /&gt;
&lt;a href=&quot;http://lu.com/odlis/search.cfm&quot;&gt;http://lu.com/odlis/search.cfm&lt;/a&gt;</description>
    <dc:creator>jhagmann</dc:creator>
    <dc:subject>&lt;a href=&quot;http://jhagmann.twoday.net/topics/Definitions&quot;&gt;Definitions&lt;/a&gt;</dc:subject>
    <dc:rights>Copyright &#169; 2008 jhagmann</dc:rights>
    <dc:date>2008-08-18T11:22:00Z</dc:date>
  </item>
  <item rdf:about="http://jhagmann.twoday.net/stories/4589701/">
    <title>Data, documents, records</title>
    <link>http://jhagmann.twoday.net/stories/4589701/</link>
    <description>New York State has published a &quot;Request for public comment&quot; (RFPC) - for&lt;br /&gt;
A study concerning electronic record policy for New York State. Electronic records &lt;br /&gt;
&lt;br /&gt;
Interesting definitions: data, documents, records&lt;br /&gt;
&lt;br /&gt;
Terminology - Electronic &quot;Records&quot;:&lt;br /&gt;
&lt;br /&gt;
Concerning a similar survey, the State of Minnesota CIO recently noted that the &quot;terms &apos;records&apos;, &apos;data&apos;, and &apos;documents&apos; are often used interchangeably; the [Minnesota law requiring an e-records study] uses &apos;documents&apos; and &apos;data&apos; without distinguishing the two. But all of these terms have a separate legal meaning and significance in Minnesota, so it will be important to understand the exact distinctions any respondent makes in this survey.&quot;&lt;br /&gt;
&lt;br /&gt;
This observation is equally true in New York State: words such as electronic &quot;data&quot; and &quot;records&quot; are terms of art with specific legal definitions. To avoid confusion, survey respondents are asked to please keep in mind the following basic distinctions. In this study and in the survey, the term:&lt;br /&gt;
&lt;br /&gt;
* &lt;b&gt;Electronic &quot;data&quot;&lt;/b&gt; will be conceptualized as electronic &quot;information, evidencing any act, transaction, occurrence, event, or other activity.&quot; (NYS Technology Law § 302, the Electronic Signatures and Records Act or &quot;ESRA&quot;); &lt;br /&gt;
* &lt;b&gt;Electronic &quot;documents&quot;&lt;/b&gt; will be conceptualized as the &quot;physical embodiment of information or ideas&quot; (Black&apos;s Law Dictionary) within electronic &quot;forms [which are] perceptible by human sensory capabilities.&quot; (ESRA); &lt;br /&gt;
* &lt;b&gt;Electronic &quot;records&quot; &lt;/b&gt;will be conceptualized as being created when electronic data is &quot;produced or stored by electronic means and accurately reproducible&quot; (ESRA) as required; and &lt;br /&gt;
* &lt;b&gt;Electronic copies of &lt;/b&gt;&quot;official [government] records&quot; will be conceptualized also in accordance with their legal definition, as electronic records made &quot;in connection with the transaction of public business and preserved or appropriate for preservation by that agency or its legitimate successor as evidence of the organization, functions, policies, decisions, procedures, operations, or other activities, or because of the information contained therein.&quot; (The NYS Arts and Cultural Affairs Law § 57.05). &lt;br /&gt;
&lt;br /&gt;
In summary, e-data fills e-documents creating e-records, some of which represent official State agency e-records requiring preservation.  When being referred to inclusively and generically within this survey the term &quot;electronic records&quot; will be used. In your responses to the survey, please be sure to indicate if your usage of any term other than electronic records carries any special meaning or has any special implications.&lt;br /&gt;
&lt;br /&gt;
see:&lt;br /&gt;
&lt;a href=&quot;http://www.oft.state.ny.us/oftnews/erecords-study.htm&quot;&gt;http://www.oft.state.ny.us/oftnews/erecords-study.htm&lt;/a&gt;</description>
    <dc:creator>jhagmann</dc:creator>
    <dc:subject>&lt;a href=&quot;http://jhagmann.twoday.net/topics/Definitions&quot;&gt;Definitions&lt;/a&gt;</dc:subject>
    <dc:rights>Copyright &#169; 2008 jhagmann</dc:rights>
    <dc:date>2008-01-07T06:58:00Z</dc:date>
  </item>
  <item rdf:about="http://jhagmann.twoday.net/stories/4269557/">
    <title>Taxonomie - Taxonomy (Begriff)</title>
    <link>http://jhagmann.twoday.net/stories/4269557/</link>
    <description>An der 2. nationalen Records Mgmt Konferenz in Zürich tauchte auch die Frage&lt;br /&gt;
nach dem Begriff und Wesen einer Taxonomie auf.&lt;br /&gt;
In der Regel handelt es sich im Bereich Records Mgmt um ein kontrolliertes Vokabular &lt;br /&gt;
für eine hierarchische Klassierung der Business Prozesse in einem Unternehmen &lt;br /&gt;
(business classification) zwecks Ordnung der unter den entsprechenden Geschäfts-&lt;br /&gt;
prozessen anfallenden Unterlagen (records).&lt;br /&gt;
Die Hierarchie folgt in der Regel dem Schema:&lt;br /&gt;
- Hauptprozess/Sub-Prozess&lt;br /&gt;
- Aktivität&lt;br /&gt;
- Aufgabe (task)&lt;br /&gt;
&lt;br /&gt;
vgl. wikipedia&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://de.wikipedia.org/wiki/Taxonomie&quot;&gt;http://de.wikipedia.org/wiki/Taxonomie&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
und english:&lt;br /&gt;
&lt;a href=&quot;http://en.wikipedia.org/wiki/Taxonomy&quot;&gt;http://en.wikipedia.org/wiki/Taxonomy&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
betr. Business classification schemes hat Jeff Morelli (UK) schon viel geleistet:&lt;br /&gt;
&lt;a href=&quot;http://www.jmcl.net/&quot;&gt;http://www.jmcl.net/&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
go to Link &quot;Records Management&quot; - and download:&lt;br /&gt;
Business Classification Schemes: Issues and Options&lt;br /&gt;
As published in Issue 124 February 2005 of the Records Management Society Bulletin&lt;br /&gt;
&lt;br /&gt;
s. auch:&lt;br /&gt;
&lt;a href=&quot;http://jhagmann.twoday.net/stories/3326734/&quot;&gt;http://jhagmann.twoday.net/stories/3326734/&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
und:&lt;br /&gt;
&lt;a title=&quot;&quot; href=&quot;http://jhagmann.twoday.net/files/Taxonomie-Last-oder-Chance/&quot;&gt;Taxonomie-Last-oder-Chance&lt;/a&gt; (pdf, 257 KB)&lt;br /&gt;
oder&lt;br /&gt;
&lt;a title=&quot;&quot; href=&quot;http://jhagmann.twoday.net/files/10-reasons-to-use-a-taxonomy/&quot;&gt;10-reasons-to-use-a-taxonomy&lt;/a&gt; (pdf, 60 KB)</description>
    <dc:creator>jhagmann</dc:creator>
    <dc:subject>&lt;a href=&quot;http://jhagmann.twoday.net/topics/Definitions&quot;&gt;Definitions&lt;/a&gt;</dc:subject>
    <dc:rights>Copyright &#169; 2007 jhagmann</dc:rights>
    <dc:date>2007-09-18T10:42:00Z</dc:date>
  </item>
  <item rdf:about="http://jhagmann.twoday.net/stories/3765480/">
    <title>Defining digital preservation (ALA)</title>
    <link>http://jhagmann.twoday.net/stories/3765480/</link>
    <description>Short&lt;br /&gt;
Medium&lt;br /&gt;
Long   Definition&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://blogs.ala.org/digipres.php&quot;&gt;http://blogs.ala.org/digipres.php&lt;/a&gt;</description>
    <dc:creator>jhagmann</dc:creator>
    <dc:subject>&lt;a href=&quot;http://jhagmann.twoday.net/topics/Definitions&quot;&gt;Definitions&lt;/a&gt;</dc:subject>
    <dc:rights>Copyright &#169; 2007 jhagmann</dc:rights>
    <dc:date>2007-05-24T19:21:00Z</dc:date>
  </item>
  <item rdf:about="http://jhagmann.twoday.net/stories/3714059/">
    <title>Glossary of Records and Information Management Terms, 3rd Ed. (ARMA)</title>
    <link>http://jhagmann.twoday.net/stories/3714059/</link>
    <description>Das unentbehrliche Glossar 3. Auflage ist da.&lt;br /&gt;
&lt;br /&gt;
ISBN-13: 978-1-931786-37-9 (ARMA International)&lt;br /&gt;
&lt;br /&gt;
ISBN-10: 1-931786-37-2 (ARMA International)&lt;br /&gt;
&lt;br /&gt;
Catalog No. A4759, soft cover, English, 38 pages, 2007&lt;br /&gt;
&lt;br /&gt;
35$ for members, 50$ for non-members&lt;br /&gt;
&lt;br /&gt;
see:&lt;br /&gt;
&lt;a href=&quot;http://www.arma.org/bookstore/productdetail.cfm?ProductID=2038&quot;&gt;http://www.arma.org/bookstore/productdetail.cfm?ProductID=2038&lt;/a&gt;</description>
    <dc:creator>jhagmann</dc:creator>
    <dc:subject>&lt;a href=&quot;http://jhagmann.twoday.net/topics/Definitions&quot;&gt;Definitions&lt;/a&gt;</dc:subject>
    <dc:rights>Copyright &#169; 2007 jhagmann</dc:rights>
    <dc:date>2007-05-11T07:45:00Z</dc:date>
  </item>
  <item rdf:about="http://jhagmann.twoday.net/stories/2301785/">
    <title>Definitionen: ECM - ILM - RM (part 3 - (e)RM)</title>
    <link>http://jhagmann.twoday.net/stories/2301785/</link>
    <description>Teil 3: ERM (e) Records  Management) &lt;br /&gt;
&lt;br /&gt;
- Akronym: Electronic/Enterprise Records Management&lt;br /&gt;
-  Alle Daten- und Unterlagen-Records werden angesprochen&lt;br /&gt;
-  Ansatz ist integrativ und selektiv über die horizontale und vertikale&lt;br /&gt;
Raumachse&lt;br /&gt;
- Ansatz ist logisch-organisatorisch, technisch&lt;br /&gt;
- Frontoffice (Applikationen) und Backoffice (RMS) werden auf&lt;br /&gt;
einander abgestimmt&lt;br /&gt;
- Herkunft: Archivistik, Schriftgutverwaltung&lt;br /&gt;
- Grösster Vorteil: logisch ausgereift&lt;br /&gt;
- Grösster Nachteil: nicht attraktiv, unterbewertet&lt;br /&gt;
&lt;br /&gt;
The system used to manage business records includes people [training], processes, rules [policies, Regelwerke], practices, and technologies, all of which must be managed and controlled to create trustworthiness (Flynn und Kahn, 2003)&lt;br /&gt;
&lt;br /&gt;
mit freundlicher Genehmigung von Peter Toebak: www.toebak.ch&lt;br /&gt;
Source: ILM  ECM  ERM. Vom Hype zur Umsetzung&lt;br /&gt;
und Nutzung - Fachseminar v. 19.4.06 Baden</description>
    <dc:creator>jhagmann</dc:creator>
    <dc:subject>&lt;a href=&quot;http://jhagmann.twoday.net/topics/Definitions&quot;&gt;Definitions&lt;/a&gt;</dc:subject>
    <dc:rights>Copyright &#169; 2006 jhagmann</dc:rights>
    <dc:date>2006-07-06T19:15:00Z</dc:date>
  </item>
  <item rdf:about="http://jhagmann.twoday.net/stories/2264096/">
    <title>Definitionen: ECM - ILM - RM (part 2 -  ILM)</title>
    <link>http://jhagmann.twoday.net/stories/2264096/</link>
    <description>Teil 2: ILM ( Information Lifecycle Management) &lt;br /&gt;
&lt;br /&gt;
Zitat: ILM bedeutet die Werthaltigkeit von Daten zu ermitteln (regelbasiert und weitgehend automatisch) und sie, je nachdem auf schnellen, aber teuren oder langsamen, aber dafür preisgünstigen Medien zu speichern und, wenn nicht mehr benötigt, zu entsorgen (BIT, 5-2005, S. 104)&lt;br /&gt;
-  Faktisch nur mechanische Parameter, Guillotine-Methode&lt;br /&gt;
- Datei hat bestimmtes Alter erreicht&lt;br /&gt;
- Datenmenge hat bestimmte Grösse erreicht&lt;br /&gt;
- Gewisse Wartezeit ist vergangen seit letzter Ordnerergänzung&lt;br /&gt;
- Nach Zeitplan, z.B. jeden Freitag&lt;br /&gt;
- Anzahl Zugriffe einer Periode liegt unter einem Schwellenwert&lt;br /&gt;
- Dublettenprüfung per Prüfsummenlogik&lt;br /&gt;
-  Sicherheit, Business Continuity&lt;br /&gt;
- Bessere Auslastung der Storage-Medien (Virtualisierung, transparente&lt;br /&gt;
Datenhaltung)&lt;br /&gt;
&lt;br /&gt;
Bewertung von ILM:&lt;br /&gt;
- Alle Informationsressourcen, Datenobjekte werden angesprochen&lt;br /&gt;
- Ansatz ist selektiv über die vertikale Zeitachse&lt;br /&gt;
- Ansatz ist vor allem technisch, infrastrukturell, logistisch&lt;br /&gt;
- Medien (RAID, Bandsysteme, optische Systeme) werden hierarchisch,&lt;br /&gt;
im Backoffice verbunden&lt;br /&gt;
- Herkunft: HRM (Hierarchical Storage Management)&lt;br /&gt;
- Grösster Vorteil: ergänzt ECM&lt;br /&gt;
- Grösster Nachteil: logisch unausgereift&lt;br /&gt;
&lt;br /&gt;
mit freundlicher Genehmigung von Peter Toebak: www.toebak.ch&lt;br /&gt;
Source: ILM  ECM  ERM. Vom Hype zur Umsetzung&lt;br /&gt;
und Nutzung - Fachseminar v. 19.4.06 Baden&lt;br /&gt;
&lt;br /&gt;
s. auch: Definitionen und Grundsätze  nach SNIA (Storag Networking Industry Association):&lt;br /&gt;
&lt;a href=&quot;http://www.snia-dmf.org/library/ILMFoundations-DataClassification.pdf&quot;&gt;http://www.snia-dmf.org/library/ILMFoundations-DataClassification.pdf&lt;/a&gt;</description>
    <dc:creator>jhagmann</dc:creator>
    <dc:subject>&lt;a href=&quot;http://jhagmann.twoday.net/topics/Definitions&quot;&gt;Definitions&lt;/a&gt;</dc:subject>
    <dc:rights>Copyright &#169; 2006 jhagmann</dc:rights>
    <dc:date>2006-06-29T19:02:00Z</dc:date>
  </item>
  <item rdf:about="http://jhagmann.twoday.net/stories/2258030/">
    <title>Definitionen: ECM - ILM - RM (part 1 - ECM)</title>
    <link>http://jhagmann.twoday.net/stories/2258030/</link>
    <description>Teil 1: ECM&lt;br /&gt;
&lt;br /&gt;
Zitate: Definitionen&lt;br /&gt;
Enterprise Content Management (ECM) is a new concept that emphasises&lt;br /&gt;
a single open CM system built on industry standards with two-way&lt;br /&gt;
connectors to other industry standard platforms and internal applications&lt;br /&gt;
such as CRM, ERP, collaborative working applications, e-mail, portals etc.&lt;br /&gt;
Es ist die best insurance policy for the investment (...) in CM, and the&lt;br /&gt;
only way to ensure that critical information and processes are available to be shared throughout the organisation, its customers, and suppliers (White Paper CM, DLM-Forum, 2002, S. 13)&lt;br /&gt;
&lt;br /&gt;
Statt separater Software-Interfaces für den Zugriff auf unterschiedlichen&lt;br /&gt;
Content ist der einfache, integrierte Zugriff über eine einzige Schnittstelle&lt;br /&gt;
gefragt, über die alle Repositories durchsucht werden können, gleichgültig von welchem Typ sie sind oder von welchem Anbieter sie stammen (BIT, 6-2004, S. 55)&lt;br /&gt;
&lt;br /&gt;
Bewertung von ECM:&lt;br /&gt;
- Alle Informationsressourcen, Datenobjekte werden angesprochen&lt;br /&gt;
(Suchen und Zugreifen, Sicherheit, Zugriffssteuerung, Rechteverwaltung)&lt;br /&gt;
- Ansatz ist integrativ über die horizontale Raumachse&lt;br /&gt;
- Ansatz ist vor allem technisch, infrastrukturell (unternehmensweite Skalierbarkeit und Ausbau, Offenheit nach (Fremd-)Systemen und Repositories über veröffenlichten APIs, open-enterprise platform)&lt;br /&gt;
- Applikationen bleiben als Einzelsysteme funktionieren, werden nur&lt;br /&gt;
oberflächlich, im Frontoffice verknüpft&lt;br /&gt;
- Herkunft: Internet-, Intranet-Technik, Portalgedanke (Personalisierung&lt;br /&gt;
und Präsentation mittels Standard-Browser)&lt;br /&gt;
- Grösster Vorteil: integrativer Gedanke&lt;br /&gt;
- Grösster Nachteil: logisch unausgereift&lt;br /&gt;
&lt;br /&gt;
mit freundlicher Genehmigung von Peter Toebak: www.toebak.ch&lt;br /&gt;
Source: ILM  ECM  ERM. Vom Hype zur Umsetzung&lt;br /&gt;
und Nutzung - Fachseminar v. 19.4.06 Baden</description>
    <dc:creator>jhagmann</dc:creator>
    <dc:subject>&lt;a href=&quot;http://jhagmann.twoday.net/topics/Definitions&quot;&gt;Definitions&lt;/a&gt;</dc:subject>
    <dc:rights>Copyright &#169; 2006 jhagmann</dc:rights>
    <dc:date>2006-06-28T20:03:00Z</dc:date>
  </item>
  <item rdf:about="http://jhagmann.twoday.net/stories/1351350/">
    <title>Compliance Costs Affect Funding for E-Records Management</title>
    <link>http://jhagmann.twoday.net/stories/1351350/</link>
    <description>In a recent article in Line56, Colman Murphy of Xerox points out an important truth about the spike in compliance-oriented projects: &quot;Amidst all this spending, funding for electronic records management (ERM) initiatives has lagged.&quot;  Many companies are following the letter of laws like Sarbanes-Oxley, but still failing to implement any reasonable semblance of a true records management program.&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://www.arma.org/news/enewsletters/index.cfm?ID=1066&quot;&gt;http://www.arma.org/news/enewsletters/index.cfm?ID=1066&lt;/a&gt;</description>
    <dc:creator>jhagmann</dc:creator>
    <dc:subject>&lt;a href=&quot;http://jhagmann.twoday.net/topics/Definitions&quot;&gt;Definitions&lt;/a&gt;</dc:subject>
    <dc:rights>Copyright &#169; 2006 jhagmann</dc:rights>
    <dc:date>2006-01-02T20:22:57Z</dc:date>
  </item>
  <item rdf:about="http://jhagmann.twoday.net/stories/1348465/">
    <title>Specifications, Certifications, and Compliance: There is a Difference</title>
    <link>http://jhagmann.twoday.net/stories/1348465/</link>
    <description>Certifications are more than specifications&lt;br /&gt;
&lt;br /&gt;
Some people co-equate specifications and certifications, but in fact, certifications go beyond defining a standard or set of specifications. Certification bodies use specifications as a set of criteria for testing and qualifying vendors and other parties as compliant with the set of defined specifications. Certification implies both a rigorous set of specifications together with a rigorous testing procedure and set process for demonstrating a product&apos;s worthiness to be certified.&lt;br /&gt;
&lt;br /&gt;
more ...&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;http://www.cmswatch.com/Feature/136-Records-Management&quot;&gt;http://www.cmswatch.com/Feature/136-Records-Management&lt;/a&gt;</description>
    <dc:creator>jhagmann</dc:creator>
    <dc:subject>&lt;a href=&quot;http://jhagmann.twoday.net/topics/Definitions&quot;&gt;Definitions&lt;/a&gt;</dc:subject>
    <dc:rights>Copyright &#169; 2006 jhagmann</dc:rights>
    <dc:date>2006-01-02T15:24:05Z</dc:date>
  </item>


<textinput rdf:about="http://jhagmann.twoday.net/search">
   <title>find</title>
   <description>Search this site:</description>
   <name>q</name>
   <link>http://jhagmann.twoday.net/search</link>
</textinput>


</rdf:RDF>
