firstdotorg / global-irt Goto Github PK

Other fields like phone-numbers and enckeys already are lists. Making the email field an "emails" list field would be a good idea as there might be more than one email per organisation (and therefore a reason for multiple enckeys). You could store multiple emails comma separated but then a client has to parse this list if he wants to know which encryption key is used for a specific email address, etc.

I found it hard to have spaces in IRT team types.

e.g. "as a service"

We could use
"aaS" or "as_a_service"

Opinions?

the enckeys property only returns the encryption keys in short id format, e.g. 0xBADCOFFE
As collisions in the short id space are nowadays very easily done the preferred key format should be long id e.g. 0xDEADBEEFBADCOFFE

HI,
i will install this application global-irt. please share me the steps.
thank you

The wiki deviates from the definition found in api.md.
In the wiki operating-hours is defined as as a dict of dicts (day -> {from, to}) and api.md says it is an string type. At the moment the api,first.org is using untyped string type. For better support in tools to show availability it would be good if operating hours are saved in a structured way.

Also including timezone information to these operating hours to be useful.

Closed and deleted old repo as requested by @shrekts