-
Notifications
You must be signed in to change notification settings - Fork 458
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
Data and code availability statement zone #951
Conversation
…hConstant return type
…d the rest of the data statement body
…itt2/grobid into feature/data-availability-statement
Hi @lfoppiano ! I reviewed everything and made some few changes - in particular put back the header labels into Currently, when the availability statement is in the header, it is correctly labeled and stored in // data availability statements
StringBuilder dataAvailability = new StringBuilder();
if (StringUtils.isNotBlank(resHeader.getDataAvailability())) {
dataAvailability = getSectionAsTEI("availability", "\t\t\t", doc, TaggingLabels.HEADER_AVAILABILITY,
teiFormatter, resCitations, config);
} else {
dataAvailability = getSectionAsTEI("availability", "\t\t\t", doc, SegmentationLabels.AVAILABILITY,
teiFormatter, resCitations, config);
}
SortedSet<DocumentPiece> sectionPart = doc.getDocumentPart(taggingLabel); Only the To retrieve the layout tokens relative to the availability statement from the header stored in List<LayoutToken> headerAvailabilityStatementTokens = biblio.getLayoutTokens(TaggingLabels.HEADER_AVAILABILITY); |
Latest commits fixed the header availability statement TEI serialization. |
Recognition of data and code availability statements, either in the header or the end of an article and marking the section in a normalized place in the TEI result (similarly as the acknowledgement section).
This involves the segmentation model (to recognize the zone as an additional section after the main article body) and the header model (when the zone is located within the header).
Thanks @lfoppiano :D