[
https://issues.apache.org/jira/browse/TIKA-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124667#comment-18124667
]
ASF GitHub Bot commented on TIKA-4944:
--------------------------------------
henry-lindeman-glean commented on PR #3278:
URL: https://github.com/apache/tika/pull/3278#issuecomment-6044617424
@tballison I think you meant to put [this
comment](https://github.com/apache/tika/pull/3277#issuecomment-5963874799) here
Anyway,
1 - easy fix, is done
2 - is asking me to test the link components against the test fixtures but
I'm pretty sure I don't have access to the test fixtures in onedrive... it
works with the files I tested with though.
3 - the classic walker was picking up a version-history page. In
test-tika-3970-dupetext.one, the extra page GUID {7B093AC2…} is only ever
reached as the root of its own object space; current pages are always reached
through MetaDataObjectsAboveGraphSpace. The classic walker now records page
GUIDs only when they're reached through that property, so the file yields one
page GUID. Turning the check off makes both new tests fail, as intended.
4 - added
sectionGuids is now sectionGuid
> Emit onenote page guids in properties
> -------------------------------------
>
> Key: TIKA-4944
> URL: https://issues.apache.org/jira/browse/TIKA-4944
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Reporter: Henry Lindeman
> Priority: Minor
>
> Onenote section files contain page GUIDs which can be used to reconstruct a
> url pointing to a page in the MS SaaS Onenote application. Since MS hands you
> the documents section at a time the only other way to get to the page GUID is
> to ask MS to list the pages in the section, which we'd prefer not to do
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
