-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
[Feature Request] Custom fields #530
Comments
For filename, i would say we really don’t recommend directly accessing papers via the OS file manager. Could you describe the reason why you do that? For searchable field, you can write your prefix in the note field. |
Yes, I agree with you. I would prefer to modify this prefix field and it is automatically added to the name without the direct access via the OS file manager, because I think it corrupt the linking between the file and the item. Also, when the file is renamed, it is easy to open the file directly using spotlight search in mac |
Ah, I got you, it's for spotlight. Currently, it's unsupported. But I would say I have a bigger plan for this. What if I add three custom fields for the metadata. {
title: string,
author: string,
...
customField1: {
name: string,
value: string
},
customField2: ...,
customField3: ...
} Users can rename the customField, input your prefered value via the editing view, and display it in the mainview. Also you can use it for the file renaming. Most importantly, It would be good for extension developers as they can display some custom information in the custom field. |
That looks a good idea! |
Add an extra field in the metadata for a prefix name of the document. This prefix name is assigned by the user. Sometimes, I want to add the method name (which is not simply the {firstchartitle})
So, I can create a custom renaming format like:
{prefix}-{title}.pdf
Also, this field would be great if it is searchable.
Great application, I really like it!
The text was updated successfully, but these errors were encountered: