external reference ID in list model #2

New Issue

k2s · 2022-06-18T13:13:35Z

k2s commented

2022-06-18 13:13:35 +00:00

The list model contains identifier which is 10 characters long.
We need property, which will link the list item with person in Curo.
This property should support UUID lenght.

Would it be possible to change the API to support internal IDs, but also UUID?

The list model contains identifier which is 10 characters long. We need property, which will link the list item with person in Curo. This property should support UUID lenght. Would it be possible to change the API to support internal IDs, but also UUID?

k2s added this to the Curo integration project 2022-06-18 13:13:35 +00:00

k2s commented

2022-06-18 13:18:52 +00:00

Related to #3, the external ID could be list title to minimize duplication.

konrad commented

2022-06-18 17:42:15 +00:00

There's been an issue about switching to uuids: vikunja/api#772

But because of the complexity involved I don't think that's happening anytime soon. Right now I see three solutions to your problems:

Increase the list prefix so that it supports uuids - you could then put your uuid in there.
Put the UUID somewhere else, maybe in the description or title.
Add a reference to your person uuid from Curo in a fork of Vikunja.

Or maybe even easier, couldn't you just save the ID of the list with the person in Curo?

There's been an issue about switching to uuids: https://kolaente.dev/vikunja/api/issues/772 But because of the complexity involved I don't think that's happening anytime soon. Right now I see three solutions to your problems: 1. Increase the list prefix so that it supports uuids - you could then put your uuid in there. 2. Put the UUID somewhere else, maybe in the description or title. 3. Add a reference to your person uuid from Curo in a fork of Vikunja. Or maybe even easier, couldn't you just save the ID of the list with the person in Curo?

k2s commented

2022-06-18 18:40:31 +00:00

list prefix - @konrad you mean the list.identifier ? I don't see any prefix in https://try.vikunja.io/api/v1/docs#tag/list/paths/~1namespaces~1{namespaceID}~1lists/put
we need quick access/filter by this information, so this will not work
this seams to be the most generic solution

1. list prefix - @konrad you mean the `list.identifier` ? I don't see any `prefix` in https://try.vikunja.io/api/v1/docs#tag/list/paths/~1namespaces~1{namespaceID}~1lists/put 2. we need quick access/filter by this information, so this will not work 3. **this seams to be the most generic solution**

konrad commented

2022-06-18 19:08:13 +00:00

you mean the list.identifier?

Exactly, that's what I meant.

we need quick access/filter by this information, so this will not work

And if you could filter by identifier?

> you mean the list.identifier? Exactly, that's what I meant. > we need quick access/filter by this information, so this will not work And if you could filter by identifier?

k2s commented

2022-06-18 19:21:34 +00:00

Yes, if list.identifier identifier would accept up to 23 distinct octets in ASCII or 32 characters which is UUID lenght it would help.

But I would need to extend the GET /lists/{id} to work also as GET /lists/{uuid}. Would that be ok?

For now I see as the best way to store Vikunja list ID in Curo.

Yes, if `list.identifier` identifier would accept up to `23 distinct octets in ASCII` or 32 characters which is UUID lenght it would help. But I would need to extend the `GET /lists/{id}` to work also as `GET /lists/{uuid}`. **Would that be ok?** **For now I see as the best way to store Vikunja list ID in Curo.**

👍 1

konrad commented

2022-06-18 19:23:19 +00:00

But I would need to extend the GET /lists/{id} to work also as GET /lists/{uuid}. Would that be ok?

Not sure if the endpoint would be that but that should be fine to implement.

> But I would need to extend the GET /lists/{id} to work also as GET /lists/{uuid}. Would that be ok? Not sure if the endpoint would be that but that should be fine to implement.

Sign in to join this conversation.

No Label

API

UI

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: k2s/populate-vikunja#2