[
https://issues.apache.org/jira/browse/PDFBOX-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johannes Manner updated PDFBOX-4196:
------------------------------------
Description:
We try to integrate xmp metadata in pdf files (bibliograhpy metadata written in
Latex) and read this metadata later on.
The problem in this case is, that sometimes only the year attribute is
specified, but the xmp metadata parsing within xmpbox creates calendar values
with defaults, especially the month attribute is critical for us.
Maybe an example is more informative:
<dc:date>
<rdf:Seq>
<rdf:li>2017-06</rdf:li>
</rdf:Seq>
</dc:date>
In this case, we are only interested in the year and month value. The day
value should be null or filled with a non-valid value like -1 or similar.
More problematic is the following case:
<dc:date>
<rdf:Seq>
<rdf:li>2017</rdf:li>
</rdf:Seq>
</dc:date>
Per default PDFBox fills the month with 1 -> January and my import recognices
this 1 as January, but the value is not present.
Our wish is, to have a functionality, where we can handle only information that
are present and not struggeling with default values.
was:
I try to integrate xmp metadata in pdf files (bibliograhpy metadata written in
Latex) and read this metadata later on.
The problem in this case is, that sometimes only the year attribute is
specified, but the xmp metadata parsing within xmpbox creates calendar values
with defaults, especially the month attribute is critical for us.
Maybe an example is more informative:
<dc:date>
<rdf:Seq>
<rdf:li>2017-06</rdf:li>
</rdf:Seq>
</dc:date>
In this case, we are only interested in the year and month value. The day value
should be null or filled with a non-valid value like -1 or similar.
More problematic is the following case:
<dc:date>
<rdf:Seq>
<rdf:li>2017</rdf:li>
</rdf:Seq>
</dc:date>
Per default PDFBox fills the month with 1 -> January and my import recognices
this 1 as January, but the value is not present.
Our wish is, to have a functionality, where we can handle only information that
are present and not struggeling with default values.
> getUnqualifiedSequenceDateValueList returns date with undesired default values
> ------------------------------------------------------------------------------
>
> Key: PDFBOX-4196
> URL: https://issues.apache.org/jira/browse/PDFBOX-4196
> Project: PDFBox
> Issue Type: Wish
> Components: XmpBox
> Affects Versions: 2.0.8
> Reporter: Johannes Manner
> Priority: Major
>
> We try to integrate xmp metadata in pdf files (bibliograhpy metadata written
> in Latex) and read this metadata later on.
> The problem in this case is, that sometimes only the year attribute is
> specified, but the xmp metadata parsing within xmpbox creates calendar values
> with defaults, especially the month attribute is critical for us.
> Maybe an example is more informative:
> <dc:date>
> <rdf:Seq>
> <rdf:li>2017-06</rdf:li>
> </rdf:Seq>
> </dc:date>
> In this case, we are only interested in the year and month value. The day
> value should be null or filled with a non-valid value like -1 or similar.
>
> More problematic is the following case:
> <dc:date>
> <rdf:Seq>
> <rdf:li>2017</rdf:li>
> </rdf:Seq>
> </dc:date>
> Per default PDFBox fills the month with 1 -> January and my import recognices
> this 1 as January, but the value is not present.
> Our wish is, to have a functionality, where we can handle only information
> that are present and not struggeling with default values.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
