Google Keep: unnecessary alias

[obsidianmd]

Google Keep: unnecessary alias

[lishid]

Ok so it makes sense to alias to line one and line two, which is the current behavior.

[daledesilva]

Agree with all of this. That was my thinking when I did it.

To reiterate

• Notes can often just be a title.
• The obsidian note name is just what keep exported as filename so it's already sanitised.
• Because the original title can have any character or even line breaks, the filename can be different, so the original title is added as an alias.
• To prevent multi line aliases, new line chars are replaced with spaces.

Note, on the original ticket question...
I considered checking whether the title matched the filename and only adding the alias if different, but I decided to just keep it simple and consistent for every note. Which could definitely be reconsidered if necessary.

[lishid]

@daledesilva I am not sure I understand the purpose of using keepJson.title.split('\n') for aliases. Can notes have multiple titles?

[NomarCub]

Notes can have titles that are more than one line long, but I only noticed that accidentally.
The data then looks like this: "title": "line one\nline two",. It can even have trailing newlines.

[lishid]

For "line one\nline two", what does the filename become?

[NomarCub]

With 1.1.0, it's line one_line two
The alias becomes line one line two

[lishid]

Hmm ok, so we should probably ignore the title field altogether? What do you think @daledesilva?

[NomarCub]

Definitely don't ignore the title, at least for file names. Notes can even be only a title. I don't think many people use multi line titles, you'd have to know and press shit enter, or a normal enter would take you to the note content when you input it. (Or you can just copy text there that has more lines.)
I think it's fine as is, collapsing multi line titles with a single space, and keeping the file name with underscores.

[lishid]

The file name is created from what Keep exports as file names in the zip. If it's always some combination of flattened "title" field then it would make sense to ignore.

[NomarCub]

I think that's what it is, yes, and if there's no title, it's the date instead. But I would not ignore it, unless you have some better mechanism for creating a file name or title. It makes a lot of sense to me, to have the OS friendly file name, and if it differs from the original, have an alias field with the original title with special characters if there were any.