COPTR - User contributions [en-gb]

Workflow:Validation Error Analysis and Treatment for PDF-hul 133 Invalid date

2024-05-23T16:18:32Z

Lindlar:

{{Infobox COW
|status=Production
|tools=ExifTool, HxD, Pdfcpu, Qpdf, JHOVE, veraPDF Arlington Model Checker
|input=File with JHOVE validation error PDF-HUL-133 “Improperly formed date"
|output=Fixed file
|organisation=TIB
|organisationurl=https://wiki.tib.eu/confluence/display/lza/Digital+preservation+at+TIB
}}
==Workflow Description==

The workflow describes the analysis and the fix of a specific instance of a PDF-HUL-133 error.
It is a manual workflow. The methodology used here is that introduced in https://hdl.handle.net/2142/121092.

'''Validation Error'''

JHOVE v1.30.0RC1 PDF-hul v1.12.5 PDF-HUL-133 Improperly formed date. Well-formed, but not valid.

'''Cross-Check with other Tools'''

Cross-checked with:
pdfcpu v0.6.0dev relaxed mode - no error
pdfcpu v0.6.0dev strict mode - no error
qpdf v9.1.1 - no error
Arlington PDF Model checker by verapdf 1.26.0-RC1 Greenfield Parser:
Entry ModDate in DocInfo shall have type Date (1 occurance)
Entry CreationDate in DocInfo shall have type Date (1 occurance)
'''

'''Locate Error in Spec'''

ISO3200-2:2017 (PDF 2.0 Spec) lists the the Keys CreationDate and ModDate in the Document Info Dictionary as type Date.
Section 7.0.4 defines that a date shall be a text string containing no whitespace, of the form:
''(D:YYYYMMDDHHmmSSOHH'mm)
where:
YYYY shall be the year
MM shall be the month (01–12)
DD shall be the day (01–31)
HH shall be the hour (00–23)
mm shall be the minute (00–59)
SS shall be the second (00–59)
O shall be the relationship of local time to Universal Time (UT), and shall be denoted by one of the characters PLUS SIGN (U+002B) (+), HYPHEN-MINUS (U+002D) (-), or LATIN CAPITAL LETTER Z (U+005A) (Z) (see below)
HH followed by APOSTROPHE (U+0027) (') shall be the absolute value of the offset from UT in hours (00–23)
mm shall be the absolute value of the offset from UT in minutes (00–59)

The prefix D: shall be present, the year field (YYYY) shall be present and all other fields may be present but only if all of their preceding fields are also present. The APOSTROPHE following the hour offset field (HH) shall only be present if the HH field is present. The minute offset field (mm) shall only be present if the APOSTROPHE following the hour offset field (HH) is present. The default values for MM and DD shall be both 01; all other numerical fields shall default to zero values. A PLUS SIGN as the value of the O field signifies that local time is now and later than UT, a HYPHEN-MINUS signifies that local time is earlier than UT, and the LATIN CAPITAL LETTER Z signifies that local time is equal to UT. If no UT information is specified, the relationship of the specified time to UT shall be considered to be GMT. Regardless of whether the time zone is specified, the rest of the date shall be specified in local time.''

The specification further notes that ''versions up to and including 1.7 defined a date string to include a terminating apostrophe. PDF processors are recommended to accept date strings that still follow that convention''.

'''Locate Error in File
'''
Offset given by JHOVE can be navigated to using a hex editor such as HxD. The offset points to the Document Info Dictionary with /CreationDate (D:2018020915415409'00') and /ModDate(D:2018020915415409'00'). Mapping those dates to the notation given above it becomes clear that the O key which identifies the relation to UT is missing. Alternatively to looking for the dates in a hex editor, exiftool can be used to pull out all dates with:
exiftool -time:all -G -a -s file.pdf

''' Match?'''

Yes. Description in the spec and error in the file match. (D:2018020915415409'00') is missing the O key.

'''Fixable?'''

Yes. If other dates, e.g. in the XMP-section, are in the correct format, they can be used to determine the corect value for O. If not, the HH'MM' UT offset can be removed to form a valid date.

'''Fix'''

Option 1:
This option only works in the case of the missing O entry and the trailing apostrophe being present. In this case, the trailing apostrophe can be deleted and the O entry, if it can be determined from other dates, added to the value. This does not change the overall byte number of the date value and therefore has no impact on the PDF's internal structure.

Option 2:
The date can also be modified using exiftool. This will create an incremental update to the end of the file which can be rolled back with tools such as pdfressurect. Due to objects being added, the size of the file will change.
The exiftool command to e.g. update the dates above to include the O key + is:
exiftool -PDF:ModifyDate="2018:02:09 15:41:54+09:00" -PDF:CreateDate="2018:02:09 15:41:54+09:00" file.pdf
If you do not know the correct O key, you can also omit the offset with:
exiftool -PDF:ModifyDate="2018:02:09 15:41:54" -PDF:CreateDate="2018:02:09 15:41:54" file.pdf

'''Check'''

Re-validate file with Arlington PDF Model checker by veraPDF: Error messages are gone, no deviations found.
Re-validate file with JHOVE: Well-formed and valid with option 2. Well-formed but not valid with option 1, as JHOVE currently expects date in format pre-PDF2.0, i.e. without trailing apostrophe.

'''Success?'''

Yes.

[[File:PDF-hul-133_1.jpg|Workflow image]] 



==Purpose, Context and Content==

This workflow describes the analysis and treatment of JHOVE PDF-Hul error message PDF-HUL-133 Improperly formed date. It describes the process and results of a manual validation error analysis and treatment process.

==Evaluation/Review==

The workflow is effective and should be replicable for most improperly formed date related errors in PDFs. However, as an invalid date has little impact on the rendering behavior of the PDF file itself, institutions may decide to not fix the error.
Please note that most PDF Readers (e.g., Adobe Acrobat, Foxit) make use of XMP Metadata and not of Document Info Dictionary Metadata when they display Date Created and Last Modified Dates in a document's properties.

==Further Information==

Workflow:Validation Error Analysis and Treatment for PDF-hul 133 Invalid date

2024-05-12T11:21:00Z

Lindlar:

{{Infobox COW
|status=Production
|tools=ExifTool, HxD, Pdfcpu, Qpdf, JHOVE, veraPDF Arlington Model Checker
|input=File with JHOVE validation error PDF-HUL-133 “Improperly formed date"
|output=Fixed file
|organisation=TIB
|organisationurl=https://wiki.tib.eu/confluence/display/lza/Digital+preservation+at+TIB
}}
==Workflow Description==

The workflow describes the analysis and the fix of a specific instance of a PDF-HUL-133 error.
It is a manual workflow. The methodology used here is that introduced in https://hdl.handle.net/2142/121092.

'''Validation Error'''

JHOVE v1.30.0RC1 PDF-hul v1.12.5 PDF-HUL-133 Improperly formed date. Well-formed, but not valid.

'''Cross-Check with other Tools'''

Cross-checked with:
pdfcpu v0.6.0dev relaxed mode - no error
pdfcpu v0.6.0dev strict mode - no error
qpdf v9.1.1 - no error
Arlington PDF Model checker by verapdf 1.26.0-RC1 Greenfield Parser:
Entry ModDate in DocInfo shall have type Date (1 occurance)
Entry CreationDate in DocInfo shall have type Date (1 occurance)
'''

'''Locate Error in Spec'''

ISO3200-2:2017 (PDF 2.0 Spec) lists the the Keys CreationDate and ModDate in the Document Info Dictionary as type Date.
Section 7.0.4 defines that a date shall be a text string containing no whitespace, of the form:
''(D:YYYYMMDDHHmmSSOHH'mm)
where:
YYYY shall be the year
MM shall be the month (01–12)
DD shall be the day (01–31)
HH shall be the hour (00–23)
mm shall be the minute (00–59)
SS shall be the second (00–59)
O shall be the relationship of local time to Universal Time (UT), and shall be denoted by one of the characters PLUS SIGN (U+002B) (+), HYPHEN-MINUS (U+002D) (-), or LATIN CAPITAL LETTER Z (U+005A) (Z) (see below)
HH followed by APOSTROPHE (U+0027) (') shall be the absolute value of the offset from UT in hours (00–23)
mm shall be the absolute value of the offset from UT in minutes (00–59)

The prefix D: shall be present, the year field (YYYY) shall be present and all other fields may be present but only if all of their preceding fields are also present. The APOSTROPHE following the hour offset field (HH) shall only be present if the HH field is present. The minute offset field (mm) shall only be present if the APOSTROPHE following the hour offset field (HH) is present. The default values for MM and DD shall be both 01; all other numerical fields shall default to zero values. A PLUS SIGN as the value of the O field signifies that local time is now and later than UT, a HYPHEN-MINUS signifies that local time is earlier than UT, and the LATIN CAPITAL LETTER Z signifies that local time is equal to UT. If no UT information is specified, the relationship of the specified time to UT shall be considered to be GMT. Regardless of whether the time zone is specified, the rest of the date shall be specified in local time.''

The specification further notes that ''versions up to and including 1.7 defined a date string to include a terminating apostrophe. PDF processors are recommended to accept date strings that still follow that convention''.

'''Locate Error in File
'''
Offset given by JHOVE can be navigated to using a hex editor such as HxD. The offset points to the Document Info Dictionary with /CreationDate (D:2018020915415409'00') and /ModDate(D:2018020915415409'00'). Mapping those dates to the notation given above it becomes clear that the O key which identifies the relation to UT is missing. Alternatively to looking for the dates in a hex editor, exiftool can be used to pull out all dates with:
exiftool -time:all -G -a -s file.pdf

''' Match?'''

Yes. Description in the spec and error in the file match. (D:2018020915415409'00') is missing the O key.

'''Fixable?'''

Yes. If other dates, e.g. in the XMP-section, are in the correct format, they can be used to determine the corect value for O. If not, the HH'MM' UT offset can be removed to form a valid date.

'''Fix'''

Option 1:
This option only works in the case of the missing O entry and the trailing apostrophe being present. In this case, the trailing apostrophe can be deleted and the O entry, if it can be determined from other dates, added to the value. This does not change the overall byte number of the date value and therefore has no impact on the PDF's internal structure.

Option 2:
The date can also be modified using exiftool. This will create an incremental update to the end of the file which can be rolled back with tools such as pdfressurect. Due to objects being added, the size of the file will change.
The exiftool command to e.g. update the dates above to include the O key + is:
exiftool -PDF:ModifyDate="2018:02:09 15:41:54+09:00" -PDF:CreateDate="2018:02:09 15:41:54+09:00" file.pdf
If you do not know the correct O key, you can also omit the offset with:
exiftool -PDF:ModifyDate="2018:02:09 15:41:54" -PDF:CreateDate="2018:02:09 15:41:54" file.pdf

'''Check'''

Re-validate file with Arlington PDF Model checker by veraPDF: Error messages are gone, no deviations found.
Re-validate file with JHOVE: Well-formed and valid with option 2. Well-formed but not valid with option 1, as JHOVE currently expects date in format pre-PDF2.0, i.e. without trailing apostrophe.

'''Success?'''

Yes.

[[File:PDF-hul-133 1.jpg|Workflow image]] 



==Purpose, Context and Content==

This workflow describes the analysis and treatment of JHOVE PDF-Hul error message PDF-HUL-133 Improperly formed date. It describes the process and results of a manual validation error analysis and treatment process.

==Evaluation/Review==

The workflow is effective and should be replicable for most improperly formed date related errors in PDFs. However, as an invalid date has little impact on the rendering behavior of the PDF file itself, institutions may decide to not fix the error.
Please note that most PDF Readers (e.g., Adobe Acrobat, Foxit) make use of XMP Metadata and not of Document Info Dictionary Metadata when they display Date Created and Last Modified Dates in a document's properties.

==Further Information==

Workflow:Validation Error Analysis and Treatment for PDF-hul 133 Invalid date

2024-05-12T10:33:44Z

Lindlar:

{{Infobox COW
|status=Production
|tools=ExifTool, HxD, Pdfcpu, Qpdf, JHOVE, veraPDF Arlington Model Checker
|input=File with JHOVE validation error PDF-HUL-133 “Invalid date"
|output=Fixed file
|organisation=TIB
|organisationurl=https://wiki.tib.eu/confluence/display/lza/Digital+preservation+at+TIB
}}
==Workflow Description==

The workflow describes the analysis and the fix of a specific instance of a PDF-HUL-133 error.
It is a manual workflow. The methodology used here is that introduced in https://hdl.handle.net/2142/121092.

'''Validation Error'''

JHOVE v1.30.0RC1 PDF-hul v1.12.5 PDF-HUL-133 Invalid Date. Well-formed, but not valid.

'''Cross-Check with other Tools'''

Cross-checked with:
pdfcpu v0.6.0dev relaxed mode - no error
pdfcpu v0.6.0dev strict mode - no error
qpdf v9.1.1 - no error
Arlington PDF Model checker by verapdf 1.26.0-RC1 Greenfield Parser:
Entry ModDate in DocInfo shall have type Date (1 occurance)
Entry CreationDate in DocInfo shall have type Date (1 occurance)
'''

'''Locate Error in Spec'''

ISO3200-2:2017 (PDF 2.0 Spec) lists the the Keys CreationDate and ModDate in the Document Info Dictionary as type Date.
Section 7.0.4 defines that a date shall be a text string containing no whitespace, of the form:
''(D:YYYYMMDDHHmmSSOHH'mm)
where:
YYYY shall be the year
MM shall be the month (01–12)
DD shall be the day (01–31)
HH shall be the hour (00–23)
mm shall be the minute (00–59)
SS shall be the second (00–59)
O shall be the relationship of local time to Universal Time (UT), and shall be denoted by one of the characters PLUS SIGN (U+002B) (+), HYPHEN-MINUS (U+002D) (-), or LATIN CAPITAL LETTER Z (U+005A) (Z) (see below)
HH followed by APOSTROPHE (U+0027) (') shall be the absolute value of the offset from UT in hours (00–23)
mm shall be the absolute value of the offset from UT in minutes (00–59)

The prefix D: shall be present, the year field (YYYY) shall be present and all other fields may be present but only if all of their preceding fields are also present. The APOSTROPHE following the hour offset field (HH) shall only be present if the HH field is present. The minute offset field (mm) shall only be present if the APOSTROPHE following the hour offset field (HH) is present. The default values for MM and DD shall be both 01; all other numerical fields shall default to zero values. A PLUS SIGN as the value of the O field signifies that local time is now and later than UT, a HYPHEN-MINUS signifies that local time is earlier than UT, and the LATIN CAPITAL LETTER Z signifies that local time is equal to UT. If no UT information is specified, the relationship of the specified time to UT shall be considered to be GMT. Regardless of whether the time zone is specified, the rest of the date shall be specified in local time.''

The specification further notes that ''versions up to and including 1.7 defined a date string to include a terminating apostrophe. PDF processors are recommended to accept date strings that still follow that convention''.

'''Locate Error in File
'''
Offset given by JHOVE can be navigated to using a hex editor such as HxD. The offset points to the Document Info Dictionary with /CreationDate (D:2018020915415409'00') and /ModDate(D:2018020915415409'00'). Mapping those dates to the notation given above it becomes clear that the O key which identifies the relation to UT is missing. Alternatively to looking for the dates in a hex editor, exiftool can be used to pull out all dates with:
exiftool -time:all -G -a -s file.pdf

''' Match?'''

Yes. Description in the spec and error in the file match. (D:2018020915415409'00') is missing the O key.

'''Fixable?'''

Yes. If other dates, e.g. in the XMP-section, are in the correct format, they can be used to determine the corect value for O. If not, the HH'MM' UT offset can be removed to form a valid date.

'''Fix'''

Option 1:
This option only works in the case of the missing O entry and the trailing apostrophe being present. In this case, the trailing apostrophe can be deleted and the O entry, if it can be determined from other dates, added to the value. This does not change the overall byte number of the date value and therefore has no impact on the PDF's internal structure.

Option 2:
The date can also be modified using exiftool. This will create an incremental update to the end of the file which can be rolled back with tools such as pdfressurect. Due to objects being added, the size of the file will change.
The exiftool command to e.g. update the dates above to include the O key + is:
exiftool -PDF:ModifyDate="2018:02:09 15:41:54+09:00" -PDF:CreateDate="2018:02:09 15:41:54+09:00" file.pdf
If you do not know the correct O key, you can also omit the offset with:
exiftool -PDF:ModifyDate="2018:02:09 15:41:54" -PDF:CreateDate="2018:02:09 15:41:54" file.pdf

'''Check'''

Re-validate file with Arlington PDF Model checker by veraPDF: Error messages are gone, no deviations found.
Re-validate file with JHOVE: Well-formed and valid with option 2. Well-formed but not valid with option 1, as JHOVE currently expects date in format pre-PDF2.0, i.e. without trailing apostrophe.

'''Success?'''

Yes.

[[File:PDF-hul-133 1.jpg|Workflow image]] 



==Purpose, Context and Content==

This workflow describes the analysis and treatment of JHOVE PDF-Hul error message PDF-HUL-133 Invalid date. It describes the process and results of a manual validation error analysis and treatment process.

==Evaluation/Review==

The workflow is effective and should be replicable for most invalid date related errors in PDFs. However, as an invalid date has little impact on the rendering behavior of the PDF file itself, institutions may decide to not fix the error.
Please note that most PDF Readers (e.g., Adobe Acrobat, Foxit) make use of XMP Metadata and not of Document Info Dictionary Metadata when they display Date Created and Last Modified Dates in a document's properties.

==Further Information==

Workflow:Validation Error Analysis and Treatment for PDF-hul 133 Invalid date

2024-05-08T17:16:04Z

Lindlar:

{{Infobox COW
|status=Production
|tools=ExifTool, HxD, Pdfcpu, Qpdf, JHOVE, veraPDF Arlington Model Checker
|input=File with JHOVE validation error PDF-HUL-133 “Invalid date"
|output=Fixed file
|organisation=TIB
|organisationurl=https://wiki.tib.eu/confluence/display/lza/Digital+preservation+at+TIB
}}
==Workflow Description==

The workflow describes the analysis and the fix of a specific instance of a PDF-HUL-133 error.
It is a manual workflow. The methodology used here is that introduced in https://hdl.handle.net/2142/121092.

'''Validation Error'''

JHOVE v1.30.0RC1 PDF-hul v1.12.5 PDF-HUL-133 Invalid Date. Well-formed, but not valid.

'''Cross-Check with other Tools'''

Cross-checked with:
pdfcpu v0.6.0dev relaxed mode - no error
pdfcpu v0.6.0dev strict mode - no error
qpdf v9.1.1 - no error
Arlington PDF Model checker by verapdf 1.26.0-RC1 Greenfield Parser:
Entry ModDate in DocInfo shall have type Date (1 occurance)
Entry CreationDate in DocInfo shall have type Date (1 occurance)
'''

'''Locate Error in Spec'''

ISO3200-2:2017 (PDF 2.0 Spec) lists the the Keys CreationDate and ModDate in the Document Info Dictionary as type Date.
Section 7.0.4 defines that a date shall be a text string containing no whitespace, of the form:
''(D:YYYYMMDDHHmmSSOHH'mm)
where:
YYYY shall be the year
MM shall be the month (01–12)
DD shall be the day (01–31)
HH shall be the hour (00–23)
mm shall be the minute (00–59)
SS shall be the second (00–59)
O shall be the relationship of local time to Universal Time (UT), and shall be denoted by one of the characters PLUS SIGN (U+002B) (+), HYPHEN-MINUS (U+002D) (-), or LATIN CAPITAL LETTER Z (U+005A) (Z) (see below)
HH followed by APOSTROPHE (U+0027) (') shall be the absolute value of the offset from UT in hours (00–23)
mm shall be the absolute value of the offset from UT in minutes (00–59)

The prefix D: shall be present, the year field (YYYY) shall be present and all other fields may be present but only if all of their preceding fields are also present. The APOSTROPHE following the hour offset field (HH) shall only be present if the HH field is present. The minute offset field (mm) shall only be present if the APOSTROPHE following the hour offset field (HH) is present. The default values for MM and DD shall be both 01; all other numerical fields shall default to zero values. A PLUS SIGN as the value of the O field signifies that local time is now and later than UT, a HYPHEN-MINUS signifies that local time is earlier than UT, and the LATIN CAPITAL LETTER Z signifies that local time is equal to UT. If no UT information is specified, the relationship of the specified time to UT shall be considered to be GMT. Regardless of whether the time zone is specified, the rest of the date shall be specified in local time.''

The specification further notes that ''versions up to and including 1.7 defined a date string to include a terminating apostrophe. PDF processors are recommended to accept date strings that still follow that convention''.

'''Locate Error in File
'''
Offset given by JHOVE can be navigated to using a hex editor such as HxD. The offset points to the Document Info Dictionary with /CreationDate (D:2018020915415409'00') and /ModDate(D:2018020915415409'00'). Mapping those dates to the notation given above it becomes clear that the O key which identifies the relation to UT is missing. Alternatively to looking for the dates in a hex editor, exiftool can be used to pull out all dates with:
exiftool -time:all -G -a -s file.pdf

''' Match?'''

Yes. Description in the spec and error in the file match. (D:2018020915415409'00') is missing the O key.

'''Fixable?'''

Yes. If other dates, e.g. in the XMP-section, are in the correct format, they can be used to determine the corect value for O. If not, the HH'MM' UT offset can be removed to form a valid date.

'''Fix'''

Option 1:
This option only works in the case of the missing O entry and the trailing apostrophe being present. In this case, the trailing apostrophe can be deleted and the O entry, if it can be determined from other dates, added to the value. This does not change the overall byte number of the date value and therefore has no impact on the PDF's internal structure.

Option 2:
The date can also be modified using exiftool. This will create an incremental update to the end of the file which can be rolled back with tools such as pdfressurect. Due to objects being added, the size of the file will change.
The exiftool command to e.g. update the dates above to include the O key + is:
exiftool -PDF:ModifyDate="2018:02:09 15:41:54+09:00" -PDF:CreateDate="2018:02:09 15:41:54+09:00" file.pdf
If you do not know the correct O key, you can also omit the offset with:
exiftool -PDF:ModifyDate="2018:02:09 15:41:54" -PDF:CreateDate="2018:02:09 15:41:54" file.pdf

'''Check'''

Re-validate file with Arlington PDF Model checker by veraPDF: Error messages are gone, no deviations found.
Re-validate file with JHOVE: Well-formed and valid with option 2. Well-formed but not valid with option 1, as JHOVE currently expects date in format pre-PDF2.0, i.e. without trailing apostrophe.

'''Success?'''

Yes.

[[File:PDF-hul-133 1.jpg|Textual description]] 



==Purpose, Context and Content==

This workflow describes the analysis and treatment of JHOVE PDF-Hul error message PDF-HUL-133 Invalid date. It describes the process and results of a manual validation error analysis and treatment process.

==Evaluation/Review==

The workflow is effective and should be replicable for most invalid date related errors in PDFs. However, as an invalid date has little impact on the rendering behavior of the PDF file itself, institutions may decide to not fix the error.
Please note that most PDF Readers (e.g., Adobe Acrobat, Foxit) make use of XMP Metadata and not of Document Info Dictionary Metadata when they display Date Created and Last Modified Dates in a document's properties.

==Further Information==

Workflow:Validation Error Analysis and Treatment for PDF-hul 133 Invalid date

2024-05-08T17:11:43Z

Lindlar:

{{Infobox COW
|status=Production
|tools=ExifTool, HxD, Pdfcpu, Qpdf, JHOVE, veraPDF Arlington Model Checker
|input=File with JHOVE validation error PDF-HUL-133 “Invalid date"
|output=Fixed file
|organisation=TIB
|organisationurl=https://wiki.tib.eu/confluence/display/lza/Digital+preservation+at+TIB
}}
==Workflow Description==

The workflow describes the analysis and the fix of a specific instance of a PDF-HUL-133 error.
It is a manual workflow. The methodology used here is that introduced in https://hdl.handle.net/2142/121092.

'''Validation Error'''

JHOVE v1.30.0RC1 PDF-hul v1.12.5 PDF-HUL-133 Invalid Date. Well-formed, but not valid.

'''Cross-Check with other Tools'''

Cross-checked with:
pdfcpu v0.6.0dev relaxed mode - no error
pdfcpu v0.6.0dev strict mode - no error
qpdf v9.1.1 - no error
Arlington PDF Model checker by verapdf 1.26.0-RC1 Greenfield Parser:
Entry ModDate in DocInfo shall have type Date (1 occurance)
Entry CreationDate in DocInfo shall have type Date (1 occurance)
'''

'''Locate Error in Spec'''

ISO3200-2:2017 (PDF 2.0 Spec) lists the the Keys CreationDate and ModDate in the Document Info Dictionary as type Date.
Section 7.0.4 defines that a date shall be a text string containing no whitespace, of the form:
''(D:YYYYMMDDHHmmSSOHH'mm)
where:
YYYY shall be the year
MM shall be the month (01–12)
DD shall be the day (01–31)
HH shall be the hour (00–23)
mm shall be the minute (00–59)
SS shall be the second (00–59)
O shall be the relationship of local time to Universal Time (UT), and shall be denoted by one of the characters PLUS SIGN (U+002B) (+), HYPHEN-MINUS (U+002D) (-), or LATIN CAPITAL LETTER Z (U+005A) (Z) (see below)
HH followed by APOSTROPHE (U+0027) (') shall be the absolute value of the offset from UT in hours (00–23)
mm shall be the absolute value of the offset from UT in minutes (00–59)

The prefix D: shall be present, the year field (YYYY) shall be present and all other fields may be present but only if all of their preceding fields are also present. The APOSTROPHE following the hour offset field (HH) shall only be present if the HH field is present. The minute offset field (mm) shall only be present if the APOSTROPHE following the hour offset field (HH) is present. The default values for MM and DD shall be both 01; all other numerical fields shall default to zero values. A PLUS SIGN as the value of the O field signifies that local time is now and later than UT, a HYPHEN-MINUS signifies that local time is earlier than UT, and the LATIN CAPITAL LETTER Z signifies that local time is equal to UT. If no UT information is specified, the relationship of the specified time to UT shall be considered to be GMT. Regardless of whether the time zone is specified, the rest of the date shall be specified in local time.''

The specification further notes that ''versions up to and including 1.7 defined a date string to include a terminating apostrophe. PDF processors are recommended to accept date strings that still follow that convention''.

'''Locate Error in File
'''
Offset given by JHOVE can be navigated to using a hex editor such as HxD. The offset points to the Document Info Dictionary with /CreationDate (D:2018020915415409'00') and /ModDate(D:2018020915415409'00'). Mapping those dates to the notation given above it becomes clear that the O key which identifies the relation to UT is missing. Alternatively to looking for the dates in a hex editor, exiftool can be used to pull out all dates with:
exiftool -time:all -G -a -s file.pdf

''' Match?'''

Yes. Description in the spec and error in the file match. (D:2018020915415409'00') is missing the O key.

'''Fixable?'''

Yes. If other dates, e.g. in the XMP-section, are in the correct format, they can be used to determine the corect value for O. If not, the HH'MM' UT offset can be removed to form a valid date.

'''Fix'''

Option 1:
This option only works in the case of the missing O entry and the trailing apostrophe being present. In this case, the trailing apostrophe can be deleted and the O entry, if it can be determined from other dates, added to the value. This does not change the overall byte number of the date value and therefore has no impact on the PDF's internal structure.

Option 2:
The date can also be modified using exiftool. This will create an incremental update to the end of the file which can be rolled back with tools such as pdfressurect. Due to objects being added, the size of the file will change.
The exiftool command to e.g. update the dates above to include the O key + is:
exiftool -PDF:ModifyDate="2018:02:09 15:41:54+09:00" -PDF:CreateDate="2018:02:09 15:41:54+09:00" file.pdf
If you do not know the correct O key, you can also omit the offset with:
exiftool -PDF:ModifyDate="2018:02:09 15:41:54" -PDF:CreateDate="2018:02:09 15:41:54" file.pdf

'''Check'''

Re-validate file with Arlington PDF Model checker by veraPDF: Error messages are gone, no deviations found.
Re-validate file with JHOVE: Well-formed and valid with option 2. Well-formed but not valid with option 1, as JHOVE currently expects date in format pre-PDF2.0, i.e. without trailing apostrophe.

'''Success?'''

Yes.

[[File:PDF-hul-122 1.jpg|Textual description]] 



==Purpose, Context and Content==

This workflow describes the analysis and treatment of JHOVE PDF-Hul error message PDF-HUL-133 Invalid date. It describes the process and results of a manual validation error analysis and treatment process.

==Evaluation/Review==

The workflow is effective and should be replicable for most invalid date related errors in PDFs. However, as an invalid date has little impact on the rendering behavior of the PDF file itself, institutions may decide to not fix the error.
Please note that most PDF Readers (e.g., Adobe Acrobat, Foxit) make use of XMP Metadata and not of Document Info Dictionary Metadata when they display Date Created and Last Modified Dates in a document's properties.

==Further Information==

Workflow:Validation Error Analysis and Treatment for PDF-hul 133 Invalid date

2024-05-08T16:41:39Z

Lindlar: Created page with '{{Infobox COW |status=Production |tools=ExifTool, HxD, Pdfcpu, Qpdf, JHOVE, veraPDF Arlington Model Checker |input=File with JHOVE validation error PDF-HUL-133 “Invalid date...'

Workflow:Validation Error Analysis and Treatment for PDF-hul 122 Invalid destination - Destination NULL

2024-01-21T19:45:16Z

Lindlar:

{{Infobox COW
|status=Production
|tools=Pdfcpu, Qpdf, JHOVE, Adobe Acrobat Pro, PDF Checker
|input=File with JHOVE validation error PDF-HUL-122 “Invalid Destination” / Well-Formed, but not valid.
This specific workflow documents the sample treatment for a file currently found here: https://www.schleswig-holstein.de/DE/landesregierung/ministerien-behoerden/VIII/Service/Broschueren/Broschueren_VIII/Kita/Mein_Kind_kommt_in_die_Kita_Rechte.pdf?__blob=publicationFile&v=2
|output=Fixed file
|organisation=TIB
|organisationurl=https://wiki.tib.eu/confluence/display/lza/Digital+preservation+at+TIB
}}
==Workflow Description==



The workflow describes the analysis and the fix of a specific instance of a PDF-HUL-122 error.
 CAUTION! PDF-HUL-122 errors can be very different in nature and impact. 
The process described here can be used for internal document links that are not working. It is a manual workflow. More information about this specific case has been discussed in a blog. The methodology used here is that introduced in https://hdl.handle.net/2142/121092.

'''Step 1: Validation Error'''

JHOVE v1.28 PDF-hul v1.12.4 PDF-HUL-122 Invalid Destination with offset given. Well-formed, but not valid.

'''Step 2: Cross-Check with other Tools'''

Cross-checked with:
pdfcpu v0.6.0dev relaxed mode - no error
pdfcpu v0.6.0dev strict mode - unrelated error (Font error)
qpdf v9.1.1 - no error
PDF Checker 2.1.0 - no error
'''
Step 3: Matching Results?'''

No. Error not reported by other tools, most likely due to low priority of error (only impacts validity, not well-formedness).
One additional un-related error picked up.

'''Step 4: Choose Error to Treat'''

Original PDF-HUL-122. Ignore Font error.

'''Step 5A: Locate Error in Spec'''

ISO 32000-2:2017 12.3.2.4 Named destinations must contain name as well as target destination. In case of internal destinations this is typically an object reference.

'''Step 5B: Locate Error in File
'''
Offset given by JHOVE only points to place where reference was used in GoTo destination. The reader tries to resolved the named destination used in the GoTo action via the name tree. Here the object is missing and replaced by "Null".
(Rechte_von_Eltern_in_der_Kita_2018_V7_bf.indd:.45593:62)[null/Fit ]

'''Step 6: Match?'''

Yes.

'''Step 7: Fixable?'''

Yes.

'''Step 8: Fix'''

Find location by checking page object the wrong destination is used on. With Adobe Acrobat Pro's "Edit Link" option, the erronous link can be removed and replaced by a correct one, if known.

'''Step 9: Check'''

Re-validated file with JHOVE: now well-formed and valid. Link is now actionable.

'''Step 10: Success?'''

Yes.

[[File:PDF-hul-122 1.jpg|Textual description]] 



==Purpose, Context and Content==

This workflow describes the analysis and treatment of JHOVE PDF-Hul error message PDF-HUL-122 Invalid destination. It describes the process and results of a manual validation error analysis.

==Evaluation/Review==

The workflow is effective for this specific instance of the error. It should be replicable for pdfs with similar invalid destination problems, i.e., internal links have been replaced with NULL. However, the fix needs to be considered carefully as it impacts the internal structure of the PDF file.

==Further Information==

See a further discussion of this in the OPF blog:

Workflow:Validation Error Analysis and Treatment for PDF-hul 122 Invalid destination - Destination NULL

2024-01-21T19:40:55Z

Lindlar:

{{Infobox COW
|status=Production
|tools=Pdfcpu, Qpdf, JHOVE, Adobe Acrobat Pro, PDF Checker
|input=File with JHOVE validation error PDF-HUL-122 “Invalid Destination” / Well-Formed, but not valid.
This specific workflow documents the sample treatment for a file currently found here: https://www.schleswig-holstein.de/DE/landesregierung/ministerien-behoerden/VIII/Service/Broschueren/Broschueren_VIII/Kita/Mein_Kind_kommt_in_die_Kita_Rechte.pdf?__blob=publicationFile&v=2
|output=Fixed file
|organisation=TIB
|organisationurl=https://wiki.tib.eu/confluence/display/lza/Digital+preservation+at+TIB
}}
==Workflow Description==



The workflow describes the analysis and the fix of a specific instance of a PDF-HUL-122 error.
 CAUTION! PDF-HUL-122 errors can be very different in nature and impact. 
The process described here can be used for internal document links that are not working. It is a manual workflow. More information about this specific case has been discussed in a blog. The methodology used here is that introduced in https://hdl.handle.net/2142/121092.

Step 1: Validation Error

JHOVE v1.28 PDF-hul v1.12.4 PDF-HUL-122 Invalid Destination with offset given. Well-formed, but not valid.

Step 2: Cross-Check with other Tools

Cross-checked with:
pdfcpu v0.6.0dev relaxed mode - no error
pdfcpu v0.6.0dev strict mode - unrelated error (Font error)
qpdf v9.1.1 - no error
PDF Checker 2.1.0 - no error

Step 3: Matching Results?

No. Error not reported by other tools, most likely due to low priority of error (only impacts validity, not well-formedness).
One additional un-related error picked up.

Step 4: Choose Error to Treat

Original PDF-HUL-122. Ignore Font error.

Step 5A: Locate Error in Spec

ISO 32000-2:2017 12.3.2.4 Named destinations must contain name as well as target destination. In case of internal destinations this is typically an object reference.

Step 5B: Locate Error in File

Offset given by JHOVE only points to place where reference was used in GoTo destination. The reader tries to resolved the named destination used in the GoTo action via the name tree. Here the object is missing and replaced by "Null".
(Rechte_von_Eltern_in_der_Kita_2018_V7_bf.indd:.45593:62)[null/Fit ]

Step 6: Match?

Yes.

Step 7: Fixable?

Yes.

Step 8: Fix

Find location by checking page object the wrong destination is used on. With Adobe Acrobat Pro's "Edit Link" option, the erronous link can be removed and replaced by a correct one, if known.

Step 9: Check

Re-validated file with JHOVE: now well-formed and valid. Link is now actionable.

Step 10: Success?

Yes.

[[File:PDF-hul-122 1.jpg|Textual description]] 



==Purpose, Context and Content==


==Evaluation/Review==


==Further Information==

Workflow:Validation Error Analysis and Treatment for PDF-hul 122 Invalid destination - Destination NULL

2024-01-21T19:25:02Z

Lindlar: Created page with "{{Infobox COW |status=Production |tools=Pdfcpu, Qpdf, JHOVE, Adobe Acrobat Pro, PDF Checker |input=File with JHOVE validation error PDF-HUL-122 “Invalid Destination” / Wel..."

File:PDF-hul-122 1.jpg

2024-01-21T19:23:51Z

Lindlar:

MD5Checker

2022-10-22T13:56:04Z

Lindlar: /* Description */

{{Infobox tool
|purpose=Lightweight Windows Desktop application to create and check MD5 Digests for one or several files.
|homepage=http://getmd5checker.com/
|license=All rights reserved
|cost=Free
|platforms=Windows
|language=English and Simplified Chinese versions available
|function=Fixity
}}
{{Infobox tool details}}
== Description ==

Md5Checker is a free, lightweight and easy-to-use GUI tool to manage, calculate and verify MD5 checksum of one or several files/folders.
Program is for Windows plattform only and consists of a single, small .exe File (300 KB), which makes it portable.

[[File:Md5checker.png|thumb|Screenshot of md5checker GUI]]

== User Experiences ==

MD5Checker

2022-10-22T13:53:48Z

Lindlar:

File:Md5checker.png

2022-10-22T13:52:47Z

Lindlar: Screenshot from Md5checker tool

== Summary ==
Screenshot from Md5checker tool

MD5Checker

2022-10-22T13:51:23Z

Lindlar: Created page with "{{Infobox tool |purpose=Lightweight Windows Desktop application to create and check MD5 Digests for one or several files. |homepage=http://getmd5checker.com/ |license=All righ..."

{{Infobox tool
|purpose=Lightweight Windows Desktop application to create and check MD5 Digests for one or several files.
|homepage=http://getmd5checker.com/
|license=All rights reserved
|cost=Free
|platforms=Windows
|language=English and Simplified Chinese versions available
|function=Fixity
}}
{{Infobox tool details}}
== Description ==

Md5Checker is a free, lightweight and easy-to-use GUI tool to manage, calculate and verify MD5 checksum of one or several files/folders.
Program is for Windows plattform only and consists of a single, small .exe File (300 KB), which makes it portable.

== User Experiences ==

DBPTK Developer

2022-05-23T09:21:00Z

Lindlar:

{{Infobox tool
|image=DBPTK_developer.png
|purpose=DBPTK Developer - library and command-line tool for exection of database preservation actions
|homepage=https://database-preservation.com/
|sourcecode=https://github.com/keeps/dbptk-developer
|license=GNU LESSER GENERAL PUBLIC LICENSE
|language=Java
|formats_in=MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server, Microsoft Access, Progress OpenEdge, Sybase ASA
|formats_out=SIARD1, SIARD2, SIARD DK
|function=Validation, File Format Migration
}}
{{Infobox tool details}}
== Description ==

The Database Preservation Toolkit allows conversion between Database formats, including connection to live systems, for purposes of digitally preserving databases. The toolkit allows conversion of live or backed-up databases into preservation formats such as SIARD, a XML-based format created for the purpose of database preservation. The toolkit also allows conversion of the preservation formats back into live systems to allow the full functionality of databases.

This toolkit was part of the RODA project and now has been released as a project by its own due to the increasing interest on this particular feature. It is now being further developed in the EARK project together with a new version of the SIARD preservation format.

The toolkit is created as a platform that uses input and output modules. Each module supports read and/or write to a particular database format or live system. New modules can easily be added by implementation of a new interface and adding of new drivers.

== User Experiences ==

File:DBPTK developer.png

2022-05-23T09:20:06Z

Lindlar:

DBPTK Developer

2022-05-23T09:19:21Z

Lindlar: Created page with "{{Infobox tool |image=DBTPK_Developer.png |purpose=DBPTK Developer - library and command-line tool for exection of database preservation actions |homepage=https://database-pre..."

{{Infobox tool
|image=DBTPK_Developer.png
|purpose=DBPTK Developer - library and command-line tool for exection of database preservation actions
|homepage=https://database-preservation.com/
|sourcecode=https://github.com/keeps/dbptk-developer
|license=GNU LESSER GENERAL PUBLIC LICENSE
|language=Java
|formats_in=MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server, Microsoft Access, Progress OpenEdge, Sybase ASA
|formats_out=SIARD1, SIARD2, SIARD DK
|function=Validation, File Format Migration
}}
{{Infobox tool details}}
== Description ==

The Database Preservation Toolkit allows conversion between Database formats, including connection to live systems, for purposes of digitally preserving databases. The toolkit allows conversion of live or backed-up databases into preservation formats such as SIARD, a XML-based format created for the purpose of database preservation. The toolkit also allows conversion of the preservation formats back into live systems to allow the full functionality of databases.

This toolkit was part of the RODA project and now has been released as a project by its own due to the increasing interest on this particular feature. It is now being further developed in the EARK project together with a new version of the SIARD preservation format.

The toolkit is created as a platform that uses input and output modules. Each module supports read and/or write to a particular database format or live system. New modules can easily be added by implementation of a new interface and adding of new drivers.

== User Experiences ==

ADIGRES

2021-10-19T11:17:49Z

Lindlar:

{{Infobox tool
|purpose=ADIGRES is a powerful cross-platform Document Management System written in Java.
|homepage=http://sourceforge.net/projects/adigres
|function=Access, File Management, Storage
|content=Document
}}
{{Infobox tool details
|ohloh_id=p_d_7823
}}
= Description =
ADIGRES is a powerful cross-platform Document Management System written in Java. It can be used to archive various document formats such as HTML, PDF, e-mail, plain-text or images. A user management module and a full-text search engine are included.

= User Experiences =

= Development Activity =

ADIGRES

2021-10-19T11:17:24Z

Lindlar:

{{Infobox tool
|purpose=ADIGRES is a powerful cross-platform Document Management System written in Java.
|homepage=http://sourceforge.net/projects/adigres
|function=Access, File Management, Storage
|content=Document
}}
{{Infobox tool details
|ohloh_id=ADIGRES
}}
= Description =
ADIGRES is a powerful cross-platform Document Management System written in Java. It can be used to archive various document formats such as HTML, PDF, e-mail, plain-text or images. A user management module and a full-text search engine are included.

= User Experiences =

= Development Activity =

ACE (Audit Control Environment)

2021-10-19T11:16:12Z

Lindlar:

{{Infobox tool
|purpose=The Auditing Control Environment is a mature set of software designed to help libraries and archives prove their holdings are intact and trustworthy.
|homepage=https://wiki.umiacs.umd.edu/adapt/index.php/Ace:Main
|license=Apache License
|platforms=Web-based and platform independent. Requires Java 1.6 or later; Tomcat 6.0 or later; MySQL 4.0 or later; and MySQL connector 5.0.7 or better
|function=Fixity
}}
{{Infobox tool details
|ohloh_id=ace
}}
= Description =
The Audit Control Environment is a mature set of software designed to help librarys and archives prove their holdings are intact and trustworthy. Recent developments of ACE include a new token store format to allow ACE tokens to be easily exported, transferred, and independently verified by third parties. To support the ACE tokens a python proof of concept has been developed to allow 3rd parties to write their own file validation routines using ACE tokens. Developed by University of Maryland. Written in Java.

= User Experiences =

* I deployed ACE-AM a few years ago, in it's servlet form, and it worked pretty well. The only problem was that for very large collections (millions of individual files) it would start to fall over due to running out of RAM. There is no technical need to keep the entire collection's checksum data in memory (as the system has a database available), so this could easily have been fixed by now. If this is a potential concern, I recommend monitoring memory usage as part of a large-scale test during evaluation. [[User:Andy Jackson|Andy Jackson]] ([[User talk:Andy Jackson|talk]]) 11:02, 11 September 2014 (UTC)
* [https://groups.google.com/forum/#!topic/digital-curation/ZT21Ac1aLQQ Discussion of fixity tools, including ACE on the Digital Curation google groups]

= Development Activity =

7train

2021-10-19T11:04:30Z

Lindlar:

{{Infobox tool
|purpose=XSLT 2.0 tool for generating METS files from XML input
|homepage=http://seventrain.sourceforge.net/
|license=BSD License
|formats_out=METS (Metadata Encoding and Transmission Standard)
|function=Metadata Processing
|content=Metadata
}}
{{Infobox tool details
|ohloh_id=seventrain
}}
== Description ==

An XSLT 2.0 tool for generating METS files from XML input. It builds the basic METS structure so that the user can worry about what is specific to the user's project. It includes (and was first built for) a complete transformation from ContentDM XML export.

== User Experiences ==


== Development Activity ==


Development stopped. Last commit was done in 2012-12-12.

Commits in SourceForge : https://sourceforge.net/p/seventrain/code/commit_browser

EmbARC

2021-09-27T06:47:00Z

Lindlar:

{{Infobox tool
|image={{PAGENAMEE}}.png
|purpose=internal file metadata management including embedding and validation
|homepage=http://www.digitizationguidelines.gov/guidelines/embARC.html
|license=CC0 1.0 Public Domain
|platforms=Windows, Mac
|function=Metadata Processing, Quality Assurance
|content=Video
}}
{{Infobox tool details}}




== Description ==

embARC (“metadata embedded for archival content”) manages internal file metadata including embedding and validation. Created by [http://www.digitizationguidelines.gov/ FADGI] (Federal Agencies Digital Guidelines Initiative), in conjunction with [https://www.weareavp.com/ AVP] and [https://www.portalmedia.com/ PortalMedia], embARC features flexible options for DPX (Digital Picture Exchange) and MXF (Material Exchange Format) files to support FADGI’s Guidelines.

Guidelines implemented in validation routines within in embARC are currently:
* [http://www.digitizationguidelines.gov/guidelines/digitize-DPXembedding.html Guidelines for Embedded Metadata within DPX File Headers for Digitized Motion Picture Film]
* required SMPTE 268 metadata rules
* [http://www.digitizationguidelines.gov/guidelines/MXF_app_spec.html SMPTE RDD 48: MXF Archive and Preservation Format]

embARC enables users to audit and correct internal metadata of both individual files or an entire DPX sequence while not impacting the image data. Functionality for additional file formats is in development, including MXF files. embARC is developed in JAVA.

Further information about the software and release history is available at:
http://www.digitizationguidelines.gov/guidelines/embARC.html

== User Experiences ==

* [https://docs.google.com/document/d/1twXVvNwsQdc-u_kHyURyjmKQl3R7bOpYX_Po0uXJVXk/edit embARC GUI user guide]
* [https://docs.google.com/document/d/1lHL2ZQJ8Z2Yhpkjhk4ci0l0vHpsbjXgZZvr8umLSebM/edit embARC CLI user Guide]
* [https://blogs.loc.gov/thesignal/2021/09/fadgi-embarc/?loclr=eadpb Library of Congress Blog about v1 and CLI development]

== Development Activity ==



Current release is 1.0.0 for GUI and Version 0.2.0 beta for CLI.
Github repo: https://github.com/LibraryOfCongress/embARC
Windows and Mac builds: http://www.digitizationguidelines.gov/guidelines/embARC.html

EmbARC

2021-09-27T06:44:28Z

Lindlar:

{{Infobox tool
|image={{PAGENAMEE}}.png
|purpose=internal file metadata management including embedding and validation
|homepage=http://www.digitizationguidelines.gov/guidelines/embARC.html
|license=CC0 1.0 Public Domain
|platforms=Windows, Mac
|function=Metadata Processing, Quality Assurance
|content=Video
}}
{{Infobox tool details}}




== Description ==

embARC (“metadata embedded for archival content”) manages internal file metadata including embedding and validation. Created by [http://www.digitizationguidelines.gov/ FADGI] (Federal Agencies Digital Guidelines Initiative), in conjunction with [https://www.weareavp.com/ AVP] and [https://www.portalmedia.com/ PortalMedia], embARC features flexible options for DPX (Digital Picture Exchange) and MXF (Material Exchange Format) files to support FADGI’s Guidelines.

Guidelines implemented in validation routines within in embARC are currently:
* [http://www.digitizationguidelines.gov/guidelines/digitize-DPXembedding.html Guidelines for Embedded Metadata within DPX File Headers for Digitized Motion Picture Film]
* required SMPTE 268 metadata rules
* [http://www.digitizationguidelines.gov/guidelines/MXF_app_spec.html SMPTE RDD 48: MXF Archive and Preservation Format]

embARC enables users to audit and correct internal metadata of both individual files or an entire DPX sequence while not impacting the image data. Functionality for additional file formats is in development, including MXF files. embARC is developed in JAVA.

Further information about the software and release history is available at:
http://www.digitizationguidelines.gov/guidelines/embARC.html

== User Experiences ==

embARC GUI user guide:
https://docs.google.com/document/d/1twXVvNwsQdc-u_kHyURyjmKQl3R7bOpYX_Po0uXJVXk/edit

embARC CLI user Guide:
https://docs.google.com/document/d/1lHL2ZQJ8Z2Yhpkjhk4ci0l0vHpsbjXgZZvr8umLSebM/edit

Library of Congress Blog about v1 and CLI development: https://blogs.loc.gov/thesignal/2021/09/fadgi-embarc/?loclr=eadpb

== Development Activity ==



Current release is 1.0.0 for GUI and Version 0.2.0 beta for CLI.
Github repo: https://github.com/LibraryOfCongress/embARC
Windows and Mac builds: http://www.digitizationguidelines.gov/guidelines/embARC.html

EmbARC

2021-09-27T06:30:18Z

Lindlar:

{{Infobox tool
|image={{PAGENAMEE}}.png
|purpose=internal file metadata management including embedding and validation
|homepage=http://www.digitizationguidelines.gov/guidelines/embARC.html
|license=CC0 1.0 Public Domain
|platforms=Windows, Mac
|function=Metadata Processing, Quality Assurance
|content=Video
}}
{{Infobox tool details}}




== Description ==

embARC (“metadata embedded for archival content”) manages internal file metadata including embedding and validation. Created by [http://www.digitizationguidelines.gov/ FADGI] (Federal Agencies Digital Guidelines Initiative), in conjunction with [https://www.weareavp.com/ AVP] and [https://www.portalmedia.com/ PortalMedia], embARC features flexible options for DPX (Digital Picture Exchange) files to support FADGI’s Guidelines for Embedded Metadata within DPX File Headers for Digitized Motion Picture Film as well as required SMPTE 268 metadata rules. embARC enables users to audit and correct internal metadata of both individual files or an entire DPX sequence while not impacting the image data. Functionality for additional file formats is in development, including MXF files. embARC is developed in JAVA.

Further information about the software and release history is available at:
http://www.digitizationguidelines.gov/guidelines/embARC.html

== User Experiences ==

A google doc of the user guide is availabe at:
https://docs.google.com/document/d/1twXVvNwsQdc-u_kHyURyjmKQl3R7bOpYX_Po0uXJVXk/edit
Library of Congress Blog about v1 and CLI development: https://blogs.loc.gov/thesignal/2021/09/fadgi-embarc/?loclr=eadpb

== Development Activity ==



Current release is 1.0.0 for GUI and Version 0.2.0 beta for CLI.
Github repo: https://github.com/LibraryOfCongress/embARC
Windows and Mac builds: http://www.digitizationguidelines.gov/guidelines/embARC.html

ADC Test

2021-09-17T06:05:51Z

Lindlar:

{{Infobox tool
|purpose=Tests and reports on audio analog-to-digital converters
|homepage=https://www.weareavp.com/products/adctest/
|license=Public domain and licensed under a 3-Clause BSD license.
|platforms=Windows
|function=Validation
|content=Audio
}}
{{Infobox tool details}}
== Description ==

ADCTest is a free Windows-based open source application that tests and reports on audio analog-to-digital converters in accordance with Federal Agencies Digital Guidelines Initiative ([http://www.digitizationguidelines.gov/ FADGI]) established test methods and performance metrics.

The application was designed for simplicity and ease, with everyone from archivists to audio technicians in mind. ADCTest generates and analyzes test signals and provides simple pass/fail reporting along with detailed results to support users of diverse skill levels.

For the advanced user, all tests are fully customizable to allow test methods and reporting in addition to the FADGI guidelines.

== User Experiences ==

* Guidelines: Audio Digitization System Performance http://www.digitizationguidelines.gov/guidelines/digitize-audioperf.html
* Using FADGI's ADCTest for Quality Control in Outsourced Audio Digitization: https://blogs.loc.gov/thesignal/2021/09/fadgi-adctest

== Development Activity ==


ADCTest is maintained by [http://weareavp.com AVP] on [https://github.com/WeAreAVP/ADCTest GitHub].

DupeGuru

2021-05-02T12:36:49Z

Lindlar:

{{Infobox_tool
|purpose=A brief description
|image=dg_logo_big_med.png
|homepage=https://dupeguru.voltaicideas.net/
|license= GPL-3.0 License
|platforms=Cross-plattform with Windows, MacOS and Ubuntu builds available
|function=De-Duplication
}}






== Description ==

Cross-platform (Linux, OS X, Windows) GUI tool to find duplicate files in a system. Can scan either filenames using a fuzzy matching algorithm or contents. Results can be filtered, sorted, deleted, copied or moved.
Tool and matching engine is customizable and special modes are available:
* Music mode scans tags and shows music-specific info in the duplicate results window.
* Picture mode scans pictures fuzzily, allowing to find pictures that are similar, but not exactly the same.

Supported languages: English, French, German, Chinese (Simplified), Czech, Italian, Armenian, Russian, Ukrainian, Brazilian, Vietnamese.

Witten mostly in Python3.

== User Experiences ==

GUI-View DupeGuru
[[File:Dupeguru screenshot start.png|thumb|Screenshot DupeGuru UI]]

== Development Activity ==


GitHub Repo: https://github.com/arsenetar/dupeguru/

OpenHub Record: https://www.openhub.net/p/dupeguru

{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=dupeguru
}}

File:Dupeguru screenshot start.png

2021-05-02T12:34:24Z

Lindlar: Screenshot DupeGuru Startpage

== Summary ==
Screenshot DupeGuru Startpage

File:Dg logo big med.png

2021-05-02T12:31:29Z

Lindlar: DupeGuru Logo

== Summary ==
DupeGuru Logo

DupeGuru

2021-05-02T12:30:33Z

Lindlar: Created page with " {{Infobox_tool |purpose=A brief description |image={{PAGENAMEE}}.png |homepage=https://dupeguru.voltai..."

{{Infobox_tool
|purpose=A brief description
|image={{PAGENAMEE}}.png
|homepage=https://dupeguru.voltaicideas.net/
|license= GPL-3.0 License
|platforms=Cross-plattform with Windows, MacOS and Ubuntu builds available
|function=De-Duplication
}}






== Description ==

Cross-platform (Linux, OS X, Windows) GUI tool to find duplicate files in a system. Can scan either filenames using a fuzzy matching algorithm or contents. Results can be filtered, sorted, deleted, copied or moved.
Tool and matching engine is customizable and special modes are available:
* Music mode scans tags and shows music-specific info in the duplicate results window.
* Picture mode scans pictures fuzzily, allowing to find pictures that are similar, but not exactly the same.

Supported languages: English, French, German, Chinese (Simplified), Czech, Italian, Armenian, Russian, Ukrainian, Brazilian, Vietnamese.

Witten mostly in Python3.

== User Experiences ==


== Development Activity ==


GitHub Repo: https://github.com/arsenetar/dupeguru/
OpenHub Record: https://www.openhub.net/p/dupeguru

{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=dupeguru
}}

JWAT

2020-10-01T13:01:08Z

Lindlar:

{{Infobox_tool
|purpose=Java Web Archive Toolkit
|image=
|homepage=http://jwat.org/
|license=Apache License, Version 2.0
|platforms=Java
}}


[[Category:Metadata Extraction]]
[[Category:Validation]]
[[Category:File Format Migration]]
[[Category:ARC To WARC Migration]]


[[Category:Web]]

== Description ==

An IIPC funded byproduct which can be used to read, validate and write ARC, WARC and GZip files.

Also includes the [https://sbforge.org/display/JWAT/JWAT-Tools JWAT Tools], which provides a command-line application for working with ARCs and WARCs, including conversion from ARC to WARC.

== User Experiences ==

* [http://wiki.opf-labs.org/display/SP/ARC2WARC+Experiment+at+ONB SCAPE ARC2WARC Experiment at ONB]
* [https://openpreservation.org/blogs/warc-validation-tool-experiences/?order=date%3ADESC&page=1 Comparison of different WARC Tools by National Archives of the Netherlands, 2020]

== Development Activity ==



{{Infobox_tool_details
|ohloh_id=jwat-tools
}}

Pdfcpu

2020-09-30T08:47:10Z

Lindlar:

{{Infobox_tool
|purpose=A Go library and command line tool for PDF processing incl. validation
|image=pdfcpuLogoSmall.png
|homepage=https://pdfcpu.io/
|license=Apache-2.0 License
|platforms=
}}



pdfcpu is a powerful Go library and command line tool that supports many PDF processing functions such as reading and writing the xref table, extracting images, fonts and embedded file attachments and encryption detection as well as decryption.
A full list of the command set is avaiable at:
https://pdfcpu.io/about/command_set

=== Validation ===
pdfcpu validates PDFs up to version 1.7. There are two different levels of validation, strict and relaxed, and the option to run validation in verbose mode which shows the output of the entire PDF syntax.

pdfcpu validate -mode strict this.pdf
validating(mode=strict) this.pdf ...
validation error (try -mode=relaxed): dict=type1FontDict required entry=FirstChar missing

pdfcpu validate -mode relaxed this.pdf
validating(mode=relaxed) this.pdf ...
validation ok

=== Metadata Extraction ===

Extraction of Metadata is possible in two ways. The argument ''info'' prints Information such as title, author, PDF producer, creation / modification data and some technical metadata such as encryption and permission information and whether the PDF is tagged, linearized or includes watermarks.
Sample output:

pdfcpu info this.pdf
PDF version: 1.6
Page count: 96
Page size: 21.00 x 29.70 cm
.........................................
Title: This is just a test
Author: Digiman
Subject:
PDF Producer: Adobe PDF Library 15.0
Content creator: Adobe InDesign CC 207 (Macintosh)
Creation date: D:20190912181416+02'00'
Modification date: D:20190918120753+02'00'
Keywords: key1
key2
..........................................
Tagged: Yes
Hybrid: No
Linearized: No
Using XRef streams: Yes
Using object streams: Yes
Watermarks: No
..........................................
Encrypted: No
Permissions: Full access

The second option is to extract any embedded metadata via the extract -mode meta flags. This creates txt files with the extracted metadata entries in a specified directory.
Sample output:

pdfcpu extract -mode meta this.pdf mdout
extracting metadata from this.pdf into mdout/ ...
writing mdout\this_Metadata_XObject_6499_6500.txt
writing mdout\this_Metadata_unknown_401_33.txt
writing mdout\this_Metadata_XObject_292_289.txt
writing mdout\this_Metadata_Catalog_6455_385.txt
writing mdout\this_Metadata_XObject_291_290.txt
writing mdout\this_Metadata_unknown_6491_6475.txt

== User Experiences ==


== Development Activity ==

pdfcpu has an active user and developer community. All activity can be viewed via the github repo:
[https://github.com/pdfcpu/pdfcpu https://github.com/pdfcpu/pdfcpu]


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

File:PdfcpuLogoSmall.png

2020-09-30T08:46:20Z

Lindlar:

Pdfcpu

2020-09-30T08:45:27Z

Lindlar: Created page with " {{Infobox_tool |purpose=A Go library and command line tool for PDF processing incl. validation |image=..."

{{Infobox_tool
|purpose=A Go library and command line tool for PDF processing incl. validation
|image={{PAGENAMEE}}.png
|homepage=https://pdfcpu.io/
|license=Apache-2.0 License
|platforms=
}}



pdfcpu is a powerful Go library and command line tool that supports many PDF processing functions such as reading and writing the xref table, extracting images, fonts and embedded file attachments and encryption detection as well as decryption.
A full list of the command set is avaiable at:
https://pdfcpu.io/about/command_set

=== Validation ===
pdfcpu validates PDFs up to version 1.7. There are two different levels of validation, strict and relaxed, and the option to run validation in verbose mode which shows the output of the entire PDF syntax.

pdfcpu validate -mode strict this.pdf
validating(mode=strict) this.pdf ...
validation error (try -mode=relaxed): dict=type1FontDict required entry=FirstChar missing

pdfcpu validate -mode relaxed this.pdf
validating(mode=relaxed) this.pdf ...
validation ok

=== Metadata Extraction ===

Extraction of Metadata is possible in two ways. The argument ''info'' prints Information such as title, author, PDF producer, creation / modification data and some technical metadata such as encryption and permission information and whether the PDF is tagged, linearized or includes watermarks.
Sample output:

pdfcpu info this.pdf
PDF version: 1.6
Page count: 96
Page size: 21.00 x 29.70 cm
.........................................
Title: This is just a test
Author: Digiman
Subject:
PDF Producer: Adobe PDF Library 15.0
Content creator: Adobe InDesign CC 207 (Macintosh)
Creation date: D:20190912181416+02'00'
Modification date: D:20190918120753+02'00'
Keywords: key1
key2
..........................................
Tagged: Yes
Hybrid: No
Linearized: No
Using XRef streams: Yes
Using object streams: Yes
Watermarks: No
..........................................
Encrypted: No
Permissions: Full access

The second option is to extract any embedded metadata via the extract -mode meta flags. This creates txt files with the extracted metadata entries in a specified directory.
Sample output:

pdfcpu extract -mode meta this.pdf mdout
extracting metadata from this.pdf into mdout/ ...
writing mdout\this_Metadata_XObject_6499_6500.txt
writing mdout\this_Metadata_unknown_401_33.txt
writing mdout\this_Metadata_XObject_292_289.txt
writing mdout\this_Metadata_Catalog_6455_385.txt
writing mdout\this_Metadata_XObject_291_290.txt
writing mdout\this_Metadata_unknown_6491_6475.txt

== User Experiences ==


== Development Activity ==

pdfcpu has an active user and developer community. All activity can be viewed via the github repo:
[https://github.com/pdfcpu/pdfcpu https://github.com/pdfcpu/pdfcpu]


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

OSFMount

2020-08-26T08:33:57Z

Lindlar:

{{Infobox_tool
|purpose=disk image file mounting
|image={{PAGENAMEE}}.png
|homepage=https://www.osforensics.com/tools/mount-disk-images.html
|license=Free software; Copyrighted by PassMark® Software Pty Ltd (‘PassMark’)
|platforms=Windows
}}



[[Category:Disk Imaging]]
[[Category:Forensic]]


[[Category:Disk Image]]

== Description ==

OSFMount allows you to mount local disk image files (bit-for-bit copies of an entire disk or disk partition) in Windows as a physical disk or a logical drive letter.
OSFMount is a 64-bit Windows utility. An older version (OSFMount V2.0.1001) is available for 32-bit as well.
While images are mounted as read-only per default, the tool also supports opening images in a "write cache" mode, where changes are written into a delta file.

The tool supports the following Windows image file formats:

{| class="wikitable"
|-
! scope"col"|Image Format
! scope"col"|Read
! scope"col"|Write
! scope"col"|Mount as RAM drive
! scope"col"|Convert to Image file
! scope"col"|Extend
! scope"col"|Format
|-
|Raw Image (.IMG, .DD)
|yes
|yes
|yes
|yes
|yes
|yes
|-
|Raw CD Image (.ISO, .BIN)
|yes
|no
|yes
|yes
|no
|no
|-
|Split Raw Image (.00n)
|yes
|yes
|yes
|no
|no
|yes
|-
|Nero Burning ROM Image (.NRG)
|yes
|yes
|yes
|no
|yes
|yes
|-
|System Deployment Image (.SDI)
|yes
|yes
|yes
|no
|yes
|yes
|-
|Advanced Forensics Format Images* (AFF) ´
|yes
|yes
|yes
|yes
|no
|yes
|-
|Advanced Forensics Format Images w/ meta data* (AFM)
|yes
|yes
|yes
|yes
|no
|yes
|-
|Advanced Forensics Format Directories* (AFD)
|yes
|yes
|yes
|yes
|no
|yes
|-
|VMWare Image (.VMDK)
|yes
|no
|yes
|no
|no
|no
|-
|EnCase EWF (.E01)
|yes
|no
|yes
|yes
|no
|no
|-
|SMART EWF (.S01)
|yes
|no
|yes
|yes
|no
|no
|-
|VHD Image (.VHD)
|yes
|no
|yes
|no
|no
|no
|-
|}
(*) The supported version of Advanced Forensics Format is AFFv3 with zlib compression support. Encryption and signatures are not supported.

== User Experiences ==


* Screenshot of version 3.0 showing mount drive options
[[File:OSFMount_1.png|550px|Screenshot of version 3.0 showing mount drive options]]

* Screenshot of version 3.0 showing available drive options
[[File:OSFMount_2.png|550px|Screenshot of version 3.0 showing available drive options]]

== Development Activity ==


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}
Release notes of current and previous versions are available via: https://www.osforensics.com/tools/mount-disk-images.html
Version history (visit website to see current history:
* v3.0.1006, 7 May 2020
* v3.0.1005, 29 Jul 2019
* v3.0.1005, 29 Jul 2019
* v3.0.1005, 29 Jul 2019
* v3.0.1004, 24 May 2019
* v3.0.1003, 10 May 2019
* v3.0.1002, 8 May 2019
* v3.0.1001, 17 Apr 2019
* v3.0.1000, 5 Apr 2019
* v2.0.1001, 21 Mar 2018
* v2.0.1000, 08 Mar 2018
* v1.5.1018, 18 Jan 2018
* v1.5.1017, 12 Dec 2017
* v1.5.1016, 27 Nov 2017
* v1.5.1015, 7 Feb 2014
* v1.5.1014, 22 Oct 2013
* v1.5.1013, 7 Mar 2013
* v1.5.1012, 27 Dec 2012
* v1.5.1011, 09 May 2012
* v1.5.1010, 03 Apr 2012
* v1.5.1009, 13 Mar 2012
* v1.5.1008, 22 Nov 2011
* v1.5.1007, 27 Jun 2011
* v1.5.1006, 16 Jun 2011
* v1.5.1005, 01 Jun 2011
* v1.5.1004, 25 Apr 2011
* v1.5.1003, 21 Apr 2011
* v1.5.1002, 20 Apr 2011
* v1.5.1001, 14 Apr 2011
* v1.5.1000, 16 Mar 2011
* v1.4.1005, 27 Jan 2011
* v1.4.1004, 21 Jan 2011
* v1.4.1003, 17 Dec 2010
* v1.4.1002, 15 Dec 2010
* v1.4.1001, 8 Dec 2010
* v1.4.1000, 6 Dec 2010
* v1.3.1000, 25 Oct 2010

OSFMount

2020-08-26T08:30:44Z

Lindlar:

{{Infobox_tool
|purpose=disk image file mounting
|image={{PAGENAMEE}}.png
|homepage=https://www.osforensics.com/tools/mount-disk-images.html
|license=Free software; Copyrighted by PassMark® Software Pty Ltd (‘PassMark’)
|platforms=Windows
}}



[[Category:Disk Imaging]]
[[Category:Forensic]]



== Description ==

OSFMount allows you to mount local disk image files (bit-for-bit copies of an entire disk or disk partition) in Windows as a physical disk or a logical drive letter.
OSFMount is a 64-bit Windows utility. An older version (OSFMount V2.0.1001) is available for 32-bit as well.
While images are mounted as read-only per default, the tool also supports opening images in a "write cache" mode, where changes are written into a delta file.

The tool supports the following Windows image file formats:

{| class="wikitable"
|-
! scope"col"|Image Format
! scope"col"|Read
! scope"col"|Write
! scope"col"|Mount as RAM drive
! scope"col"|Convert to Image file
! scope"col"|Extend
! scope"col"|Format
|-
|Raw Image (.IMG, .DD)
|yes
|yes
|yes
|yes
|yes
|yes
|-
|Raw CD Image (.ISO, .BIN)
|yes
|no
|yes
|yes
|no
|no
|-
|Split Raw Image (.00n)
|yes
|yes
|yes
|no
|no
|yes
|-
|Nero Burning ROM Image (.NRG)
|yes
|yes
|yes
|no
|yes
|yes
|-
|System Deployment Image (.SDI)
|yes
|yes
|yes
|no
|yes
|yes
|-
|Advanced Forensics Format Images* (AFF) ´
|yes
|yes
|yes
|yes
|no
|yes
|-
|Advanced Forensics Format Images w/ meta data* (AFM)
|yes
|yes
|yes
|yes
|no
|yes
|-
|Advanced Forensics Format Directories* (AFD)
|yes
|yes
|yes
|yes
|no
|yes
|-
|VMWare Image (.VMDK)
|yes
|no
|yes
|no
|no
|no
|-
|EnCase EWF (.E01)
|yes
|no
|yes
|yes
|no
|no
|-
|SMART EWF (.S01)
|yes
|no
|yes
|yes
|no
|no
|-
|VHD Image (.VHD)
|yes
|no
|yes
|no
|no
|no
|-
|}
(*) The supported version of Advanced Forensics Format is AFFv3 with zlib compression support. Encryption and signatures are not supported.

== User Experiences ==

Screenshot of version 3.0 showing mount drive options

[[File:OSFMount_1.png|550px]]

Screenshot of version 3.0 showing available drive options
[[File:OSFMount_2.png|550px]]

== Development Activity ==


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}
Release notes of current and previous versions are available via: https://www.osforensics.com/tools/mount-disk-images.html
Version history (visit website to see current history:
* v3.0.1006, 7 May 2020
* v3.0.1005, 29 Jul 2019
* v3.0.1005, 29 Jul 2019
* v3.0.1005, 29 Jul 2019
* v3.0.1004, 24 May 2019
* v3.0.1003, 10 May 2019
* v3.0.1002, 8 May 2019
* v3.0.1001, 17 Apr 2019
* v3.0.1000, 5 Apr 2019
* v2.0.1001, 21 Mar 2018
* v2.0.1000, 08 Mar 2018
* v1.5.1018, 18 Jan 2018
* v1.5.1017, 12 Dec 2017
* v1.5.1016, 27 Nov 2017
* v1.5.1015, 7 Feb 2014
* v1.5.1014, 22 Oct 2013
* v1.5.1013, 7 Mar 2013
* v1.5.1012, 27 Dec 2012
* v1.5.1011, 09 May 2012
* v1.5.1010, 03 Apr 2012
* v1.5.1009, 13 Mar 2012
* v1.5.1008, 22 Nov 2011
* v1.5.1007, 27 Jun 2011
* v1.5.1006, 16 Jun 2011
* v1.5.1005, 01 Jun 2011
* v1.5.1004, 25 Apr 2011
* v1.5.1003, 21 Apr 2011
* v1.5.1002, 20 Apr 2011
* v1.5.1001, 14 Apr 2011
* v1.5.1000, 16 Mar 2011
* v1.4.1005, 27 Jan 2011
* v1.4.1004, 21 Jan 2011
* v1.4.1003, 17 Dec 2010
* v1.4.1002, 15 Dec 2010
* v1.4.1001, 8 Dec 2010
* v1.4.1000, 6 Dec 2010
* v1.3.1000, 25 Oct 2010

File:OSFMount 2.png

2020-08-26T08:19:17Z

Lindlar:

File:OSFMount 1.png

2020-08-26T08:18:45Z

Lindlar:

OSFMount

2020-08-26T08:15:41Z

Lindlar: Created page with " {{Infobox_tool |purpose=disk image file mounting |image={{PAGENAMEE}}.png |homepage=https://www.osfore..."

{{Infobox_tool
|purpose=disk image file mounting
|image={{PAGENAMEE}}.png
|homepage=https://www.osforensics.com/tools/mount-disk-images.html
|license=Free software; Copyrighted by PassMark® Software Pty Ltd (‘PassMark’)
|platforms=Windows
}}



[[Category:Disk Imaging]]
[[Category:Forensic]]



== Description ==

OSFMount allows you to mount local disk image files (bit-for-bit copies of an entire disk or disk partition) in Windows as a physical disk or a logical drive letter.
OSFMount is a 64-bit Windows utility. An older version (OSFMount V2.0.1001) is available for 32-bit as well.
While images are mounted as read-only per default, the tool also supports opening images in a "write cache" mode, where changes are written into a delta file.

The tool supports the following Windows image file formats:

{|
!Image Format || Read || Write || Mount as RAM drive || Convert to Image file || Extend || Format ||
|-
|Raw Image (.IMG, .DD)
|yes
|yes
|yes
|yes
|yes
|yes
|-
|Raw CD Image (.ISO, .BIN)
|yes
|no
|yes
|yes
|no
|no
|-
|Split Raw Image (.00n)
|yes
|yes
|yes
|no
|no
|yes
|-
|Nero Burning ROM Image (.NRG)
|yes
|yes
|yes
|no
|yes
|yes
|-
|System Deployment Image (.SDI)
|yes
|yes
|yes
|no
|yes
|yes
|-
|Advanced Forensics Format Images* (AFF) ´
|yes
|yes
|yes
|yes
|no
|yes
|-
|Advanced Forensics Format Images w/ meta data* (AFM)
|yes
|yes
|yes
|yes
|no
|yes
|-
|Advanced Forensics Format Directories* (AFD)
|yes
|yes
|yes
|yes
|no
|yes
|-
|VMWare Image (.VMDK)
|yes
|no
|yes
|no
|no
|no
|-
|EnCase EWF (.E01)
|yes
|no
|yes
|yes
|no
|no
|-
|SMART EWF (.S01)
|yes
|no
|yes
|yes
|no
|no
|-
|VHD Image (.VHD)
|yes
|no
|yes
|no
|no
|no
|-
|}
(*) The supported version of Advanced Forensics Format is AFFv3 with zlib compression support. Encryption and signatures are not supported.

== User Experiences ==


== Development Activity ==


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}
Release notes of current and previous versions are available via: https://www.osforensics.com/tools/mount-disk-images.html
Version history (visit website to see current history:
* v3.0.1006, 7 May 2020
* v3.0.1005, 29 Jul 2019
* v3.0.1005, 29 Jul 2019
* v3.0.1005, 29 Jul 2019
* v3.0.1004, 24 May 2019
* v3.0.1003, 10 May 2019
* v3.0.1002, 8 May 2019
* v3.0.1001, 17 Apr 2019
* v3.0.1000, 5 Apr 2019
* v2.0.1001, 21 Mar 2018
* v2.0.1000, 08 Mar 2018
* v1.5.1018, 18 Jan 2018
* v1.5.1017, 12 Dec 2017
* v1.5.1016, 27 Nov 2017
* v1.5.1015, 7 Feb 2014
* v1.5.1014, 22 Oct 2013
* v1.5.1013, 7 Mar 2013
* v1.5.1012, 27 Dec 2012
* v1.5.1011, 09 May 2012
* v1.5.1010, 03 Apr 2012
* v1.5.1009, 13 Mar 2012
* v1.5.1008, 22 Nov 2011
* v1.5.1007, 27 Jun 2011
* v1.5.1006, 16 Jun 2011
* v1.5.1005, 01 Jun 2011
* v1.5.1004, 25 Apr 2011
* v1.5.1003, 21 Apr 2011
* v1.5.1002, 20 Apr 2011
* v1.5.1001, 14 Apr 2011
* v1.5.1000, 16 Mar 2011
* v1.4.1005, 27 Jan 2011
* v1.4.1004, 21 Jan 2011
* v1.4.1003, 17 Dec 2010
* v1.4.1002, 15 Dec 2010
* v1.4.1001, 8 Dec 2010
* v1.4.1000, 6 Dec 2010
* v1.3.1000, 25 Oct 2010

File:EmbARC.png

2019-10-05T07:35:23Z

Lindlar:

File:EmbARC-1.png

2019-10-05T07:34:38Z

Lindlar: Lindlar uploaded a new version of "File:EmbARC-1.png"

User:Lindlar

2019-10-05T07:29:19Z

Lindlar: Created page with "You can find me on [https://twitter.com/mickylindlar Twitter]"

You can find me on [https://twitter.com/mickylindlar Twitter]

File:EmbARC-1.png

2019-10-05T07:13:21Z

Lindlar:

EmbARC

2019-10-05T07:10:22Z

Lindlar: Created page with " {{Infobox_tool |purpose=Embedded metadata auditing and correction for DPX files |image={{PAGENAMEE}}.p..."

{{Infobox_tool
|purpose=Embedded metadata auditing and correction for DPX files
|image={{PAGENAMEE}}.png
|homepage=https://www.weareavp.com/products/embarc/
|license=CC0 1.0 Public Domain
|platforms=Windows, Mac
}}



[[Category:Metadata Processing]]
[[Category:Quality Assurance]]


[[Category:Video]]

== Description ==

embARC (Metadata Embedded for Archival Content)is a tool for metadata embedding and validation in DPX files. It currently supports checking against FADGI’s Guidelines for Embedded Metadata within DPX File Headers for Digitized Motion Picture Film as well as required SMPTE 268 metadata rules. embARC enables users to audit and correct internal metadata of both individual files or an entire DPX sequence while not impacting the image data.
embARC is created and maintained by FADGI (Federal Agencies Digital Guidelines Initiative), in conjunction with [https://www.weareavp.com/ AVP] and [https://www.portalmedia.com/ PortalMedia].

The tool wraps FFmpeg, CRC32C and uses Nitrite. It is developed in JAVA.

Further information about the software and release history is available at:
http://www.digitizationguidelines.gov/guidelines/embARC.html

== User Experiences ==

A google doc of the user guide is availabe at:
https://docs.google.com/document/d/1twXVvNwsQdc-u_kHyURyjmKQl3R7bOpYX_Po0uXJVXk/edit

== Development Activity ==


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}
Current release is 0.1.5 beta.
Github repo: https://github.com/LibraryOfCongress/embARC

AVP Fixity

2018-09-03T15:26:04Z

Lindlar:

{{Infobox_tool
|purpose=Fixity monitoring for digital collections
|homepage=https://www.weareavp.com/products/fixity/
|license=Apache 2.0
|platforms=Windows, Mac
}}


[[Category:Fixity]]



== Description ==

Fixity is a tool for monitoring file integrity and attendance over time. It is designed to be easy-to-use (GUI interface) and automated (scheduled checks, email alerts/reports) to help institutions ensure the integrity of their digital assets.

=== Provider ===
Fixity was developed and is maintained by [http://weareavp.com AVP].

== User Experiences ==

* Fixity User Group: https://groups.google.com/forum/#!forum/fixity-users
* Fixity Webinar https://www.weareavp.com/avp-webinar-series-fixity/
* Blog Post by Jenny Mitcham http://digital-archiving.blogspot.com/2018/07/checksum-or-fixity-which-tool-is-for-me.html

== Development Activity ==

The project repository is on [http://www.github.com/avpreserve/fixity Github]

ClairMeta

2018-06-11T08:01:37Z

Lindlar: Created page with " {{Infobox_tool |purpose=Clairmeta is a python package for Digital Cinema Package (DCP) probing and che..."

{{Infobox_tool
|purpose=Clairmeta is a python package for Digital Cinema Package (DCP) probing and checking.
|image={{PAGENAMEE}}.png
|homepage=https://github.com/Ymagis/ClairMeta
|license=BSD 3-Clause "New" or "Revised" License
|platforms=Should work on Windows, macOS, Linux, Tested on : macOS 10.12

}}






== Description ==

Clairmeta is a python package for Digital Cinema Package (DCP) probing and checking.
This project status is Beta, the following needs to be done for the release :
* Large scale tests on lots of DCPs (including D-Box, DVIs, OCAP, CCAP, ...)

'''Features'''
* DCP Probe : metadata extraction of the whole DCP, including all XML fields and MXF assets inspection.
* DCP Checker : advanced DCP validation tool, including (non exhaustive):
** SMPTE / Interop standard convention (naming, …)
** Integrity (MIME type, size, hash) of all assets
** Foreign file identification
** XSD Schema validation for XML files (VOLINDEX, ASSETMAP, CPL, PKL)
** Digital signature validation (CPL, PKL)
** Intra / Inter Reels integrity and coherence
** Metadata match between CPL assets and MXF headers
** Re-link VF / OV
** Picture tests : FrameRate, BitRate, …
** Sound tests : Channels, Sampling, …
** Subtitle : Deep inspection of Interop and SMPTE subtitles
* DSM / DCDM Checker : basic image file sequence validation with some specific rules.

'''Usage'''

ClairMeta can be used as a general command line tool as well as a python library.

Examples for command line calls:

python3 -m clairmeta.cli probe -type dcp path/to/dcp
python3 -m clairmeta.cli probe -type dcp path/to/dcp -format json > dcp.json
python3 -m clairmeta.cli probe -type dcp path/to/dcp -format xml > dcp.xml
python3 -m clairmeta.cli check -type dcp path/to/dcp

'''Installation / Dependencies'''

Installation notes are available on the github page: https://github.com/Ymagis/ClairMeta

Dependencies:
* Python
** Should work on python 2.7 and python 3.3+
** Tested on : python 2.7, python 3.6
* Platform
** Should work on Windows, macOS, Linux
** Tested on : macOS 10.12
* External (non-python) dependencies :
** libmagic
** asdcplib
** mediainfo (opt)
** sox (opt)

== User Experiences ==


== Development Activity ==

All development activity is visible on GitHub: https://github.com/Ymagis/ClairMeta/commits/develop

=== Release Feed ===
Below the last 3 release feeds:
<rss max=3>https://github.com/Ymagis/ClairMeta/releases.atom</rss>

=== Activity Feed ===
Below the last 5 commits:
<rss max=5>https://github.com/Ymagis/ClairMeta/commits/master.atom</rss>


{{Infobox_tool_details
|releases_rss=
|issues_rss=
|mailing_lists=
|ohloh_id=
}}

Exactly

2018-04-26T06:05:48Z

Lindlar:

{{Infobox_tool
|purpose=Packs data in BagIt bags and transfers them to/from remote location via FTP, SFTP
|image=Exactly-50-small-300x279.png
|homepage=https://www.weareavp.com/products/exactly/
|license=Apache License 2.0
|platforms=Mac and Windows
}}



[[Category:Transfer]]



== Description ==

Exactly allows to pack local data into BagIt bags and to transfer them to remote locations via FTP or SFTP protocol. While creating the bags, the users can choose to add user-info metadata which is added to tbe bag-info file. The UI offers reserved fields, such as source-organization, organization-adress, etc. per default, but also supports non-bagit fields to be added. Metadata profiles, (S)FTP parameters, email preferences and other settings can be stored in preset settings files for usage in client installations.
During bag creation, the user has the option to choose whether the bag should be zipped or not.
The tool integrates into desktop-based file sharing worfklows such as Dropbox or Google Transfer and is designed to assist data producers in easy data transfer to archiving institutions.

==== Provider ====
[https://www.weareavp.com/ AVP]

==== Licensing and cost ====
[https://www.apache.org/licenses/LICENSE-2.0 Apache License 2.0] – free.

== User Experiences ==

Exactly Users Google Group: https://groups.google.com/forum/#!forum/exactly-users

Exactly webinar: https://vimeo.com/200403270

== Development Activity ==


Exactly on Open Hub: https://www.openhub.net/p/exactly

All development activity is visible on github: https://github.com/WeAreAVP/uk-exactly/

{{Infobox_tool_details
|releases_rss=https://github.com/WeAreAVP/uk-exactly/releases.atom
|issues_rss=https://github.com/WeAreAVP/uk-exactly/issues.atom
|mailing_lists=https://groups.google.com/forum/#!forum/exactly-users
|ohloh_id=exactly
}}

Exactly

2018-04-26T05:49:47Z

Lindlar:

{{Infobox_tool
|purpose=Packs data in BagIt bags and transfers them to/from remote location via FTP, SFTP
|image=Exactly-50-small-300x279.png
|homepage=https://www.weareavp.com/products/exactly/
|license=Apache License 2.0
|platforms=Mac and Windows
}}



[[Category:Transfer]]



== Description ==

Exactly allows to pack local data into BagIt bags and to transfer them to remote locations via FTP or SFTP protocol. While creating the bags, the users can choose to add user-info metadata which is added to tbe bag-info file. The UI offers reserved fields, such as source-organization, organization-adress, etc. per default, but also supports non-bagit fields to be added. Metadata profiles, (S)FTP parameters, email preferences and other settings can be stored in preset settings files for usage in client installations.
During bag creation, the user has the option to choose whether the bag should be zipped or not.
The tool integrates into desktop-based file sharing worfklows such as Dropbox or Google Transfer and is designed to assist data producers in easy data transfer to archiving institutions.

== User Experiences ==

Exactly Users Google Group: https://groups.google.com/forum/#!forum/exactly-users

== Development Activity ==


Exactly on Open Hub: https://www.openhub.net/p/exactly

All development activity is visible on github: https://github.com/WeAreAVP/uk-exactly/

{{Infobox_tool_details
|releases_rss=https://github.com/WeAreAVP/uk-exactly/releases.atom
|issues_rss=https://github.com/WeAreAVP/uk-exactly/issues.atom
|mailing_lists=https://groups.google.com/forum/#!forum/exactly-users
|ohloh_id=exactly
}}

Exactly

2018-04-26T05:45:38Z

Lindlar:

{{Infobox_tool
|purpose=Packs data in BagIt bags and transfers them to/from remote location via FTP, SFTP
|image=Exactly-50-small-300x279.png
|homepage=https://www.weareavp.com/products/exactly/
|license=Apache License
|platforms=Mac and Windows
}}



[[Category:Transfer]]



== Description ==

Exactly allows to pack local data into BagIt bags and to transfer them to remote locations via FTP or SFTP protocol. While creating the bags, the users can choose to add user-info metadata which is added to tbe bag-info file. The UI offers reserved fields, such as source-organization, organization-adress, etc. per default, but also supports non-bagit fields to be added. Metadata profiles, (S)FTP parameters, email preferences and other settings can be stored in preset settings files for usage in client installations.
During bag creation, the user has the option to choose whether the bag should be zipped or not.
The tool integrates into desktop-based file sharing worfklows such as Dropbox or Google Transfer and is designed to assist data producers in easy data transfer to archiving institutions.

== User Experiences ==

Exactly Users Google Group: https://groups.google.com/forum/#!forum/exactly-users

== Development Activity ==


Exactly on Open Hub: https://www.openhub.net/p/exactly

All development activity is visible on github: https://github.com/WeAreAVP/uk-exactly/

{{Infobox_tool_details
|releases_rss=https://github.com/WeAreAVP/uk-exactly/releases.atom
|issues_rss=https://github.com/WeAreAVP/uk-exactly/issues.atom
|mailing_lists=https://groups.google.com/forum/#!forum/exactly-users
|ohloh_id=exactly
}}

File:Slide1.png

2018-04-26T05:39:46Z

Lindlar: Exactly transfer workflow

Exactly transfer workflow

File:Exactly-50-small-300x279.png

2018-04-26T05:38:54Z

Lindlar: Logo for Exactly

Logo for Exactly