Thanks Ryan ... here's some scribbling of some thoughts around this.
If you've been working this I'd suggest there's nothing new, but the primary use case below is why I asked this question ... Regards, Dave
Conceptually I see this is analogous to /logbook/ (1:M with member, typed) with the history as another child
Useful: get a list of valid credential types (like the existing '/logbooks/types/')
Only 1 concrete use case right now
- given a member/person, GET their credentials so we can see if they have a specific (active) credential
- essentially just want to be able to ask for the data we see in the UI
--> Member ID, Credential Type (ID assumed), Status, Quantity(?), Issued Date, Expires Date
- useful if we could restrict credentials to 'active' ones [?credentialstatus=active] OR [/activecredentials/]
- useful if we could restrict credentials to a specific type(s) [?credentialtype=x,y]
- seeing the credential History ('logs' in UI) for a credential would be useful [?history=true]
- useful if credential list was available (as an option?) in the response from GET /members/{ID}/
Other potential usage
- issue or update (POST/PUT) a credential (via automation from another app)
- for POST/PUT we would expect that MSR would maintain the integrity of the 'History' info
JSON only