https://coptr.digipres.org/api.php?action=feedcontributions&user=Danielle+Plumer&feedformat=atomCOPTR - User contributions [en-gb]2024-03-28T09:17:02ZUser contributionsMediaWiki 1.35.14https://coptr.digipres.org/index.php?title=Archivematica&diff=2613Archivematica2015-02-13T23:57:08Z<p>Danielle Plumer: </p>
<hr />
<div>{{Infobox_tool<br />
|purpose=Archivematica is a digital preservation system that automates the process of preparing digital objects for ingest into a repository and an access system<br />
|image=<br />
|homepage=https://www.archivematica.org<br />
|license=<br />
|platforms=<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Preservation System]]<br />
[[Category:File Format Migration]]<br />
<br />
= Description =<br />
Archivematica is a digital preservation system that automates the process of preparing digital objects for ingest into a repository and an access system, ingesting them into archival storage and providing access to the archived material as well as uploading access copies to an access system. The process is monitored and controlled through a Web-based dashboard that co-ordinates a suite of micro-services. It relies on normalisation with preservation as the original object and comprehensive PREMIS metadata in METS.xml as its primary preservation technique.<br />
====Provider====<br />
This project is managed by [http://artefactual.com/archivematica.html Artefactual Systems. It began in collaboration with the UNESCO Memory of the World&#39;s [http://portal.unesco.org/ci/en/ev.php-URL_ID=1720&amp;URL_DO=DO_TOPIC&amp;URL_SECTION=201.html Subcommittee on Technology], the [http://vancouver.ca/ctyclerk/archives/ City of Vancouver Archives], but continues active development along with its partners at the [http://diginit.library.ubc.ca/ University of British Columbia Library], the [http://rockarch.org/ Rockefeller Archive Center], [http://www.sfu.ca/archives/ Simon Fraser University Archives and Records Management], [http://web.library.yale.edu/ Yale University Libraries] and a number of other collaborators.<br />
====Licensing and cost====<br />
The Archivematica code is released under the [http://www.gnu.org/licenses/agpl.html AGPL version 3.] The code is on [https://github.com/artefactual GitHub] and the tool may be downloaded and used free of charge.<br />
====Development activity====<br />
1.0 (September 2013 / packages December 2014)) is the first production (non-beta) version of the software. The source code for the tool is available from [https://github.com/artefactual/archivematica GitHub].<br />
====Platform and interoperability====<br />
Archivematica may be installed directly on a Linux system, and specifically targets Long Term Support releases of the Xubuntu operating system.<br />
Support is included for using Archivematica as a preservation backend for DSpace, a front end for CONTENTdm access, a front end for LOCKSS storage, and a front end for access using [https://www.accesstomemory.org/en/ AtoM], which comes bundled with the software.<br />
====Functional notes====<br />
Archivematica uses a micro-services approach, which means it acts as a wrapper for many task-specific applications such as the BagIt library, Clam Anti-Virus, DigiKam, FFmpeg, FITS (File Information Tool Set), ImageMagick, Inkscape, OpenOffice.org, and 7-Zip.<br />
The typical workflow is for the curator to assemble a transfer package in the filesystem: a script is provided for setting up the right folder structure or the structure can be assembled manually for some workflows, then digital objects are added to one folder and contextual information (submission documentation in the form of e.g. transfer forms, donation agreements) to another. The package is moved to an input folder &#39;watched&#39; by the main Archivematica Web tool. Through the Web interface, the curator can decide to accept or reject the transfer. If the transfer is accepted, the tool performs an initial analysis &ndash; calculating checksums, assigning UUIDs, scanning for viruses, identifying formats, extracting metadata &ndash; and then offers to create a Submission Information Package (SIP); it is also possible to create one or more SIPs manually. Metadata (simple Dublin Core and PREMIS 2.0 rights/restrictions) can then be added to the SIP before it is ingested. At ingest, the curator can choose various routes such as Preservation (where the digital objects are normalised to archival formats and transformed into an Archival Information Package, or AIP), Access (where the digital objects are normalised to dissemination formats and transformed into a Dissemination Information Package, or DIP), repackaging without normalisation, or many combinations of the aforementioned. Further functions are provided for moving AIPs into archival storage and uploading DIPs to the Qubit access portal. Workflows and decision points are configurable via preconfiguration settins in the administration tab of the web-based dashboard.<br />
====Documentation and user support====<br />
The online [https://www.archivematica.org/wiki/Documentation documentation] for Archivematica includes a User and an Administrative Manual, a walkthrough tutorial, screencasts, a requirements specification (including use cases, activity diagrams, recognised significant properties of various media and media preservation plans) and a description of the technical architecture.<br />
Community support is available through the [http://groups.google.com/group/archivematica Archivematica Discussion Group]. Artefactual Systems, Inc., the primary developer of Archivematica, also offers [http://www.artefactual.com/services/archivematica/maintenance/ support options].<br />
<br />
====Usability====<br />
The majority of operations are accomplished through a simple Web-based graphical user interface. For some, such as the manual construction of Submission Information Packages, a graphical file management tool ([http://thunar.xfce.org/ Thunar] with additional scripts) is provided, though in future releases such tasks may be supported by the Web interface instead.<br />
Reports on the ease of installation and the robustness of the system are mixed but improving; see for example the experiences of [http://larchivista.blogspot.co.uk/2011/04/installing-archivematica.html Bonnie Weddle] and [http://e-records.chrisprom.com/evaluating-open-source-digital-preservation-systems-a-case-study-2/ Angela Jordan] with version 0.7, and [http://digital-archiving.blogspot.co.uk/2012/09/installing-archivematica-and-running.html Jenny Mitcham] with version 0.9.<br />
====Expertise required====<br />
The system is easy to use, though as it draws heavily on the [http://www.dcc.ac.uk/resources/briefing-papers/introduction-curation/using-oais-curation OAIS Reference Model] some familiarity with that model is needed to understand the workflows Archivematica supports. When installing directly on a Linux desktop or server, even if it is deployed in a virtual machine, a little technical expertise is required (e.g. for setting up ports correctly).<br />
<br />
====Standards compliance====<br />
The functionality of Archivematica is clearly based on that defined by the OAIS Reference Model. The Archival Information Packages generated by the system use the BagIt packaging format, in conjunction with a METS packaging manifest incorporating PREMIS metadata. Metadata entry is through the profile of Dublin Core used by ICA-AtoM (Qubit).<br />
====Influence and take-up====<br />
Archivematica is used by at least [https://www.archivematica.org/wiki/Community 30 organisations].<br />
<br />
= User Experiences =<br />
<br />
<br />
= Development Activity =<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=Archivematica<br />
}}<br />
<br />
====Activity Feed====<br />
Below the last 5 activity feeds:<br />
<rss max=5>https://github.com/artefactual/archivematica/commits/master.atom</rss></div>Danielle Plumerhttps://coptr.digipres.org/index.php?title=Rhash&diff=2611Rhash2015-02-13T00:55:31Z<p>Danielle Plumer: </p>
<hr />
<div><!-- Use the structure provided in this template, do not change it! --><br />
<br />
{{Infobox_tool<br />
|purpose=RHash (Recursive Hasher) is a console utility for computing and verifying hash sums of files. <br />
|image=Rhash.png <br />
|homepage=http://rhash.anz.ru/<br />
|license=Open Source MIT [http://rhash.anz.ru/license.php].<br />
|platforms=Cross platforms<br />
}}<br />
<!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --><br />
<br />
<!-- Add one or more categories to describe the function of the tool, such as:<br />
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]<br />
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --><br />
<br />
[[Category:Fixity]] <br />
<!-- Add relevant categories to describe the content type that the tool addresses, such as:<br />
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]<br />
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --><br />
<br />
<br />
== Description ==<br />
<!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --><br />
RHash (Recursive Hasher) is a console utility for computing and verifying hash sums of files. It supports CRC32, MD4, MD5, SHA1, SHA256, SHA512, Tiger, DC++ TTH, BitTorrent BTIH, ED2K, AICH, GOST R 34.11-94, RIPEMD-160, HAS-160, EDON-R 256/512, Whirlpool and Snefru-128/256 algorithms. Hash sums are used to ensure and verify integrity of large volumes of data for a long-term storing or transferring.<br />
* Can calculate Magnet links<br />
* Output in a predefined (SFV, BSD-like) or a user-defined format<br />
* Ability to process directories recursively<br />
* Updating existing hash-files (adding hash sums of files missing in a hash-file)><br />
* Portability: the program works the same under Linux, *BSD, Solaris or Windows<br />
* Written in pure C, small in size, open source<br />
<br />
== Documentation ==<br />
<br />
Use -h for the Help screen.<br />
* Getting started: http://sourceforge.net/p/rhash/wiki/Home/<br />
* Man page: http://rhash.anz.ru/manpage.php<br />
* Hash functions: http://rhash.anz.ru/hashes.php<br />
* Ubuntu rhash package (bugs page): https://bugs.launchpad.net/ubuntu/+source/rhash<br />
* Uninstalling rhash from PC: http://pcuninstalltool.com/articles/How-to-Uninstall/Remove-RHash-Completely-Off-Your-PC_24_116231.html<br />
<br />
== User Experiences ==<br />
<!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --><br />
<br />
== Development Activity ==<br />
<!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --><br />
<!-- Add the OpenHub.com ID for the tool, if known. --><br />
{{Infobox_tool_details<br />
|releases_rss=http://sourceforge.net/projects/rhash/rss?path=/<br />
|issues_rss=http://sourceforge.net/p/rhash/bugs/feed.rss<br />
|mailing_lists=https://www.openhub.net/p/rhash/rss_subscriptions<br />
|ohloh_id=rhash<br />
}}</div>Danielle Plumerhttps://coptr.digipres.org/index.php?title=Talk:Main_Page&diff=2558Talk:Main Page2015-02-05T03:00:26Z<p>Danielle Plumer: </p>
<hr />
<div>==Use of Level 1 section headings ==<br />
I just had a first stab at some editing an existing entry, and creating a new one. One small thing I noticed: all of the pages I've seen use Level 1 headings for the main sections, but this is discouraged by the MediaWiki documentation (esp. since Level 1 is already used for the main heading of each entry). See e.g. here:<br />
<br />
http://www.mediawiki.org/wiki/Help_talk:Formatting#Level_1<br />
<br />
And also:<br />
<br />
http://www.mediawiki.org/wiki/Help:Formatting<br />
<br />
So maybe it would be better to change those to level 2 (also in all cases I've seen the child sections use level 3 headings)? Not a big deal of course but it's a bit ugly and it's probably easier to fix this now than postponing it to a later stage (also existing entries will most likely be used as a template for creating new ones, so the problem will get progressively worse if left as it is). I suppose this is also something that might mess up attempts at automated text extraction. [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 14:58, 20 November 2013 (UTC)<br />
<br />
: Good point - I didn't know about this recommendation. It should be possible to automated this transformation using the [https://www.mediawiki.org/wiki/Manual:Pywikibot Pywikibot] framework and the [https://pypi.python.org/pypi/mwparserfromhell mwparserfromhell]. We could change the [[Template:Tool/Preload|tool template]] now and use a bot to modify the rest? [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 15:15, 20 November 2013 (UTC)<br />
<br />
::Great! It would also help to mention the template on the main page (I don't have edit rights there), as I didn't even know there was any! Anyway, I just updated the template myself.[[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 16:07, 20 November 2013 (UTC)<br />
<br />
::: I updated the main page to include an explicit link to the template that should be used when creating new Tool entries. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]])<br />
<br />
==Purpose field in infobox==<br />
Another thing I noticed is that for most entries the ''purpose'' field in the infobox more or less repeats what's already in the ''Description'' section. So maybe it's better to leave it out altogether (on the other hand it might be useful for automated discovery/analysis)? [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 14:58, 20 November 2013 (UTC)<br />
: The intention was the other way around - that the 'purpose' field was a brief description that might be published and re-used in other forms (due to being in the infobox), and the Description section should be more detailed. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 15:15, 20 November 2013 (UTC)<br />
:: Yes, that's what I thought as well. For some existing entries both are identical though, so it wasn't immediately clear. [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 15:56, 20 November 2013 (UTC)<br />
::: I would say the goal is to improve the body Description section for those items. Is the Description in these cases exactly identical to the purpose? If so, I might be able to check for that automatically. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 21:18, 20 November 2013 (UTC)<br />
<br />
==Perhaps rename Imaging category to Disk Imaging?==<br />
Another thing: people might end up mixing up the ''Image'' and ''Imaging'' categories. Maybe rename the latter to ''Disk Imaging'' to avoid this?<br />
[[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 16:15, 20 November 2013 (UTC)<br />
: Good idea. Unfortunately, I think that due to the way MediaWiki works, this means editing all the items tagged with that category (unless there's a trick I'm unaware of). However, perhaps I should tweak [[User:COPTR Bot|COPTR Bot]] to do this too. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 21:22, 20 November 2013 (UTC)<br />
:: Fixed manually --[[User:Prwheatley|Prwheatley]] ([[User talk:Prwheatley|talk]]) 17:51, 26 November 2013 (UTC)<br />
<br />
==Problems with login procedure (VeriSign)==<br />
Having created an OpenID with Verisign, signing in to COPTR is a bit hit and miss. It always takes multiple attempts before I can successfully log in, and I first have to work myself through multiple authorization errors. Not clear to me whether the error is caused by COPTR or VeriSign, and results seem to be a bit random. Also after some time of inactivity I seem to get logged out automatically. Confusingly, the COPTR login status at the top right then shows I'm still logged in (depending on which page I'm on, it seems), and I have to go through the whole login procedure (including failures) again. <br />
[[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 11:16, 21 November 2013 (UTC)<br />
<br />
: [http://meta.stackoverflow.com/a/1789 This StackOverflow answer] outlines some of the possible causes of problems with OpenID logins. I guess we could perhaps enable non-OpenID logins, although I wanted to avoid that for fear of making it even easier for the robots/spammers. Using Google as an OpenID provider is working fine for me. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 11:40, 21 November 2013 (UTC)<br />
<br />
:: Hmm ... the StackOverflow page links to an OpenID checker, but I'm a bit scared of it because it exposes all the info you enter there to a publicly viewable log ... Not keen on using Google either, because they're, well ... Google. The main point of course is that the success of COPTR will depend completely on community involvement, and if the login procedure is already such a stumbling block that's not going to help there. Also the procedure to get the OpenID isn't terribly straightforward, and this will scare off potential contributors as well. So I would consider adding a non-OpenID login procedure, perhaps augmented with a CAPTCHA to keep the robots at bay (e.g. like the Archiveteam Formats Wiki). [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 12:28, 21 November 2013 (UTC)<br />
<br />
::: Okay, I've enabled plain logins and registration. To make sure you retain the same user account, you should ensure it knows the right email address so you can use password recovery to login. Alternatively, I think you should be able to reset your PW from your Preferences page. The current setup is that you should see CAPTCHAs blocking all edits etc. unless you have confirmed your email address. We'll see how it goes, and if we have to tighten up things to avoid spam, so be it. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 12:45, 21 November 2013 (UTC)<br />
<br />
::::Great, thanks for the quick response! Apparently there's no way to set a pw from the Preferences page once you have an existing OpenID assigned to your user profile, and when I try to delete my OpenID I get an error that this isn't possible because no password is set, classic Catch 22 there! Anyway, I'll stick with the OpenID madness for a bit and if I get really fed up with it I may well just create a new COPTR account, probably the easiest solution all around. [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 13:14, 21 November 2013 (UTC)<br />
<br />
::::: I'm pretty sure that, if you completely log out first, and if there is an email associated with your account, you can use the 'Password reset' option to get access. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 15:28, 21 November 2013 (UTC)<br />
<br />
== changing Open Planets Foundation to Open Preservation Foundation ==<br />
<br />
Hi. The Main Page need some update (changing Open Planets Foundation to Open Preservation Foundation). I have of course not the permission to do that :-) . Thanks. [[User:Chlara|Chlara ]] ([[User talk:Chlara|talk]]) 10:18, 27 November 2014 (UTC)<br />
* Good call, this is now fixed. Thanks!<br />
<br />
== DSPS (Digital Preservation Software Platform) is the same as Digital Preservation Software Platform ==<br />
<br />
Hi. I have updated the Digital Preservation Software Platform. After that I saw that there is a nearly same Page DSPS (Digital Preservation Software Platform). Due to the fact, that "DSPS (Digital Preservation Software Platform)" is the better title I have copied the content from Digital Preservation Software Platform into DSPS (Digital Preservation Software Platform). In the Page Digital Preservation Software Platform I replaced the content with a link to DSPS (Digital Preservation Software Platform). <br />
<br />
Can you please delete the page Digital Preservation Software Platform.<br />
<br />
Thanks. [[User:Chlara|Chlara ]] ([[User talk:Chlara|talk]]) 11:30, 8 January 2015 (UTC)<br />
<br />
== Merging duplicate entries ==<br />
<br />
I noticed that there are two entries for the CONTENTdm digital asset management system:<br />
<br />
* http://coptr.digipres.org/ContentDM<br />
* http://coptr.digipres.org/CONTENTdm<br />
<br />
I removed the limited content from the ContentDM page and made it redirect to the CONTENTdm page, using the MediaWiki #redirect option (see [http://www.mediawiki.org/wiki/Help:Redirects http://www.mediawiki.org/wiki/Help:Redirects]. Should this be the recommended practice or would you rather simply delete one of the pages? If the latter, how to we request removal of a page?<br />
<br />
[[User:Danielle Plumer|Danielle Plumer]] ([[User talk:Danielle Plumer|talk]]) 03:00, 5 February 2015 (UTC)</div>Danielle Plumerhttps://coptr.digipres.org/index.php?title=Talk:Main_Page&diff=2557Talk:Main Page2015-02-05T02:56:07Z<p>Danielle Plumer: /* Merging duplicate entries */ new section</p>
<hr />
<div>==Use of Level 1 section headings ==<br />
I just had a first stab at some editing an existing entry, and creating a new one. One small thing I noticed: all of the pages I've seen use Level 1 headings for the main sections, but this is discouraged by the MediaWiki documentation (esp. since Level 1 is already used for the main heading of each entry). See e.g. here:<br />
<br />
http://www.mediawiki.org/wiki/Help_talk:Formatting#Level_1<br />
<br />
And also:<br />
<br />
http://www.mediawiki.org/wiki/Help:Formatting<br />
<br />
So maybe it would be better to change those to level 2 (also in all cases I've seen the child sections use level 3 headings)? Not a big deal of course but it's a bit ugly and it's probably easier to fix this now than postponing it to a later stage (also existing entries will most likely be used as a template for creating new ones, so the problem will get progressively worse if left as it is). I suppose this is also something that might mess up attempts at automated text extraction. [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 14:58, 20 November 2013 (UTC)<br />
<br />
: Good point - I didn't know about this recommendation. It should be possible to automated this transformation using the [https://www.mediawiki.org/wiki/Manual:Pywikibot Pywikibot] framework and the [https://pypi.python.org/pypi/mwparserfromhell mwparserfromhell]. We could change the [[Template:Tool/Preload|tool template]] now and use a bot to modify the rest? [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 15:15, 20 November 2013 (UTC)<br />
<br />
::Great! It would also help to mention the template on the main page (I don't have edit rights there), as I didn't even know there was any! Anyway, I just updated the template myself.[[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 16:07, 20 November 2013 (UTC)<br />
<br />
::: I updated the main page to include an explicit link to the template that should be used when creating new Tool entries. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]])<br />
<br />
==Purpose field in infobox==<br />
Another thing I noticed is that for most entries the ''purpose'' field in the infobox more or less repeats what's already in the ''Description'' section. So maybe it's better to leave it out altogether (on the other hand it might be useful for automated discovery/analysis)? [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 14:58, 20 November 2013 (UTC)<br />
: The intention was the other way around - that the 'purpose' field was a brief description that might be published and re-used in other forms (due to being in the infobox), and the Description section should be more detailed. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 15:15, 20 November 2013 (UTC)<br />
:: Yes, that's what I thought as well. For some existing entries both are identical though, so it wasn't immediately clear. [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 15:56, 20 November 2013 (UTC)<br />
::: I would say the goal is to improve the body Description section for those items. Is the Description in these cases exactly identical to the purpose? If so, I might be able to check for that automatically. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 21:18, 20 November 2013 (UTC)<br />
<br />
==Perhaps rename Imaging category to Disk Imaging?==<br />
Another thing: people might end up mixing up the ''Image'' and ''Imaging'' categories. Maybe rename the latter to ''Disk Imaging'' to avoid this?<br />
[[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 16:15, 20 November 2013 (UTC)<br />
: Good idea. Unfortunately, I think that due to the way MediaWiki works, this means editing all the items tagged with that category (unless there's a trick I'm unaware of). However, perhaps I should tweak [[User:COPTR Bot|COPTR Bot]] to do this too. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 21:22, 20 November 2013 (UTC)<br />
:: Fixed manually --[[User:Prwheatley|Prwheatley]] ([[User talk:Prwheatley|talk]]) 17:51, 26 November 2013 (UTC)<br />
<br />
==Problems with login procedure (VeriSign)==<br />
Having created an OpenID with Verisign, signing in to COPTR is a bit hit and miss. It always takes multiple attempts before I can successfully log in, and I first have to work myself through multiple authorization errors. Not clear to me whether the error is caused by COPTR or VeriSign, and results seem to be a bit random. Also after some time of inactivity I seem to get logged out automatically. Confusingly, the COPTR login status at the top right then shows I'm still logged in (depending on which page I'm on, it seems), and I have to go through the whole login procedure (including failures) again. <br />
[[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 11:16, 21 November 2013 (UTC)<br />
<br />
: [http://meta.stackoverflow.com/a/1789 This StackOverflow answer] outlines some of the possible causes of problems with OpenID logins. I guess we could perhaps enable non-OpenID logins, although I wanted to avoid that for fear of making it even easier for the robots/spammers. Using Google as an OpenID provider is working fine for me. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 11:40, 21 November 2013 (UTC)<br />
<br />
:: Hmm ... the StackOverflow page links to an OpenID checker, but I'm a bit scared of it because it exposes all the info you enter there to a publicly viewable log ... Not keen on using Google either, because they're, well ... Google. The main point of course is that the success of COPTR will depend completely on community involvement, and if the login procedure is already such a stumbling block that's not going to help there. Also the procedure to get the OpenID isn't terribly straightforward, and this will scare off potential contributors as well. So I would consider adding a non-OpenID login procedure, perhaps augmented with a CAPTCHA to keep the robots at bay (e.g. like the Archiveteam Formats Wiki). [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 12:28, 21 November 2013 (UTC)<br />
<br />
::: Okay, I've enabled plain logins and registration. To make sure you retain the same user account, you should ensure it knows the right email address so you can use password recovery to login. Alternatively, I think you should be able to reset your PW from your Preferences page. The current setup is that you should see CAPTCHAs blocking all edits etc. unless you have confirmed your email address. We'll see how it goes, and if we have to tighten up things to avoid spam, so be it. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 12:45, 21 November 2013 (UTC)<br />
<br />
::::Great, thanks for the quick response! Apparently there's no way to set a pw from the Preferences page once you have an existing OpenID assigned to your user profile, and when I try to delete my OpenID I get an error that this isn't possible because no password is set, classic Catch 22 there! Anyway, I'll stick with the OpenID madness for a bit and if I get really fed up with it I may well just create a new COPTR account, probably the easiest solution all around. [[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 13:14, 21 November 2013 (UTC)<br />
<br />
::::: I'm pretty sure that, if you completely log out first, and if there is an email associated with your account, you can use the 'Password reset' option to get access. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 15:28, 21 November 2013 (UTC)<br />
<br />
== changing Open Planets Foundation to Open Preservation Foundation ==<br />
<br />
Hi. The Main Page need some update (changing Open Planets Foundation to Open Preservation Foundation). I have of course not the permission to do that :-) . Thanks. [[User:Chlara|Chlara ]] ([[User talk:Chlara|talk]]) 10:18, 27 November 2014 (UTC)<br />
* Good call, this is now fixed. Thanks!<br />
<br />
== DSPS (Digital Preservation Software Platform) is the same as Digital Preservation Software Platform ==<br />
<br />
Hi. I have updated the Digital Preservation Software Platform. After that I saw that there is a nearly same Page DSPS (Digital Preservation Software Platform). Due to the fact, that "DSPS (Digital Preservation Software Platform)" is the better title I have copied the content from Digital Preservation Software Platform into DSPS (Digital Preservation Software Platform). In the Page Digital Preservation Software Platform I replaced the content with a link to DSPS (Digital Preservation Software Platform). <br />
<br />
Can you please delete the page Digital Preservation Software Platform.<br />
<br />
Thanks. [[User:Chlara|Chlara ]] ([[User talk:Chlara|talk]]) 11:30, 8 January 2015 (UTC)<br />
<br />
== Merging duplicate entries ==<br />
<br />
I noticed that there are two entries for the CONTENTdm digital asset management system:<br />
<br />
* http://coptr.digipres.org/ContentDM<br />
* http://coptr.digipres.org/CONTENTdm<br />
<br />
I removed the limited content from the ContentDM page and made it redirect to the CONTENTdm page, using the MediaWiki #redirect option (see [http://www.mediawiki.org/wiki/Help:Redirects http://www.mediawiki.org/wiki/Help:Redirects]. Should this be the recommended practice or would you rather simply delete one of the pages? If the latter, how to we request removal of a page?</div>Danielle Plumerhttps://coptr.digipres.org/index.php?title=CONTENTdm&diff=2556CONTENTdm2015-02-05T02:53:32Z<p>Danielle Plumer: </p>
<hr />
<div>{{Infobox_tool<br />
|purpose=CONTENTdm is a digital collection management system<br />
|image=<br />
|homepage=http://www.contentdm.org/<br />
|license=<br />
|platforms=<br />
}}<br />
<br />
<!-- Delete the Categories that do not apply --><br />
[[Category:Preservation System]]<br />
<br />
<br />
= Description =<br />
[http://www.contentdm.org/ CONTENTdm] is a software solution that handles the storage, management, and delivery of library digital collection to the web by providing access to web-based digital collection tool where data and digital items are prepared in large batches, a server where data and images are stored and can be edited, a Web-based discovery interface optimized for customization, self-service tool to upload the metadata of your digital content to WorldCat using the Digital Collection Gateway, and integration with OCLC products for building collections with cataloging workflows, as well as the option of harvesting from the Web sites and adding long-term preservation. Developed by OCLC. A hosted version is available.<br />
====Provider====<br />
OCLC<br />
====Licensing and cost====<br />
CONTENTdm uses fee-based licenses for both the software and the hosting service; a range of optional services and tools is available as well. Pricing is unclear on the OCLC website. &nbsp;<br />
====Development activity====<br />
CONTENTdm version 6.1 was released in October 2011.<br />
OCLC is a self-funded not-for-profit organisation; CONTENTdm is one of their core services, receiving ongoing development and support.<br />
====Platform and interoperability====<br />
CONTENTdm Server runs on IIS with Windows 2008 or Apache with Linux (requires PHP 5.3). The CONTENTdm website has similar requirements. The software was designed to integrate with other OCLC products, including Connexion and Web Harvester. The CONTENTdm Project Client requires the Microsoft .NET Framework 3.5 or higher running on Windows P SP2 or later.<br />
CONTENTdm offers an API to allow users to customise their workflows and extend website functionality.<br />
====Functional notes====<br />
Some licenses include an OCR Extension to generate full-text transcripts, and an Image Rights tool to designate ownership of items in the collection. The customisable web access platform integrates with OCLC&rsquo;s WorldCat to promote greater discoverability. Collections can be stored on distributed drives, enabling collaboration between organisations.<br />
====Documentation and user support====<br />
Email- and telephone-based user support is included in the licensing fee. Users are also granted access to a [http://www.oclc.org/contentdm/support/default.htm User Support Center] with installation guides, Help files, tutorials and a Support FAQ. The Center also supports forums and blogs for the CONTENTdm community.<br />
====Usability====<br />
CONTENTdm provides a web-based administration interface, and includes number of options for managing and adding content to collections. For its latest iteration, extensive usability testing was conducted as part of a user-centered design approach.<br />
====Expertise required====<br />
If an organisation wishes to host its own server, installation and configuration will require system administration knowledge.<br />
====Standards compliance====<br />
CONTENTdm heavily advertises its standards compliance in a number of arenas: supporting Unicode for character display; offering Dublin Core, VRA Core, and METS/ALTO for metadata assignment; serving as an OAI repository for those who wish to make their metadata available for harvesting; and supporting Z39.50 for search and retrieval.<br />
====Influence and take-up====<br />
The CONTENTdm website advertises use by over 2,000 organizations, including public libraries, academic libraries, historical societies, and museums.<br />
<br />
<br />
= User Experiences =<br />
<br />
<br />
= Development Activity =<br />
<br />
{{Infobox_tool_details<br />
|ohloh_id=CONTENTdm<br />
}}</div>Danielle Plumerhttps://coptr.digipres.org/index.php?title=ContentDM&diff=2555ContentDM2015-02-05T02:51:42Z<p>Danielle Plumer: Redirect page to CONTENTdm</p>
<hr />
<div>#REDIRECT [[CONTENTdm]]</div>Danielle Plumerhttps://coptr.digipres.org/index.php?title=Fslint&diff=2554Fslint2015-02-04T05:14:13Z<p>Danielle Plumer: </p>
<hr />
<div><!-- Use the structure provided in this template, do not change it! --><br />
<br />
{{Infobox_tool<br />
|purpose= Set of utilities to find and clean various forms of lint on a filesystem, such as duplicate files, empty directories, and bad file names.<br />
|image=Fslint_icon.png<br />
|homepage=http://www.pixelbeat.org/fslint/<br />
|license=GPL 2+<br />
|platforms=Linux<br />
}}<br />
<!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --><br />
<br />
<!-- Add one or more categories to describe the function of the tool, such as:<br />
or or [[Category:Backup]]<br />
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --><br />
[[Category:De-Duplication]]<br />
[[Category:File_Management]]<br />
<br />
<!-- Add relevant categories to describe the content type that the tool addresses, such as:<br />
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]<br />
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --><br />
<br />
== Description ==<br />
<!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --><br />
FSlint is a utility to find and clean various forms of unwanted extraneous files on a computer file system. This excess of unnecessary files is referred to as lint. FSlint will help find unwanted or problematic lint in your files or file names. The most common forms of lint FSlint finds are duplicate files, empty directories, and improper names. FSlint has multiple tools to perform a multitude of tasks in both the graphical interface and command line modes.<br />
<br />
There are a total of ten utilities available in both FSlint's graphical and command-line modes, plus two others (find and zipdir) that are available in command-line mode only:<br />
<br />
* findup - find DUPlicate files<br />
* findnl - find Name Lint (problems with filenames)<br />
* findu8 - find filenames with invalid utf8 encoding<br />
* findbl - find Bad Links (various problems with symlinks)<br />
* findsn - find Same Name (problems with clashing names)<br />
* finded - find Empty Directories<br />
* findid - find files with dead user IDs<br />
* findns - find Non Stripped executables<br />
* findrs - find Redundant Whitespace in files<br />
* findtf - find Temporary Files<br />
* findul - find possibly Unused Libraries<br />
* zipdir - Reclaim wasted space in ext2 directory entries<br />
<br />
FSlint is copyrighted 2000-2009 Padraig Brady, P@draigBrady.com. The program is free software and can be redistributed and/or modified under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or any later version.<br />
<br />
===Platform===<br />
FSlint can be found in the online repositories of several major Linux releases, and it can be easily installed through the package manager. Detailed information on how to install FSlint for a variety of distributions is kept up-to-date on FSlint's homepage, [http://www.pixelbeat.org/fslint/ http://www.pixelbeat.org/fslint/]<br />
<br />
===Documentation===<br />
A general man page is available. Information on use of individual utilities is available by adding the flag --help to the path to the utility. In addition, documentation for both the GUI and command line tools is available at [http://en.flossmanuals.net/FSlint/ http://en.flossmanuals.net/FSlint/]. A FAQ is available at [https://raw.githubusercontent.com/pixelb/fslint/master/doc/FAQ https://raw.githubusercontent.com/pixelb/fslint/master/doc/FAQ]<br />
<br />
===Included in===<br />
<!-- optional. If the tool has been incorporated into a different toolset (e.g., JHOVE integration into FITS), note that here. --><br />
* [http://www.bitcurator.net BitCurator]<br />
<br />
== User Experiences ==<br />
<!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --><br />
* BitCurator. 2014-04-01. Identify and delete duplicate files. [http://wiki.bitcurator.net/index.php?title=Identify_and_delete_duplicate_files http://wiki.bitcurator.net/index.php?title=Identify_and_delete_duplicate_files]<br />
* Byfield, Bruce. 2007-03-27. Flint: annoyingly vague, but useful. Linux Journal. [http://www.linuxjournal.com/content/fslint-annoyingly-vague-useful http://www.linuxjournal.com/content/fslint-annoyingly-vague-useful]<br />
* drad's blog, 2012-06-02. Find Duplicate Files - A comparison of dupes and fslint. [http://www.adercon.com/ac/node/56 http://www.adercon.com/ac/node/56]<br />
* Blog My Mix. 2010-04-21. De-duplicate with Fslint (little review). [http://blogmymix.blogspot.com/2010/04/de-duplicate-with-fslint.html http://blogmymix.blogspot.com/2010/04/de-duplicate-with-fslint.html]<br />
<br />
== Development Activity ==<br />
<!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --><br />
<rss max=5>https://github.com/pixelb/fslint/commits/master.atom</rss><br />
<br />
<!-- Add the OpenHub.com ID for the tool, if known. --><br />
{{Infobox_tool_details<br />
|releases_rss=<br />
|issues_rss=<br />
|mailing_lists=<br />
|ohloh_id=fslint<br />
}}</div>Danielle Plumerhttps://coptr.digipres.org/index.php?title=Fslint&diff=2553Fslint2015-02-04T05:12:37Z<p>Danielle Plumer: </p>
<hr />
<div><!-- Use the structure provided in this template, do not change it! --><br />
<br />
{{Infobox_tool<br />
|purpose= Set of utilities to find and clean various forms of lint on a filesystem, such as duplicate files, empty directories, and bad file names.<br />
|image=Fslint_icon.png<br />
|homepage=http://www.pixelbeat.org/fslint/<br />
|license=GPL 2+<br />
|platforms=Linux<br />
}}<br />
<!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --><br />
<br />
<!-- Add one or more categories to describe the function of the tool, such as:<br />
or or [[Category:Backup]]<br />
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --><br />
[[Category:De-Duplication]]<br />
[[Category:File_Management]]<br />
<br />
<!-- Add relevant categories to describe the content type that the tool addresses, such as:<br />
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]<br />
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --><br />
<br />
== Description ==<br />
<!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --><br />
FSlint is a utility to find and clean various forms of unwanted extraneous files on a computer file system. This excess of unnecessary files is referred to as lint. FSlint will help find unwanted or problematic lint in your files or file names. The most common forms of lint FSlint finds are duplicate files, empty directories, and improper names. FSlint has multiple tools to perform a multitude of tasks in both the graphical interface and command line modes.<br />
<br />
There are a total of ten utilities available in both FSlint's graphical and command-line modes, plus two others (find and zipdir) that are available in command-line mode only:<br />
<br />
* findup - find DUPlicate files<br />
* findnl - find Name Lint (problems with filenames)<br />
* findu8 - find filenames with invalid utf8 encoding<br />
* findbl - find Bad Links (various problems with symlinks)<br />
* findsn - find Same Name (problems with clashing names)<br />
* finded - find Empty Directories<br />
* findid - find files with dead user IDs<br />
* findns - find Non Stripped executables<br />
* findrs - find Redundant Whitespace in files<br />
* findtf - find Temporary Files<br />
* findul - find possibly Unused Libraries<br />
* zipdir - Reclaim wasted space in ext2 directory entries<br />
<br />
FSlint is copyrighted 2000-2009 Padraig Brady, P@draigBrady.com. The program is free software and can be redistributed and/or modified under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or any later version.<br />
<br />
===Platform===<br />
FSlint can be found in the online repositories of several major Linux releases, and it can be easily installed through the package manager. Detailed information on how to install FSlint for a variety of distributions is kept up-to-date on FSlint's homepage, [http://www.pixelbeat.org/fslint/ http://www.pixelbeat.org/fslint/]<br />
<br />
===Documentation===<br />
A general man page is available. Information on use of individual utilities is available by adding the flag --help to the path to the utility. In addition, documentation for both the GUI and command line tools is available at [http://en.flossmanuals.net/FSlint/ http://en.flossmanuals.net/FSlint/]. A FAQ is available at [https://raw.githubusercontent.com/pixelb/fslint/master/doc/FAQ https://raw.githubusercontent.com/pixelb/fslint/master/doc/FAQ]<br />
<br />
===Included in===<br />
<!-- optional. If the tool has been incorporated into a different toolset (e.g., JHOVE integration into FITS), note that here. --><br />
* BitCurator<br />
<br />
== User Experiences ==<br />
<!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --><br />
* BitCurator. 2014-04-01. Identify and delete duplicate files. [http://wiki.bitcurator.net/index.php?title=Identify_and_delete_duplicate_files http://wiki.bitcurator.net/index.php?title=Identify_and_delete_duplicate_files]<br />
* Byfield, Bruce. 2007-03-27. Flint: annoyingly vague, but useful. Linux Journal. [http://www.linuxjournal.com/content/fslint-annoyingly-vague-useful http://www.linuxjournal.com/content/fslint-annoyingly-vague-useful]<br />
* drad's blog, 2012-06-02. Find Duplicate Files - A comparison of dupes and fslint. [http://www.adercon.com/ac/node/56 http://www.adercon.com/ac/node/56]<br />
* Blog My Mix. 2010-04-21. De-duplicate with Fslint (little review). [http://blogmymix.blogspot.com/2010/04/de-duplicate-with-fslint.html http://blogmymix.blogspot.com/2010/04/de-duplicate-with-fslint.html]<br />
<br />
== Development Activity ==<br />
<!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --><br />
<rss max=5>https://github.com/pixelb/fslint/commits/master.atom</rss><br />
<br />
<!-- Add the OpenHub.com ID for the tool, if known. --><br />
{{Infobox_tool_details<br />
|releases_rss=<br />
|issues_rss=<br />
|mailing_lists=<br />
|ohloh_id=fslint<br />
}}</div>Danielle Plumerhttps://coptr.digipres.org/index.php?title=Fslint&diff=2552Fslint2015-02-03T22:46:31Z<p>Danielle Plumer: Created page with "<!-- Use the structure provided in this template, do not change it! --> {{Infobox_tool |purpose= Set of utilities to find and clean various forms of lint on a filesystem, suc..."</p>
<hr />
<div><!-- Use the structure provided in this template, do not change it! --><br />
<br />
{{Infobox_tool<br />
|purpose= Set of utilities to find and clean various forms of lint on a filesystem, such as duplicate files, empty directories, and bad file names.<br />
|image=Fslint_icon.png<br />
|homepage=http://www.pixelbeat.org/fslint/<br />
|license=GPL 2+<br />
|platforms=Linux<br />
}}<br />
<!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --><br />
<br />
<!-- Add one or more categories to describe the function of the tool, such as:<br />
or or [[Category:Backup]]<br />
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --><br />
[[Category:De-Duplication]]<br />
[[Category:File_Management]]<br />
<br />
<!-- Add relevant categories to describe the content type that the tool addresses, such as:<br />
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]<br />
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --><br />
<br />
== Description ==<br />
<!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --><br />
FSlint is a utility to find and clean various forms of unwanted extraneous files on a computer file system. This excess of unnecessary files is referred to as lint. FSlint will help find unwanted or problematic lint in your files or file names. The most common forms of lint FSlint finds are duplicate files, empty directories, and improper names. FSlint has multiple tools to perform a multitude of tasks in both the graphical interface and command line modes.<br />
<br />
There are a total of ten utilities available in both FSlint's graphical and command-line modes, plus two others (find and zipdir) that are available in command-line mode only:<br />
<br />
* findup - find DUPlicate files<br />
* findnl - find Name Lint (problems with filenames)<br />
* findu8 - find filenames with invalid utf8 encoding<br />
* findbl - find Bad Links (various problems with symlinks)<br />
* findsn - find Same Name (problems with clashing names)<br />
* finded - find Empty Directories<br />
* findid - find files with dead user IDs<br />
* findns - find Non Stripped executables<br />
* findrs - find Redundant Whitespace in files<br />
* findtf - find Temporary Files<br />
* findul - find possibly Unused Libraries<br />
* zipdir - Reclaim wasted space in ext2 directory entries<br />
<br />
FSlint is copyrighted 2000-2009 Padraig Brady, P@draigBrady.com. The program is free software and can be redistributed and/or modified under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or any later version.<br />
<br />
==Documentation==<br />
A general man page is available. Information on use of individual utilities is available by adding the flag --help to the path to the utility. In addition, documentation for both the GUI and command line tools is available at [http://en.flossmanuals.net/FSlint/ http://en.flossmanuals.net/FSlint/]. A FAQ is available at [https://raw.githubusercontent.com/pixelb/fslint/master/doc/FAQ https://raw.githubusercontent.com/pixelb/fslint/master/doc/FAQ]<br />
<br />
== User Experiences ==<br />
<!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --><br />
* BitCurator. 2014-04-01. Identify and delete duplicate files. [http://wiki.bitcurator.net/index.php?title=Identify_and_delete_duplicate_files http://wiki.bitcurator.net/index.php?title=Identify_and_delete_duplicate_files]<br />
* Byfield, Bruce. 2007-03-27. Flint: annoyingly vague, but useful. Linux Journal. [http://www.linuxjournal.com/content/fslint-annoyingly-vague-useful http://www.linuxjournal.com/content/fslint-annoyingly-vague-useful]<br />
* drad's blog, 2012-06-02. Find Duplicate Files - A comparison of dupes and fslint. [http://www.adercon.com/ac/node/56 http://www.adercon.com/ac/node/56]<br />
* Blog My Mix. 2010-04-21. De-duplicate with Fslint (little review). [http://blogmymix.blogspot.com/2010/04/de-duplicate-with-fslint.html http://blogmymix.blogspot.com/2010/04/de-duplicate-with-fslint.html]<br />
<br />
== Development Activity ==<br />
<!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --><br />
<!-- Add the OpenHub.com ID for the tool, if known. --><br />
{{Infobox_tool_details<br />
|releases_rss=<br />
|issues_rss=<br />
|mailing_lists=<br />
|ohloh_id=fslint<br />
}}</div>Danielle Plumerhttps://coptr.digipres.org/index.php?title=File:Fslint_icon.png&diff=2551File:Fslint icon.png2015-02-03T22:02:43Z<p>Danielle Plumer: </p>
<hr />
<div></div>Danielle Plumer