COPTR - User contributions [en-gb]

EpubCheck

2013-11-26T15:14:01Z

Johanvanderknijff: Created page with "{{Infobox_tool |purpose=Validator for EPUB files |homepage=https://github.com/IDPF/epubcheck |license=New BSD License |platforms= }} Category:Validation Category:Metada..."

{{Infobox_tool
|purpose=Validator for EPUB files
|homepage=https://github.com/IDPF/epubcheck
|license=New BSD License
|platforms=
}}

[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:Characterisation]]

[[Category:Document]]

== Description ==
EpubCheck is a tool to validate EPUB files. It is also able to extract technical characteristics and embedded metadata from an EPUB file. Both the EPUB 2 and EPUB 3 formats are supported. EpubCheck can be run as a standalone command-line tool or used as a Java library. Development of this tool is supported by the [http://idpf.org/ International Digital Publishing Forum] (IDPF), which also publishes the EPUB standards.

== User Experiences ==


===Online version of EpubCheck ===

http://validator.idpf.org/

== Development Activity ==



{{Infobox_tool_details
|ohloh_id=epubcheck
}}

Tabula

2013-11-26T14:14:58Z

Johanvanderknijff: Created page with "{{Infobox_tool |purpose=Extract tabular data from PDF files |homepage=http://tabula.nerdpower.org/ |license=MIT |platforms= }} Category:Data Extraction Category:Data ca..."

{{Infobox_tool
|purpose=Extract tabular data from PDF files
|homepage=http://tabula.nerdpower.org/
|license=MIT
|platforms=
}}

[[Category:Data Extraction]]
[[Category:Data capture and Deposit]]

[[Category:Document]]
[[Category:Research Data]]

== Description ==
Tabula extracts tabular data from a PDF document to CSV format.

== User Experiences ==


== Development Activity ==



{{Infobox_tool_details
|ohloh_id=tabula-extractor
}}

PDF Tools (by Didier Stevens)

2013-11-26T13:29:04Z

Johanvanderknijff:

{{Infobox_tool
|purpose=Tools for parsing and analysing PDF documents
|image=
|homepage=http://blog.didierstevens.com/programs/pdf-tools/
|license=Not specified, public domain
|platforms=
}}


[[Category:Metadata Extraction]]
[[Category:Dependency Analysis]]
[[Category:Validation]]
[[Category:Document]]

== Description ==
This is a set of Python scripts for anaysing PDF documents. The main ones are:

=== pdf-parser.py ===

This tool will parse a PDF document to identify the fundamental elements used in the analyzed file. A command line option exists to search for specific text strings within indirect objects.

=== pdfid.py ===

Scans a file to look for certain PDF keywords, allowing you to identify PDF documents that contain (for example) JavaScript or execute an action when opened.

== User Experiences ==

== Development Activity ==

{{Infobox_tool_details
|ohloh_id=PDF Tools (by Didier Stevens)
}}

Talk:Main Page

2013-11-21T13:14:57Z

Johanvanderknijff: /* Problems with login procedure (VeriSign) */

==Use of Level 1 section headings ==
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:

http://www.mediawiki.org/wiki/Help_talk:Formatting#Level_1

And also:

http://www.mediawiki.org/wiki/Help:Formatting

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)

: 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)

::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)

::: 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]])

==Purpose field in infobox==
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)
: 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)
:: 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)
::: 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)

==Perhaps rename Imaging category to Disk Imaging?==
Another thing: people might end up mixing up the ''Image'' and ''Imaging'' categories. Maybe rename the latter to ''Disk Imaging'' to avoid this?
[[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 16:15, 20 November 2013 (UTC)
: 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)

==Problems with login procedure (VeriSign)==
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.
[[User:Johanvanderknijff|johanvanderknijff]] ([[User talk:Johanvanderknijff|talk]]) 11:16, 21 November 2013 (UTC)

: [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)

:: 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)

::: 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)

::::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)

Talk:Main Page

2013-11-21T12:28:28Z

Johanvanderknijff:

Talk:Main Page

2013-11-21T11:16:29Z

Johanvanderknijff:

Talk:Main Page

2013-11-21T09:29:33Z

Johanvanderknijff: /* Use of Level 1 section headings */

Talk:Main Page

2013-11-20T16:15:49Z

Johanvanderknijff:

Talk:Main Page

2013-11-20T16:15:01Z

Johanvanderknijff: /* Use of Level 1 section headings */

Talk:Main Page

2013-11-20T16:08:54Z

Johanvanderknijff: /* Use of Level 1 section headings */

Talk:Main Page

2013-11-20T16:07:51Z

Johanvanderknijff: /* Use of Level 1 section headings */

Template:Tool/Preload

2013-11-20T16:00:47Z

Johanvanderknijff: Changed all level 1 headings to level 2, following mediawiki recomms

{{Infobox_tool
|purpose=A brief description
|image=image.png
|homepage=url
|license=
|platforms=
}}


[[Category:Metadata Extraction]]
[[Category:File Format Identification]]
[[Category:Preservation System]]


[[Category:Audio]]
[[Category:Document]]
[[Category:Research Data]]

== Description ==


== User Experiences ==


== Development Activity ==



{{Infobox_tool_details
|ohloh_id=
}}

Talk:Main Page

2013-11-20T15:56:42Z

Johanvanderknijff:

Talk:Main Page

2013-11-20T15:00:16Z

Johanvanderknijff: /* Purpose field in infobox */

Talk:Main Page

2013-11-20T14:59:50Z

Johanvanderknijff:

Talk:Main Page

2013-11-20T14:58:57Z

Johanvanderknijff:

ODF Validator

2013-11-20T14:33:52Z

Johanvanderknijff:

{{Infobox_tool
|purpose=ODF Validator is a tool that validates OpenDocument files and checks them for certain conformance criteria..
|image=
|homepage=https://incubator.apache.org/odftoolkit/conformance/ODFValidator.html
|license=Apache License, Version 2.0
|platforms=
}}


[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:Document]]

== Description ==
ODF Validator is a tool that validates OpenDocument files and checks them for certain conformance criteria. It is available as Java library for command line or embedded use, as well as a servlet. An instance of the servlet is [http://odf-validator.rhcloud.com/ hosted online] courtesy of the OpenDoc Society. ODF Validator is part of the [Apache ODF Toolkit].

== User Experiences ==

[http://www.openplanetsfoundation.org/comment/529#comment-529 Test by KEEP Solutions]:

<blockquote>Apache ODF Validator gives many false-negatives and false-positives (...) [b]ut (..) the schemas are publicly available and the method to validate is well defined by OASIS (...).</blockquote>

== Development Activity ==

{{Infobox_tool_details
|ohloh_id=odftoolkit
}}

Talk:Main Page

2013-11-20T13:48:04Z

Johanvanderknijff:

Talk:Main Page

2013-11-20T13:24:21Z

Johanvanderknijff: Created page with "==Use of Level 1 section headings == 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 u..."

Jpylyzer

2013-11-20T13:10:02Z

Johanvanderknijff:

{{Infobox_tool
|purpose=JP2 validation + properties extraction
|image=
|homepage=http://www.openplanetsfoundation.org/software/jpylyzer
|license=GNU Lesser
|platforms=
}}


[[Category:Validation]]
[[Category:Quality Assurance]]
[[Category:Metadata Extraction]]
[[Category:Image]]

= Description =
JP2 (JPEG 2000 Part 1) validator and properties extractor. Jpylyzer was specifically created to check that a JP2 file really conforms to the format's specifications. Additionally jpylyzer extracts technical characteristics of a JP2 image.

See also: [http://www.openplanetsfoundation.org/blogs/2011-12-14-prototype-jp2-validator-and-properties-extractor A prototype JP2 validator and properties extractor].

Successor to [[Jp2StructCheck]].

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=Jpylyzer
}}

== Release Feed ==

== Activity Feed==
<rss max=5>https://github.com/openplanets/jpylyzer/commits/master.atom</rss>

ODF Validator

2013-11-20T12:52:20Z

Johanvanderknijff:

{{Infobox_tool
|purpose=ODF Validator is a tool that validates OpenDocument files and checks them for certain conformance criteria..
|image=
|homepage=https://incubator.apache.org/odftoolkit/conformance/ODFValidator.html
|license=Apache License, Version 2.0
|platforms=
}}


[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:Document]]

== Description ==
ODF Validator is a tool that validates OpenDocument files and checks them for certain conformance criteria. It is available as Java library for command line or embedded use, as well as a servlet. An instance of the servlet is [http://odf-validator.rhcloud.com/ hosted online] courtesy of the OpenDoc Society. ODF Validator is part of the [Apache ODF Toolkit].

== User Experiences ==

== Development Activity ==

{{Infobox_tool_details
|ohloh_id=odftoolkit
}}

Jpylyzer

2013-11-20T12:16:11Z

Johanvanderknijff:

{{Infobox_tool
|purpose=JP2 validation + properties extraction \\
|image=
|homepage=http://www.openplanetsfoundation.org/software/jpylyzer
|license=GNU Lesser
|platforms=
}}


[[Category:Validation]]
[[Category:Quality Assurance]]
[[Category:Metadata Extraction]]
[[Category:Image]]

= Description =
JP2 (JPEG 2000 Part 1) validator and properties extractor. Jpylyzer was specifically created to check that a JP2 file really conforms to the format's specifications. Additionally jpylyzer extracts technical characteristics of a JP2 image.

See also: [http://www.openplanetsfoundation.org/blogs/2011-12-14-prototype-jp2-validator-and-properties-extractor A prototype JP2 validator and properties extractor].

Successor to [[Jp2StructCheck]].

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=Jpylyzer
}}

== Release Feed ==

== Activity Feed==
<rss max=5>https://github.com/openplanets/jpylyzer/commits/master.atom</rss>

Jpylyzer

2013-11-20T12:15:10Z

Johanvanderknijff:

{{Infobox_tool
|purpose=JP2 validation + properties extraction \\
|image=
|homepage=http://www.openplanetsfoundation.org/software/jpylyzer
|license=GNU Lesser
|platforms=
}}


[[Category:Validation]]
[[Category:Quality Assurance]]
[[Category:Metadata Extraction]]
[[Category:Image]]

= Description =
JP2 (JPEG 2000 Part 1) validator and properties extractor. Jpylyzer was specifically created to check that a JP2 file really conforms to the format's specifications. Additionally jpylyzer extracts technical characteristics of a JP2 image.

See also: [http://www.openplanetsfoundation.org/blogs/2011-12-14-prototype-jp2-validator-and-properties-extractor]

Successor to [[Jp2StructCheck]].

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=Jpylyzer
}}

== Release Feed ==

== Activity Feed==
<rss max=5>https://github.com/openplanets/jpylyzer/commits/master.atom</rss>

ODF Validator

2013-11-20T12:05:24Z

Johanvanderknijff: Created page with "{{Infobox_tool |purpose=ODF Validator is a tool that validates OpenDocument files and checks them for certain conformance criteria.. |image= |homepage=https://incubator.apache..."

{{Infobox_tool
|purpose=ODF Validator is a tool that validates OpenDocument files and checks them for certain conformance criteria..
|image=
|homepage=https://incubator.apache.org/odftoolkit/conformance/ODFValidator.html
|license= Apache License, Version 2.0
|platforms=
}}


[[Category:Validation]]
[[Category:Metadata Extraction]]
[[Category:Document]]

= Description =
ODF Validator is a tool that validates OpenDocument files and checks them for certain conformance criteria. It is available as Java library for command line or embedded use, as well as a servlet. An instance of the servlet is [http://odf-validator.rhcloud.com/ hosted online] courtesy of the OpenDoc Society. ODF Validator is part of the [Apache ODF Toolkit].

= User Experiences =

= Development Activity =

{{Infobox_tool_details
|ohloh_id=odftoolkit
}}