Skip to content

Add Settings - Search - Index - Asset path #8221

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

Closed
TWQM opened this issue May 9, 2023 · 0 comments
Closed

Add Settings - Search - Index - Asset path #8221

TWQM opened this issue May 9, 2023 · 0 comments
Assignees
Milestone

Comments

@TWQM
Copy link

TWQM commented May 9, 2023

In what scenarios do you need this feature?

在我实际工作中会将文件归类放入assets下的子目录,当对子目录进行重新归类迁移时搜索assets并批量替换的操作非常重要。

我最开始使用思源笔记时也习惯将文件直接拖入,但使用一段时间后我发现大量文件集中在assets根目录下导致从文件夹寻找文件变得非常困难。

特别是在处理excel文件时,我希望可以直接通过打开文件夹的方式对其进行编辑,而不用每次都通过笔记搜索进行打开。

我使用手动导入文件的主要原因是我发现思源笔记的双链页面打开方式非常适合多领域协作,这比之前在多个文件目录中寻找快得多。即便使用everything有时也会想不起文件名导致查找失败。因此希望逐步将之前积累的资料从文件夹管理切换为笔记管理,配合OCR和文档内容检索逐步形成新的知识网络管理方法。

Describe the optimal solution

我想最佳的实现方案是将assets作为一个搜索类型,并在搜索框中的类型按钮中进行选择。

但我看到#8076 中提到这种方式实现困难,或许可以像是否区分大小写一样,将是否索引 asset hyperlinks 选项添加至设置中。

Describe the candidate solution

No response

Other information

No response

@88250 88250 self-assigned this May 10, 2023
@88250 88250 added this to the 2.8.8 milestone May 10, 2023
@88250 88250 changed the title Please include asset hyperlinks in the search index Add Settings - Search - Inlines - Asset link May 10, 2023
@88250 88250 changed the title Add Settings - Search - Inlines - Asset link Add Settings - Search - Inlines - Asset path May 10, 2023
@88250 88250 changed the title Add Settings - Search - Inlines - Asset path Add Settings - Search - Inline types - Asset path May 10, 2023
@88250 88250 changed the title Add Settings - Search - Inline types - Asset path Add Settings - Search - Index - Asset path May 10, 2023
88250 added a commit that referenced this issue May 10, 2023

Unverified

This user has not yet uploaded their public signing key.
@88250 88250 closed this as completed May 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants