Record the source of memos created via access tokens

[binjoo]

Pre-submission Checklist

• I have searched existing issues and confirmed this feature has not been requested
• This is a feature request, not a bug report or question

Feature Area

Integrations / Plugins

Problem or Use Case

Memos supports access tokens, which makes it possible to create memos through the API. However, when multiple access tokens are in use, it becomes hard to tell which token was used to create a specific memo.

It would be helpful if Memos could record the name of the access token used when a memo is created. This would make it easier to identify the source of each memo.

Proposed Solution

For example, if I create an access token named telegram, then any memo created with that token could be marked or recorded as coming from telegram.

Alternatives Considered

No response

Additional Context

Contribution

• I'm willing to submit a pull request for this feature

[mateenbagheri]

Hello there. I'm interested in working on this issue if it is available.

I'm new to the Memos codebase and this would be my first contribution to the project. It might take me a tad bit longer than usual as I get familiar with the code structure, setup, and contribution workflow.

If that's okay with you, I'd love to give it a try. I'll make sure to ask questions along the way if I get stuck.

[mateenbagheri]

Oh and btw, before I start, would it be possible to get a quick breakdown of the main files or areas I should look at for this change? Just to help me scope things out.
Few other questions:

• Will this information be shown to user only when the note is opened in detail or in the main scrolling page too?
• Will the user be able to toggle on and off this feature? If yes more information on how this is done would be much appreciated

[kylege]

You can achieve this functionality by including a specific tag when creating a memo. For example, when creating a Telegram token request memo, you can include the #telegram tag.

[mateenbagheri]

I am sorry Im a bit confused. Do you mean this functionality is already implemented through using tags or you want the implementation leverage tags in order to achieve its goal? @kylege

[kylege]

I am sorry Im a bit confused. Do you mean this functionality is already implemented through using tags or you want the implementation leverage tags in order to achieve its goal? @kylege

By leveraging existing functionality, users holding tokens who create memos via the API can simply include the corresponding tag when creating their memos.

[binjoo]

You can achieve this functionality by including a specific tag when creating a memo. For example, when creating a Telegram token request memo, you can include the #telegram tag.

This is one way, but if we forget to do it, we’ll have to edit the memo again.

Would it be better if each submission could automatically include labels or have a separate “source” field?

[kylege]

You can achieve this functionality by including a specific tag when creating a memo. For example, when creating a Telegram token request memo, you can include the #telegram tag.

This is one way, but if we forget to do it, we’ll have to edit the memo again.

Would it be better if each submission could automatically include labels or have a separate “source” field?

I don't think this should be the system's responsibility.

[mateenbagheri]

Thanks for the discussion @kylege and @binjoo .
Considering that:

• Tags can already be added manually to memos
• This can be done through API too
• It is preffered that avoiding automatic metadata injection is decided

I'll leave it to @binjoo to decide if this issue should stay open or be closed. Happy to help either way.

[ztm0929]

but if we forget to do it, we’ll have to edit the memo again.

@binjoo We can add tags automatically by appending them to the end of the content.

For example, in a specific scenario: I type the content I want to record in Telegram bot chat, the API receives the message, and the program appends a separator line (---) along with the text This memo comes from #telegram at the end of the content (which means we don’t have to manually add such source attribution).

This is just an example. The actual implementation is up to you. As for creating a dedicated source field as a property for the memo, I don’t have a strong opinion. However, from a system design and development perspective, I think it could be a relatively heavy task.

https://usememos.com/docs/api/memoservice/CreateMemo

[binjoo]

Thanks for the suggestions, @kylege, @mateenbagheri, and @ztm0929. I understand your points and have indeed tried that approach.

For instance, when I set up an integration like telegram-integration to send messages via Telegram, I currently have to manually append telegram to the message each time. This becomes quite tedious and error-prone, especially with frequent use.

It would be significantly more efficient if the system could automatically persist/store the token's name within the payload field of the memo database table.

The key point here is that this token name isn't part of the memo's content itself, but rather an additional attribute or metadata associated with that memo.