4/16 Minutes
jos...@gmail.com
https://docs.google.com/document/d/1lGMSIwlxAoq42kGMkGeJicOHxwEuDmKbiMOhW4pW50c/edit?usp=sharing
OSDI Weekly Minutes
Meeting time: Wednesdays, 10am Pacific, 1pm Eastern
1.2 Closeted OSDI Participation 2
2.1 UPDATE on Discovering Available Custom Fields 2
2.2 APPROVED Update: Cost efficient mappings to underlying APIs #325 2
2.5 DISCUSSION Batch Import Helper #335 3
3.2 Sandbox Updates - API call, object change audit logs 3
1 Logistics
1.1 Meeting Information
Meeting time: Wednesdays, 10am Pacific, 1pm Eastern,
1.2 Closeted OSDI Participation
If you are interested in providing technical feedback and wish to do so privately, in the closet, you can contact me at the OSDI Closet Hotline (516) 701 1900. You feedback will be related anonymously and your identity will only be known by me.
2 Tech Work
2.1 UPDATE on Discovering Available Custom Fields
On some systems, the custom fields hash object allows any field to be inserted/created. On other systems, the custom fields must be explicitly created. Tags have a similar aspect where on some systems you can create a tag by tagging someone, on others you must know the tags in advance. We have a way to enumerate tags, but we dont have a way to enumerate custom fields.
See full discussion from previous meeting here:
I’ve been prototyping this for VAN, OSDI sandbox, VolunteerHub, Salesforce, Salsa Engage. I’ll discuss results
Next Steps: make PR for metadata endpoint approach
2.2 APPROVED Update: Cost efficient mappings to underlying APIs #325
https://github.com/opensupporter/osdi-docs/issues/325
One clarification that is worthy of discussion is a reminder to add other links to the response. Eg, if we're returning the "self" link, we should also include related resources like "osdi:attendances" or "osdi:donations" Even though the client may not be interested in the actual representation, it may wish to navigate to other collections.
Updated Pull request here: https://github.com/opensupporter/osdi-docs/pull/334
MOTION to approve
Approved
2.5 DISCUSSION Batch Import Helper #335
https://github.com/opensupporter/osdi-docs/pull/335
“Based on the need of apps like Spoke or CRMs to have people imported in batches vs single API call per person, this is a proposal for a new helper osdi:people_import_helper. It's been prototyped as a Spoke contacts API.”
Discussion reviewing prototype implementation for Spoke
TODO
- Add “duplicates” to response object
- Clarify that duplicates exist within the input batch
3 Outreach
3.1 Ecosystem Updates
3.2 Sandbox Updates - API call, object change audit logs
Here is an example of the sandbox audit history in the UI after an OSDI person signup helper is invoked, which matches and updates an existing person as well as a tagging.
5 Leadership
When recruiting, also include the ask for leadership candidates with these goals:
https://docs.google.com/document/d/1_ARqsa1hxhADJc4f4eFAUt9JxZGgBGbeangtd8mcfEk/edit?usp=sharing
6 Adjourn
--- Connection reset by queer Gender Pronouns: Gay/Non/Normative
Josh Cohen, EMT jos...@gmail.com | @joshco | LinkedIn | GitHub | OSDI | Hit me up to AutoSync your new Salesforce data to VAN and apply Activist Codes nightly