Here’s a short question about dataview, from someone who’s still a very basic beginner.
after receiving some advices from a previous question, I started use the following “entry” (syntax ?) when it comes to book / article authors : (author::NAME, Surname)
So I was wondering if there’s a way to automatically suggest a list containing the author’s name that I already typed in my other notes.
for example → (author::H and as soon as the “H” is typed, a list with auhtor’s name starting by the letter H would appear.
I also noticed that when I type a double “::” it will sometimes suggest me things (like when I’m doing this here, it suggests me emojis faces) but I don’t really understand how such amechanism works and how I can eventually set it by myself.
I recommend browsing the forum, especially the Share and Showcase section and posts about Books, frontmatter (properties), templates, etc.
If you are to add an author property key, any former value set for the author property will be offered via the Properties core plugin.
Both Properties and Templater (a more feature rich 3rd party version of Templates core plugin) can be enhanced by the Modal forms external plugin (it has some learning curve as all things in Obsidian), which Modal forms plugin can be used with Dataview queries so tags and any property values previously added by Obsidian to the metadatacache can be picked up for selection.
In some cases or for particular vaults, Modal forms will be great for data entry, other times, not needed.
All elaborate workflows need exploring, some tinkering, but as Hampton’s example shows, you can get started on basic out-of-the-box features as well.
Suggesting Author Names Based on Input
To achieve the functionality where typing an author’s initial (e.g., “H”) automatically suggests names you’ve already entered, you typically need a system that supports:
Auto-Completion: This is often built into the note-taking app. When you type a prefix (like “H”), the app should automatically suggest entries that match.
Tagging or Linking: Ensure that you’re consistently formatting your author entries in a way that the system recognizes them as tags or links.
Example Workflow:
When you enter an author, format it as author::John, Doe in your notes.
As you type author::H, the app should ideally suggest existing entries like author::Hannah, Smith or author::Henry, Adams.
How to Set Up Suggestions
Check Documentation: Most note-taking apps have specific guidelines on how to enable auto-complete features. Look for sections on tagging, linking, or creating templates.
Use Plugins: If the app allows, consider using plugins that enhance functionality. For example, in Obsidian, there are plugins for managing metadata that can improve how authors and other entities are handled.
Consistent Entry: Make sure that you consistently use the same syntax (author::), as variations can affect how suggestions are generated.
Understanding Double “::” and Suggestions
The double colon (: syntax often indicates a property or metadata field in many note-taking applications. When you type a double colon:
The application may scan your notes for matching entries, tags, or emojis that you’ve used previously.
This behavior can usually be customized within the app’s settings. Look for features related to snippets, templates, or auto-complete settings.
Setting Up Your System
Consistent Naming: Use a standard format for entering authors and other entities.
Check Settings: Explore the settings or preferences of your note-taking app for options related to auto-completion or suggestions.
Use Templates: Some apps allow you to create templates for repeated entries, which could help maintain consistency and facilitate suggestions.
syntax often indicates a property or metadata field in many note-taking applications. When you type a double colon: