improve UX for template management #10

Open
opened 2025-02-20 15:22:57 +00:00 by pedro · 1 comment
Owner

on templates, operations add/remove are really enable/disable

the way to add templates is not explained in the same application and it might be confusing for new users

on templates, operations add/remove are really enable/disable the way to add templates is not explained in the same application and it might be confusing for new users
pedro changed title from template management to improve UX for template management 2025-02-20 15:23:07 +00:00
Owner

Adding new credentials to idHub is described in the help. Now it requires to add:

  1. Context to ./context folder
  2. Schema to ./schemas folder
  3. Template to ./idhub/templates/credentials folder. The credential template has placeholders for each possible value.
  4. Spreadsheet (check ./examples/excel_examples folder) can be generated with [this archived repository] (https://farga.pangea.org/trustchain-oc1-orchestral/schemas/src/branch/master/tools).

Given that contexts and schemas are typically accessible with a URL, these may not need to be included as local files but retrieved from their URLs.
For (3) and (4), they could be generated automatically. We have that for (4), and I think (3) is doable, starting from a generic VC and adding placeholders for credentialSubject elements.

As a result, adding support to a new VC would only require entering two external URL (Context, Schema).

What do you think @cayop @pedro @felixfreitag ?

Adding new credentials to idHub is described [in the help](https://idhub.pangea.org/help/en/community/). Now it requires to add: 1. Context to ./context folder 2. Schema to ./schemas folder 3. Template to ./idhub/templates/credentials folder. The credential template has placeholders for each possible value. 4. Spreadsheet (check ./examples/excel_examples folder) can be generated with [this archived repository] (https://farga.pangea.org/trustchain-oc1-orchestral/schemas/src/branch/master/tools). Given that contexts and schemas are typically accessible with a URL, these may not need to be included as local files but retrieved from their URLs. For (3) and (4), they could be generated automatically. We have that for (4), and I think (3) is doable, starting from a generic VC and adding placeholders for credentialSubject elements. As a result, adding support to a new VC would only require entering two external URL (Context, Schema). What do you think @cayop @pedro @felixfreitag ?
Sign in to join this conversation.
No labels
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: ereuse/IdHub#10
No description provided.