AI Feature Request: use AI to manage tags/collections
complete
J
Jason Costanza
Maybe I have missed it, is there any method planned for using the AI to manage collections/tags? Example, If I had a method to say, "Collect all the objects relating to [subject] that are [object type]." and it would go through my objects looking for contexts that relate to my request and place them into a new collection. Maybe the same for tagging objects, "Tag all objects of any type that relate to [subject] with [tag name]."
conversely telling the AI to go through a tag or collection and remove things it thinks are unrelated.
1) "Collect all objects that are vehicles into a collection called "Cars".
2) "Go through my collection called "Cars" and remove everything that is a Truck leaving only sedans and crossovers
Log In
Steffen Bleher
complete
Tag and Collection AI are now released! You can read about it here: https://capacities.io/whats-new
J
Justin McDaniel
I think a good way of dealing with AI Collections is adding custom instructions for each collection, since each user is going to have collection names that may not be intuitive for an AI to understand semantically.
Steffen Bleher
in progress
Steffen Bleher
Merged in a post:
automatic custom tagging for types & collections
v
vision assemblies
normally putting something into a type / collection category comes with some automatic implication for the semantics / labeling of any object.
... so an option for auto-tagging specific tags to any object in types / collections is one if the ways to save people a lot if work... and improve systematicity.
(I noticed this idea / request from the forums was not put up here yet. so I did.)
M
Michael von Hohnhorst
Merged in a post:
AI Integration, Swipe, Table: A Feature To ORGANIZE Your Content
B
Blaze Lux
1.) AI integration: A useful feature for Capacities would be to integrate AI within the app. This feature would allow the app to automatically organize the notes based on the content, context, and user preferences.
Basic feature: The AI feature could be accessed by an AI button on the top right corner of the screen. When the user finishes writing their notes, they can press the button and the AI will analyze the notes and sort them into appropriate categories, folders, or tags. The AI will also suggest relevant keywords, summaries, and links for the notes. This could be a basic feature for all users, as it would save them time and effort in managing their notes.
Pro believers: For pro users, the AI feature could offer more customization and control. The pro users could give commands or feedback on how they want their notes to be organized. For example, they could specify the criteria, format, or style of the categories, folders, or tags. They could also edit or delete the suggestions made by the AI. This way, the app can match the user’s preferences and needs more closely, and provide a personalized note taking experience.
2.) AI tags: Another feature that would enhance Capacities as a note taking app is the AI tags. This feature would enable the app to automatically generate tags for each note, based on the main topics, concepts, or keywords of the note. The app would use natural language processing and machine learning to extract the most relevant and meaningful tags from the note. The app would then display the tags at the end of the note, or allow the user to edit or add their own tags. This feature would make it easier for the user to search, filter, or group their notes by tags.
3.) AI cover image selection: Another feature that would make Capacities more attractive and user-friendly is the AI cover image selection. This feature would enable the app to choose a suitable cover image for each note, based on the content and theme of the note. The app would use an image search engine to find relevant and high-quality images online. The app would then present four options for the user to choose from, or allow the user to upload their own image. The cover image would add a visual element to the note, and make it easier to identify and recall.
4.) Swipe gesture for going back: A final feature that would improve Capacities as a note taking app is the swipe gesture for going back. This feature would allow the user to navigate between notes and screens by swiping left or right on the touchpad or touchscreen. This feature would make the app more intuitive and convenient, as most people are used to swipe gestures on their devices. This feature would also reduce the time taken to switch between notes and screens, and enhance the user’s productivity and efficiency.
5.) Table creation option: A useful feature that would make Capacities more versatile and powerful as a note taking app is the table creation option. This feature would allow the user to create tables within their notes, and fill them with any data or information they want. The user could also format the tables, such as adjusting the size, color, alignment, or borders of the cells. The user could also insert formulas, charts, or images into the tables, to make them more dynamic and interactive. This feature would make note making more beautiful, easier, organized, and understandable, as the user could present and manipulate data or information in a clear and concise way.
These features would make Capacities stand out from other note taking apps. Capacities is already an aesthetic app, but these features would make it even better. They would provide a smart, flexible, and enjoyable note taking experience for the users.
Steffen Bleher
Merged in a post:
AI automated tagging / tagging-suggestions
S
Stefan Huber
AI supported and maybe automated tagging of content / tagging suggestions that the user can accept/deny
Steffen Bleher
planned
Steffen Bleher
Thanks for adding it. This can be achieved with templates. Do you agree? It would close it then.
v
vision assemblies
Steffen Bleher: thx for letting us know! I personally haven´t thought about it, mostly as I haven´t really got my head / habit into templating, yet.
I´d say, practically: yes, it´s there. So, no real need for the fundamental FR.
... there is, of course some 'extra steppin' '; but this extra click, while making it a little volatile in practice, actually also adds some benefits (easy to add different patterns according to context).
... the one tear it brings to me, if this is closed, is more of an associated fact / implication: the fact that it somehow says, there will be no drag and drop support for this (either for now; or out of conceptual reasons). this (drag and drop) is something I do / would really miss. one, for its convenience, and two, for (potential) bulk operations...
(– btw: is there a way to bulk apply templates...?)
... another drawback, if you think of auto-tagging for collections: depending on use patterns this will create a rather long tail of templates. which might bring some practical inconveniences, like clogging up the template footer section, making process slow and nitty gritty etc. – again, this is to be weighed against some of the flexibility templating also brings...
in the end, I think having two ways here (via templates and directly linked to types / collections would be best / preferrable.
but also thinking, this is very usable already, even carrying some drawbacks.
with those thoughts in mind, I will go with the progressive flow of things :-)
thx again!
PS, thx Steffen Bleher – you probably kickstarted my template career in Capacities! :-D