Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

OneNote: read handwriting, images and SharePoint notebooks

Abierto
  • ¿Algo no está bien?
#1,284 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
ai, backend-api-design

Línea de trabajo

Start with intl/microsoft-onenote.json and connectors/binary-response.util.ts to understand the existing content and binary response paths. The proposal also requires tracing the connector layer and response-transform.util.ts opt-in pattern, then checking Microsoft Graph permissions and calibrating InkML coordinates on real pages. Done means resource retrieval, SharePoint and group notebook access, and optional page images with ink work within the stated response limits.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement
Problem

The OneNote adapter (intl/microsoft-onenote.json) reads a page through GET /me/onenote/pages/{id}/content, which returns HTML without ink. Many OneNote users write by hand with a pen (meeting notes, sketches, calculations), so the AI sees nothing of those pages. Embedded pictures and PDF printouts reach the AI only as <img> links to Graph that need the user's sign-in, so it cannot read them either.

Two smaller gaps in the same adapter:

  • Notebooks stored on SharePoint team sites (/sites/{id}/onenote, /groups/{id}/onenote) are not reachable; only /me/onenote is.
  • There is no tool to fetch a single page resource (image or printout).
Proposed Solution
  1. microsoft_onenote_get_resource (adapter JSON only): GET /me/onenote/resources/{id}/$value with the existing binary handling (connectors/binary-response.util.ts), so an image comes back as an MCP image content block that the model can read.
  2. SharePoint and group notebooks (adapter JSON only): list notebooks, sections and pages under /sites/{site-id}/onenote and /groups/{group-id}/onenote. Check which delegated permission Graph needs for these (likely Notes.Read.All / Notes.ReadWrite.All, admin consent) and document it in the adapter instructions.
  3. microsoft_onenote_get_page_image (engine change): render a page as PNG including ink.
    • Fetch content?includeinkML=true (HTML plus InkML).
    • Parse the InkML traces (fast-xml-parser, already a dependency) and draw each trace as an SVG path with its brush colour and width, scaled to page coordinates.
    • Fetch the page's images with the user's token and place them at their absolute positions.
    • Rasterise with @resvg/resvg-js (MPL-2.0, no browser needed); split tall pages into tiles of about 1,500 px on the long edge.
    • Return the typed text as text (as today) plus the image(s). Typed text is not drawn into the PNG; that would need a headless browser in the image.
    • Opt-in per tool through a config key (e.g. "render": "onenote-page"), following the opt-in pattern of decode / images in response-transform.util.ts, but run in the connector layer because it needs further authenticated Graph calls.
Alternatives Considered
  • Handwriting recognition on our side: not needed; current models read handwriting from images well, and Graph exposes no recognised text for ink.
  • Rendering the full page in headless Chromium: higher fidelity for typed text, but adds about 300 MB to the image and a lot of memory per render on the shared Cloud.
  • Returning raw InkML: the model cannot use stroke coordinates meaningfully.
Area

Connectors / adapters (Microsoft OneNote), REST engine.

Additional Context
  • Cloud and self-hosted behave the same; the new dependency ships in the backend image for both.
  • Size limits: the 10 MB tool response cap and the per-tool binary.maxBytes apply; tiles keep each image well below them.
  • InkML coordinate units need calibrating against real pages with pen input before release.
Lenguaje dominante
TypeScript
Estrellas
856
Forks
82
Merge medio
7 h 49 min
PR fusionados (30 d)
302

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de HelpCode-ai/anythingmcp

Todos los issues de HelpCode-ai/anythingmcp

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.