Peterhouse card api setup

Dear Team,

Following correspondences with Monty over the last few days and our embarrassing lateness to this piece, partly owing to lack of knowledge in this area, returning students workload and a very small team, I really feel we will need some assistance with this please.

As I mentioned to Monty, we have noticed that Student Mifare id’s have not been updating in the last few weeks and have finally put 2 and 2 together, apologies for that……

Would there by anyone that could help us with this? as we have very limited SQL/Python skills – this area is not well documented on our part.

In the meantime we have suppressed the current daily export and are manually making student changes, which is less than ideal (Fellows and staff are handled via our HR system)

Look forward to hearing soon

Much appreciated Will

assigned to @av603

made the issue confidential

changed milestone to %DevOps Sprint 134

made the issue visible to everyone

Hi Will,

I'm picking up this support request below. In the future (although it's not setup at the moment) these type of requests will go via the HEAT ticket system.

I presume you want to run a daily export of the cards associated with Peterhouse? If so, you can either use the card client: https://gitlab.developers.cam.ac.uk/uis/devops/iam/card-database/card-client or talk directly to the card-api.

If using the card client, you will find a config example that was prepared for Peterhouse (just add a valid API Gateway Key & Secret) https://gitlab.developers.cam.ac.uk/uis/devops/iam/card-database/card-client/-/blob/master/example-configuration/peterhouse.yml

Who will be performing the integration work on your end? and what's their preferred method? (API or card client or other) What's the current process?

Cheers Andrew

added workflowBlocked label

changed milestone to %DevOps Sprint 135

added teamIdentity label

Sorry didn't realise this was a duplicate.

added resolution Duplicate workflowDone labels and removed workflowBlocked label

closed