kbiw 0.1.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- kbiw-0.1.1/LICENSE +201 -0
- kbiw-0.1.1/MANIFEST.in +2 -0
- kbiw-0.1.1/PKG-INFO +335 -0
- kbiw-0.1.1/README.md +316 -0
- kbiw-0.1.1/kbiw/__init__.py +0 -0
- kbiw-0.1.1/kbiw/__main__.py +8 -0
- kbiw-0.1.1/kbiw/conf/config.json +36 -0
- kbiw-0.1.1/kbiw/conf/schemas/kbAccess_2015.sch +117 -0
- kbiw-0.1.1/kbiw/conf/schemas/kbMaster_2015.sch +109 -0
- kbiw-0.1.1/kbiw/conf/schemas/kbMaster_2026.sch +158 -0
- kbiw-0.1.1/kbiw/ctables.py +171 -0
- kbiw-0.1.1/kbiw/grok.py +126 -0
- kbiw-0.1.1/kbiw/kakadu.py +101 -0
- kbiw-0.1.1/kbiw/kbiw.py +236 -0
- kbiw-0.1.1/kbiw/propertiescheck.py +114 -0
- kbiw-0.1.1/kbiw/shared.py +77 -0
- kbiw-0.1.1/kbiw/vips.py +55 -0
- kbiw-0.1.1/kbiw/workflows/__init__.py +0 -0
- kbiw-0.1.1/kbiw/workflows/tifftojp2.py +356 -0
- kbiw-0.1.1/kbiw.egg-info/PKG-INFO +335 -0
- kbiw-0.1.1/kbiw.egg-info/SOURCES.txt +25 -0
- kbiw-0.1.1/kbiw.egg-info/dependency_links.txt +1 -0
- kbiw-0.1.1/kbiw.egg-info/entry_points.txt +2 -0
- kbiw-0.1.1/kbiw.egg-info/requires.txt +4 -0
- kbiw-0.1.1/kbiw.egg-info/top_level.txt +1 -0
- kbiw-0.1.1/pyproject.toml +38 -0
- kbiw-0.1.1/setup.cfg +4 -0
kbiw-0.1.1/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "{}"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright {yyyy} {name of copyright owner}
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
kbiw-0.1.1/MANIFEST.in
ADDED
kbiw-0.1.1/PKG-INFO
ADDED
|
@@ -0,0 +1,335 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: kbiw
|
|
3
|
+
Version: 0.1.1
|
|
4
|
+
Summary: KB Image Workflow Tool
|
|
5
|
+
Author-email: Johan van der Knijff <johan.vanderknijff@kb.nl>
|
|
6
|
+
License-Expression: Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://github.com/KBNLresearch/kbiw
|
|
8
|
+
Project-URL: Issues, https://github.com/KBNLresearch/kbiw/issues
|
|
9
|
+
Classifier: Programming Language :: Python :: 3
|
|
10
|
+
Classifier: Operating System :: OS Independent
|
|
11
|
+
Requires-Python: >=3.9
|
|
12
|
+
Description-Content-Type: text/markdown
|
|
13
|
+
License-File: LICENSE
|
|
14
|
+
Requires-Dist: lxml
|
|
15
|
+
Requires-Dist: pyvips
|
|
16
|
+
Requires-Dist: jpylyzer
|
|
17
|
+
Requires-Dist: pyexiftool
|
|
18
|
+
Dynamic: license-file
|
|
19
|
+
|
|
20
|
+
# KB Image Workflow Tool
|
|
21
|
+
|
|
22
|
+
## About this software
|
|
23
|
+
|
|
24
|
+
Kbiw converts image files in digitisation batches to JP2 (JPEG 2000 Part 1) format using the [Grok](https://github.com/GrokImageCompression/grok) codec. It clones the structure of the input directory, and then replicates it in the output directory. The JP2 images are then subjected to the following quality checks:
|
|
25
|
+
|
|
26
|
+
1. Pixel comparison between each pair of source and destination images (using [libvips](https://www.libvips.org/) and [pyvips](https://libvips.github.io/pyvips/)).
|
|
27
|
+
2. Check of extracted technical properties (using [jpylyzer](https://jpylyzer.openpreservation.org/)) against a user-defined [Schematron](http://en.wikipedia.org/wiki/Schematron) profile.
|
|
28
|
+
|
|
29
|
+
The software also generates checksums of all converted images.
|
|
30
|
+
|
|
31
|
+
## Dependencies
|
|
32
|
+
|
|
33
|
+
- Python (tested with versions 3.12.3 and 3.14.5)
|
|
34
|
+
- [Grok JPEG 2000 codec](https://github.com/GrokImageCompression/grok) (tested with version ??)
|
|
35
|
+
- [Libvips](https://www.libvips.org/)
|
|
36
|
+
|
|
37
|
+
## Installation of dependencies
|
|
38
|
+
|
|
39
|
+
### Grok (all platforms)
|
|
40
|
+
|
|
41
|
+
1. Download the latest binaries of the Grok image compression software for your platform from:
|
|
42
|
+
|
|
43
|
+
<https://github.com/GrokImageCompression/grok/releases>
|
|
44
|
+
|
|
45
|
+
2. Extract the ZIP file to your local file system, and make a note of the installation location. You'll need to enter this later in the kbiw configuration file.
|
|
46
|
+
|
|
47
|
+
### Libvips
|
|
48
|
+
|
|
49
|
+
#### Linux (Ubuntu, Linux Mint)
|
|
50
|
+
|
|
51
|
+
Install libvips using:
|
|
52
|
+
|
|
53
|
+
```
|
|
54
|
+
sudo apt install libvips-dev --no-install-recommends
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
#### macOS
|
|
58
|
+
|
|
59
|
+
TODO
|
|
60
|
+
|
|
61
|
+
#### Windows
|
|
62
|
+
|
|
63
|
+
1. Download the latest release from the [build-win64-mxe repository](https://github.com/libvips/build-win64-mxe/releases). For a 64 bit Windows system you need the ZIP file that follows the "vips-dev-x64-all-x.y.z.zip" naming pattern (e.g. vips-dev-x64-all-8.18.2.zip).
|
|
64
|
+
|
|
65
|
+
2. Extract the ZIP file to your local file system, and make a note of the installation location (e.g. "C:\vips-dev"). You'll need to enter this later in the kbiw configuration file.
|
|
66
|
+
|
|
67
|
+
### ExifTool
|
|
68
|
+
|
|
69
|
+
#### Linux (Ubuntu, Linux Mint)
|
|
70
|
+
|
|
71
|
+
Install ExifTool using:
|
|
72
|
+
|
|
73
|
+
```
|
|
74
|
+
sudo apt install libimage-exiftool-perl
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
#### macOS
|
|
78
|
+
|
|
79
|
+
TODO
|
|
80
|
+
|
|
81
|
+
#### Windows
|
|
82
|
+
|
|
83
|
+
1. Download the 64-bit Windows executable from the [ExifTool website](https://exiftool.org/index.html).
|
|
84
|
+
|
|
85
|
+
2. Extract the ZIP file to your local file system.
|
|
86
|
+
|
|
87
|
+
3. In the extracted folder, rename the ExifTool executable ("exiftool(-k).exe") to "exiftool.exe.
|
|
88
|
+
|
|
89
|
+
4. Make a note of the full path to the executable (e.g. "C:\exiftool\exiftool.exe"). You'll need to enter this later in the kbiw configuration file.
|
|
90
|
+
|
|
91
|
+
## Installation of kbiw
|
|
92
|
+
|
|
93
|
+
As of 2026, [uv](https://docs.astral.sh/uv/) appears to be the most straightforward tool for installing Python applications on a variety of platforms (Linux, MacOS, Windows).
|
|
94
|
+
|
|
95
|
+
### uv installation
|
|
96
|
+
|
|
97
|
+
First, check if uv is installed on your system by typing the uv command in a terminal:
|
|
98
|
+
|
|
99
|
+
```
|
|
100
|
+
uv
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
If this results in a help message, uv is installed, and you can skip directly to the "imgquad installation" section below. If not, you first need to install uv.
|
|
104
|
+
|
|
105
|
+
On Linux and MacOS you can install uv with the following command:
|
|
106
|
+
|
|
107
|
+
```
|
|
108
|
+
curl -LsSf https://astral.sh/uv/install.sh | sh
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
Alternatively, you can use wget if your system doesn't have curl installed:
|
|
112
|
+
|
|
113
|
+
```
|
|
114
|
+
wget -qO- https://astral.sh/uv/install.sh | sh
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
To install uv on Windows, open a Powershell terminal, and run the following command:
|
|
118
|
+
|
|
119
|
+
```
|
|
120
|
+
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
Regardless of the operating system, in some cases the installation script will update your system's configuration to make the location of the uv executable globally accessible. If this happens, just close your current terminal, and open a new one for these changes to take effect. Pay attention to the screen output of the installation script for any details on this.
|
|
124
|
+
|
|
125
|
+
### kbiw installation
|
|
126
|
+
|
|
127
|
+
Use the following command to install kbiw (all platforms):
|
|
128
|
+
|
|
129
|
+
```
|
|
130
|
+
uv tool install kbiw
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
Then run kbiw once:
|
|
134
|
+
|
|
135
|
+
```
|
|
136
|
+
kbiw
|
|
137
|
+
```
|
|
138
|
+
|
|
139
|
+
Depending on your system, kbiw will now create a configuration folder (see next section).
|
|
140
|
+
|
|
141
|
+
## Configuration
|
|
142
|
+
|
|
143
|
+
Before you can use kbiw, you need to edit the configuration file, which is located in the configuration folder. The configuration folder has the name "kbiw", and its location depends on your operating system:
|
|
144
|
+
|
|
145
|
+
- For Linux and MacOS, the configuration folder is a subdirectory of the location defined by the environment variable *$XDG_CONFIG_HOME*. If this variable is not set, it will be a subdirectory of the *.config* directory in the user's home folder (e.g. `/home/johan/.config/kbiw`). Note that the *.config* directory is hidden by default.
|
|
146
|
+
- For Windows, the configuration folder is a subdirectory of of the *AppData\Local* folder (e.g. `C:\Users\johan\AppData\Local\kbiw`).
|
|
147
|
+
|
|
148
|
+
Open the configuration file ("config.json") in a text editor, and edit the following values:
|
|
149
|
+
|
|
150
|
+
|Variable|Meaning|Examples|
|
|
151
|
+
|:--|:--|:--|
|
|
152
|
+
|grokDir|Grok installation directory|`C:/Grok` (Windows); `~/grok` (Linux)|
|
|
153
|
+
|exifToolExecutable|ExifTool executable|`C:/exiftool/exiftool.exe` (Windows); `/bin/exiftool` (Linux)|
|
|
154
|
+
|vipsBinDir|Libvips binary dir (only needed on Windows, ignored on Linux/macOS)|`C:/vips-dev/bin` (Windows)|
|
|
155
|
+
|
|
156
|
+
Here's an example for a Windows system:
|
|
157
|
+
|
|
158
|
+
|
|
159
|
+
```json
|
|
160
|
+
{
|
|
161
|
+
"grokDir": "`C:/Grok",
|
|
162
|
+
"exifToolExecutable": "C:/exiftool/exiftool.exe",
|
|
163
|
+
"vipsBinDir": "C:/vips-dev/bin",
|
|
164
|
+
:
|
|
165
|
+
}
|
|
166
|
+
```
|
|
167
|
+
|
|
168
|
+
## upgrade kbiw
|
|
169
|
+
|
|
170
|
+
Use the following command to upgrade an existing kbiw installation to the latest version:
|
|
171
|
+
|
|
172
|
+
```
|
|
173
|
+
uv tool upgrade kbiw
|
|
174
|
+
```
|
|
175
|
+
|
|
176
|
+
<!---
|
|
177
|
+
|
|
178
|
+
## Command-line syntax
|
|
179
|
+
|
|
180
|
+
The general syntax of imgquad is:
|
|
181
|
+
|
|
182
|
+
```
|
|
183
|
+
usage: imgquad [-h] [--version] {process,list,copyps} ...
|
|
184
|
+
```
|
|
185
|
+
|
|
186
|
+
Imgquad has three sub-commands:
|
|
187
|
+
|
|
188
|
+
|Command|Description|
|
|
189
|
+
|:-----|:--|
|
|
190
|
+
|process|Process a batch.|
|
|
191
|
+
|list|List available profiles and schemas.|
|
|
192
|
+
|copyps|Copy default profiles and schemas to user directory.|
|
|
193
|
+
|
|
194
|
+
|
|
195
|
+
|
|
196
|
+
### process command
|
|
197
|
+
|
|
198
|
+
Run imgquad with the *process* command to process a batch. The syntax is:
|
|
199
|
+
|
|
200
|
+
```
|
|
201
|
+
usage: imgquad process [-h] [--prefixout PREFIXOUT] [--outdir OUTDIR]
|
|
202
|
+
[--delimiter DELIMITER] [--verbose]
|
|
203
|
+
profile batchDir
|
|
204
|
+
```
|
|
205
|
+
|
|
206
|
+
The *process* command expects the following positional arguments:
|
|
207
|
+
|
|
208
|
+
|Argument|Description|
|
|
209
|
+
|:-----|:--|
|
|
210
|
+
|profile|This defines the validation profile. Note that any file paths entered here will be ignored, as Imgquad only accepts profiles from the profiles directory. You can just enter the file name without the path. Use the *list* command to list all available profiles.|
|
|
211
|
+
|batchDir|This defines the batch directory that will be analyzed.|
|
|
212
|
+
|
|
213
|
+
In addition, the following optional arguments are available:
|
|
214
|
+
|
|
215
|
+
|Argument|Description|
|
|
216
|
+
|:-----|:--|
|
|
217
|
+
|--prefixout, -p|This defines a text prefix on which the names of the output files are based (default: "pq").|
|
|
218
|
+
|--outdir, -o|This defines the directory where output is written (default: current working directory from which imgquad is launched).|
|
|
219
|
+
|--delimiter, -d|This defines the delimiter that is used in the output summary file (default: ';')|
|
|
220
|
+
|--verbose, -b|This tells imgquad to report Schematron output in verbose format.|
|
|
221
|
+
|
|
222
|
+
In the simplest case, we can call imgquad with the profile and the batch directory as the only arguments:
|
|
223
|
+
|
|
224
|
+
```
|
|
225
|
+
imgquad process beeldstudio-retro.xml ./mybatch
|
|
226
|
+
```
|
|
227
|
+
|
|
228
|
+
Imgquad will now recursively traverse all directories and files inside the "mybatch" directory, and analyse all image files (based on a file extension match).
|
|
229
|
+
|
|
230
|
+
### list command
|
|
231
|
+
|
|
232
|
+
Run imgquad with the *list* command to get a list of the available profiles and schemas, as well as their locations. For example:
|
|
233
|
+
|
|
234
|
+
```
|
|
235
|
+
imgquad list
|
|
236
|
+
```
|
|
237
|
+
|
|
238
|
+
Results in:
|
|
239
|
+
|
|
240
|
+
```
|
|
241
|
+
Available profiles (directory /home/johan/.config/imgquad/profiles):
|
|
242
|
+
- mh-2025-tiff.xml
|
|
243
|
+
Available schemas (directory /home/johan/.config/imgquad/schemas):
|
|
244
|
+
- mh-2025-tiff-600.sch
|
|
245
|
+
```
|
|
246
|
+
|
|
247
|
+
|
|
248
|
+
|
|
249
|
+
## Schemas
|
|
250
|
+
|
|
251
|
+
Schemas contain the Schematron rules on which the quality assessment is based. Some background information about this type of rule-based validation can be found in [this blog post](https://www.bitsgalore.org/2012/09/04/automated-assessment-jp2-against-technical-profile). Currently the following schemas are included:
|
|
252
|
+
|
|
253
|
+
### mh-2025-tiff-600.sch
|
|
254
|
+
|
|
255
|
+
This is a schema for digitised medieval manuscripts. It includes the following checks:
|
|
256
|
+
|
|
257
|
+
|Check|Value|
|
|
258
|
+
|:---|:---|
|
|
259
|
+
|Image format|TIFF|
|
|
260
|
+
|ICC profile name|eciRGB v2|
|
|
261
|
+
|XResolution TIFF tag|tag exists|
|
|
262
|
+
|YResolution TIFF tag|tag exists|
|
|
263
|
+
|XResolution value|600 (+/- 1) |
|
|
264
|
+
|YResolution value|600 (+/- 1) |
|
|
265
|
+
|ResolutionUnit TIFF tag|tag exists|
|
|
266
|
+
|ResolutionUnit value|2 (inches)|
|
|
267
|
+
|ImageWidth TIFF tag|tag exists|
|
|
268
|
+
|ImageLength TIFF tag|tag exists|
|
|
269
|
+
|BitsPerSample TIFF tag|tag exists|
|
|
270
|
+
|BitsPerSample value|'8 8 8'|
|
|
271
|
+
|ICCProfile TIFF tag|tag exists|
|
|
272
|
+
|Copyright TIFF tag|tag exists|
|
|
273
|
+
|NewSubfileType TIFF tag|at most 1 instance of this tag|
|
|
274
|
+
|SubIFDs TIFF tag|tag does not exist|
|
|
275
|
+
|Compression EXIF tag|tag exists|
|
|
276
|
+
|Compression|1 (Uncompressed)|
|
|
277
|
+
|Software EXIF tag|tag exists|
|
|
278
|
+
|Software value|not empty|
|
|
279
|
+
|DateTimeOriginal EXIF tag|tag exists|
|
|
280
|
+
|DateTimeOriginal value|not empty|
|
|
281
|
+
|Model EXIF tag|tag exists|
|
|
282
|
+
|Model value|not empty|
|
|
283
|
+
|Make EXIF tag|tag exists|
|
|
284
|
+
|Make value|not empty|
|
|
285
|
+
|ShutterSpeedValue EXIF tag|tag exists|
|
|
286
|
+
|ShutterSpeedValue value|not empty|
|
|
287
|
+
|ApertureValue EXIF tag|tag exists|
|
|
288
|
+
|ApertureValue value|not empty|
|
|
289
|
+
|ISOSpeedRatings EXIF tag|tag exists|
|
|
290
|
+
|ISOSpeedRatings value|not empty|
|
|
291
|
+
|photoshop:Headline|defined in XMP metadata as either element `rdf:RDF/rdf:Description/photoshop:Headline`, or attribute `rdf:RDF/rdf:Description/@photoshop:Headline`|
|
|
292
|
+
|photoshop:Headline value|not empty|
|
|
293
|
+
|photoshop:Credit|defined in XMP metadata as either element `rdf:RDF/rdf:Description/photoshop:Credit`, or attribute `rdf:RDF/rdf:Description/@photoshop:Credit`|
|
|
294
|
+
|photoshop:Credit value|not empty|
|
|
295
|
+
|
|
296
|
+
The schema also includes an additional check on any exceptions that occurred while parsing the image, as this may indicate a corrupted file.
|
|
297
|
+
|
|
298
|
+
### mh-2025-tiff-300.sch
|
|
299
|
+
|
|
300
|
+
This schema is identical to the mh-2025-tiff-600.sch schema, except for the checks on the XResolution and YResolution values:
|
|
301
|
+
|
|
302
|
+
|Check|Value|
|
|
303
|
+
|:---|:---|
|
|
304
|
+
|XResolution value|300 (+/- 1) |
|
|
305
|
+
|YResolution value|300 (+/- 1) |
|
|
306
|
+
|
|
307
|
+
## Output
|
|
308
|
+
|
|
309
|
+
Imgquad reports the following output:
|
|
310
|
+
|
|
311
|
+
### Comprehensive output file (XML)
|
|
312
|
+
|
|
313
|
+
For each batch, Imgquad generates one comprehensive output file in XML format. This file contains, for each image, all extracted properties, as well as the Schematron report and the assessment status.
|
|
314
|
+
|
|
315
|
+
### Summary file (CSV)
|
|
316
|
+
|
|
317
|
+
This is a comma-delimited text file that summarises the analysis. At the minimum, Imgquad reports the following columns for each image:
|
|
318
|
+
|
|
319
|
+
|Column|Description|
|
|
320
|
+
|:-----|:--|
|
|
321
|
+
|file|Full path to the image file.|
|
|
322
|
+
|validationSuccess|Flag with value *True* if Schematron validation was succesful, and *False* if not. A value *False* indicates that the file could not be validated (e.g. because no matching schema was found, or the validation resulted in an unexpected exception)|
|
|
323
|
+
|validationOutcome|The outcome of the Schematron validation/assessment. Value is *Pass* if file passed all tests, and *Fail* otherwise. Note that it is automatically set to *Fail* if the Schematron validation was unsuccessful (i.e. "validationSuccess" is *False*)|
|
|
324
|
+
|validationErrors|List of validation errors (separated by "\|" characters).|
|
|
325
|
+
|
|
326
|
+
In addition, the summary file contains additional columns with the properties that are defined by the *summaryProperty* elements in the profile.
|
|
327
|
+
|
|
328
|
+
-->
|
|
329
|
+
|
|
330
|
+
## Licensing
|
|
331
|
+
|
|
332
|
+
KBiw is released under the [Apache License, Version 2.0](https://www.apache.org/licenses/LICENSE-2.0). Parts of the code were inspired by the Bodeleian's [Image Processing](https://github.com/bodleian/image-processing) library.
|
|
333
|
+
|
|
334
|
+
|
|
335
|
+
|