nextcloud / nextcloud/fulltextsearch

attachment.date uses content created date of docx files

Open
#612 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
234
Forks
64
Avg merge
6h 18m
Merged PRs (30d)
10

Description

NC: 20.0.7
elasticsearch: 6.8
Full text search: 20.0.0
Full text search - Elasticsearch Platform: 20.0.0
Full text search - Files: 20.0.0

All my Word docx files are indexed with content created date from the meta data of the docx file. So the attachment.date always contains the content date created and not the last time I saved/modified this document.

Is it possible to configure it, to using the last modification/save time?
Is this an issue of nextcloud or an issue of the ingest-attachment plugin of elasticsearch?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how fulltextsearch handles the attachment.date field and how Elasticsearch's ingest-attachment plugin derives dates from DOCX metadata. Determine whether the last modification time is available and configurable, and whether the behavior belongs in Nextcloud or Elasticsearch. Done means the ownership and a supported way to index the modification date are established.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch, php
Domain
backend, search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.