You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/09/30 18:58:00 UTC
[jira] [Commented] (TIKA-4944) Emit onenote page guids in properties
[ https://issues.apache.org/jira/browse/TIKA-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18121305#comment-18121305 ]
ASF GitHub Bot commented on TIKA-4944:
--------------------------------------
henry-lindeman-glean opened a new pull request, #3278:
URL: https://github.com/apache/tika/pull/3278
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated!
Before opening the pull request, please verify that
* there is an open issue on the [Tika issue tracker](https://issues.apache.org/jira/projects/TIKA) which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes.
* the issue ID (`TIKA-XXXX`)
- is referenced in the title of the pull request
- and placed in front of your commit messages surrounded by square brackets (`[TIKA-XXXX] Issue or pull request title`)
* commits are squashed into a single one (or few commits for larger changes)
* Tika builds and unit tests pass with `./mvnw clean install` (`clean test` alone cannot resolve the pipes plugin zips)
* if you used a generative AI tool: follow the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) (`Generated-by: <tool>` in the commit message), and consider running the pre-flight in `.skills/devs/pr-review/SKILL.md` — fix what it finds; don't paste its report here
* there should be no conflicts when merging the pull request branch into the *recent* `main` branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled `main` branch
* if you add new module that downstream users will depend upon add it to relevant group in `tika-bom/pom.xml`.
We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the [Tika mailing list](http://tika.apache.org/mail-lists.html). Thanks!
```
❯ java -jar tika-app/target/tika-app-4.1.1-SNAPSHOT.jar -x ~/glean/tika/Downloadme/parsing-test-2/Section-1.one
INFO [main] 10:05:34,215 org.apache.tika.cli.TikaCLI As a convenience, TikaCLI has turned on several non-default features
as specified in tika-app/src/main/resources/tika-config-default-single-file.json.
See: TIKA-2374, TIKA-4017, TIKA-4354 and TIKA-4472).
This is not the default behavior in Tika generally or in tika-server.
INFO [main] 10:05:34,290 org.apache.tika.config.loader.TikaLoader temporary files go to java.io.tmpdir=/var/folders/r3/0ktdq26562d324x6wxwj10y40000gn/T
INFO [main] 10:05:36,375 org.apache.tika.config.loader.ParserLoader text recognizers: none found among the loaded parsers; images and rendered pages are not enriched
<?xml version="1.0" encoding="UTF-8"?><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="tk:content-type-magic-detected" content="application/onenote; format=one"/>
<meta name="tk:resource-name" content="Section-1.one"/>
<meta name="Content-Length" content="86561"/>
<meta name="tk:parsed-by" content="org.apache.tika.parser.CompositeParser"/>
<meta name="tk:parsed-by" content="org.apache.tika.parser.DefaultParser"/>
<meta name="tk:parsed-by" content="org.apache.tika.parser.microsoft.onenote.OneNoteParser"/>
<meta name="Content-Type" content="application/onenote; format=one"/>
<title/>
</head>
<body><div class="page" id="{0044A32F-B467-4A61-946C-765ADF524E8D}"><p>Page 1</p>
<p>Wednesday, August 12, 2026</p>
<p>10:24 AM</p>
<p>Text</p>
<p>More text</p>
<p>Bold Text</p>
<p>Italic Text</p>
<p>Underlined test</p>
<p>Red text</p>
<p>Highlighted text</p>
<p>ddd</p>
</div>
<div class="page" id="{01F78CA7-DD93-4208-861C-9034B28BA411}"><p>Page sdskgjhsdlf</p>
<p>Wednesday, August 12, 2026</p>
<p>10:26 AM</p>
<p>Bullet 1</p>
<p>Bullet 2</p>
<p>Indented bullet</p>
<p>Indented square</p>
<p>Number 1</p>
<p>Number 2</p>
<p>Letter a</p>
<p>Numeral I</p>
<p>Outdented number</p>
<p>More text</p>
<p>Table cell 1a</p>
<p>Table cell 4a</p>
<p>Table cell 2b</p>
<p>Table cell 3b</p>
<p>Table cell 4b</p>
<p>Comic sans</p>
<p>Dd</p>
<p>D</p>
</div>
</body></html>%
```
> 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)