Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

publication date not correctly extracted #109

Closed
Aazhar opened this issue Jul 28, 2016 · 1 comment · Fixed by #580
Closed

publication date not correctly extracted #109

Aazhar opened this issue Jul 28, 2016 · 1 comment · Fixed by #580
Labels
bug From Hemiptera and especially its suborder Heteroptera

Comments

@Aazhar
Copy link
Collaborator

Aazhar commented Jul 28, 2016

Grobid alter the publication date found from the publication, maybe it makes bad interpretations.
I've found the problem with this document https://hal.archives-ouvertes.fr/hal-00135377/document

which give me back
<publicationStmt> <date type="published" when="20077-03-07">7 Mar 2007 7th March 2007</date </publicationStmt>

@kermitt2 kermitt2 added the bug From Hemiptera and especially its suborder Heteroptera label Aug 11, 2016
@lfoppiano lfoppiano linked a pull request Jun 23, 2020 that will close this issue
@lfoppiano
Copy link
Collaborator

lfoppiano commented Aug 12, 2020

The dates seems now correct:

            <publicationStmt>
                <publisher/>
                <availability status="unknown">
                    <licence/>
                </availability>
                <date type="published" when="2007-03-07">7th March 2007</date>
            </publicationStmt>
                     <monogr>
                        <imprint>
                            <date type="published" when="2007-03-07">7th March 2007</date>
                        </imprint>
                    </monogr>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug From Hemiptera and especially its suborder Heteroptera
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants