Archiving Members

[kylegregory]

vis #25 @MilSix

Hi Kyle,
Quick questions for you about Emma api :

Is there an emma api calls for bulk “archive” subaccount/group/ of members

I only see there are 3 member statuses: “active”, “error”, or “optout” . Is there a way to set a member to “Inactive” ?

Terminology here is very complicated, so let me see if I can help. An 'archived' member is one which has been also been 'deleted.' That endpoint is DeleteMember or to delete multiple use DeleteMembers.

My understanding before GDPR was that 'deleting' via the API or 'archiving' through the front-end just adds a date to the deleted_at parameter. You might find help in the Resource Center especially as it pertains to users signing up again if they are 'archived.' This is probably a bit more complicated/changed after GDPR.

Now as far as making a user account 'inactive' that's an entirely other issue. Sounds like you want to move them into Error, where they won't receive any mailing, but information on that contact can be kept current. Then at some point in the future, you can move them back to Active if needed.

Reach out if you have other questions.
Kyle

[kylegregory]

@MilSix

Just received clarification from Emma on the Delete endpoints in Member. DeleteMember and DeleteMembers are "hard deletes" that remove the account and all history.

Checking on the existence of an "archive" or "soft delete" via the API, similar to the front-end.

Kyle

[MilSix]

Hi Kyle, I’ve just tested for one emailAddress, 1.I called GetMemberByEmai(emailAddress) to retrieve memberID 2. then passing memberID into the call DeleteMember(memberID) 3. Log in to emma and verified that I can find the email that I just deleted got save to archived Items under ‘contacts’ with (‘active’ status) So it is archived or soft Delete like front end and I still have option to either ‘Restore’ or ‘Delete’ from here Is there an equivalent ‘Restore’/’Delete’ api call from Arichived Items ? [cid:[email protected]] From: Kyle Gregory [mailto:[email protected]] Sent: Friday, June 8, 2018 11:11 AM To: kylegregory/EmmaSharp <[email protected]> Cc: Mydieu Nguyen <[email protected]>; Mention <[email protected]> Subject: Re: [kylegregory/EmmaSharp] Archiving Members (#36) @MilSix<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMilSix&data=01%7C01%7Cmnguyen%40foundation.fsu.edu%7Cd690f64b6b8c40f22efe08d5cd52163b%7C92acbb4de6d24e85a77671e615222e90%7C0&sdata=6SvBwSAbjWlnV1ARa8pEoRD12ArPWnk0u9vCE8xx4to%3D&reserved=0> Just received clarification from Emma on the Delete endpoints in Member. DeleteMember<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapi.myemma.com%2Fapi%2Fexternal%2Fmembers.html%23delete--%23account_id-members-%23member_id&data=01%7C01%7Cmnguyen%40foundation.fsu.edu%7Cd690f64b6b8c40f22efe08d5cd52163b%7C92acbb4de6d24e85a77671e615222e90%7C0&sdata=c3gwgcsS9LY5ncf5bi1bIDdv4XtrBnnHZ%2FYfWC2Wj%2FA%3D&reserved=0> and DeleteMembers<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapi.myemma.com%2Fapi%2Fexternal%2Fmembers.html%23put--%23account_id-members-delete&data=01%7C01%7Cmnguyen%40foundation.fsu.edu%7Cd690f64b6b8c40f22efe08d5cd52163b%7C92acbb4de6d24e85a77671e615222e90%7C0&sdata=3qVnIK2Nr%2FhmiR%2B7DJUr0WC2j9%2BW1vVNfoSRFDJvTog%3D&reserved=0> are "hard deletes" that remove the account and all history. Checking on the existence of an "archive" or "soft delete" via the API, similar to the front-end. Kyle — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkylegregory%2FEmmaSharp%2Fissues%2F36%23issuecomment-395791731&data=01%7C01%7Cmnguyen%40foundation.fsu.edu%7Cd690f64b6b8c40f22efe08d5cd52163b%7C92acbb4de6d24e85a77671e615222e90%7C0&sdata=Qz93SAbbPNtxm87jPnK0QAOTTqWPiZXB4ZCJSIsnAFM%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfgqvY-W6RHZ4Pr6eDPVaMlaXjEoBc3jks5t6pQVgaJpZM4Ubv6t&data=01%7C01%7Cmnguyen%40foundation.fsu.edu%7Cd690f64b6b8c40f22efe08d5cd52163b%7C92acbb4de6d24e85a77671e615222e90%7C0&sdata=Ymr%2FX6fOsx0JddKMeqTG1eLdlCJ7cfmUj0ieSj2TrzY%3D&reserved=0>.

[MilSix]

Hello Kyle, Just an FYI. I found from community question that con your 1st replied on this question. https://community.myemma.com/emma/topics/delete-member-does-not-delete So after I’ve archived record I was able to ‘restore’ the same record by calling post members api action again, the email showed up to the correct group. [cid:[email protected]] [cid:[email protected]] From: Mydieu Nguyen Sent: Wednesday, June 13, 2018 6:03 PM To: 'kylegregory/EmmaSharp' <[email protected]>; kylegregory/EmmaSharp <[email protected]> Cc: Mention <[email protected]> Subject: RE: [kylegregory/EmmaSharp] Archiving Members (#36) Hi Kyle, I’ve just tested for one emailAddress, 1.I called GetMemberByEmai(emailAddress) to retrieve memberID 2. then passing memberID into the call DeleteMember(memberID) 3. Log in to emma and verified that I can find the email that I just deleted got save to archived Items under ‘contacts’ with (‘active’ status) So it is archived or soft Delete like front end and I still have option to either ‘Restore’ or ‘Delete’ from here Is there an equivalent ‘Restore’/’Delete’ api call from Arichived Items ? [cid:[email protected]] From: Kyle Gregory [mailto:[email protected]] Sent: Friday, June 8, 2018 11:11 AM To: kylegregory/EmmaSharp <[email protected]<mailto:[email protected]>> Cc: Mydieu Nguyen <[email protected]<mailto:[email protected]>>; Mention <[email protected]<mailto:[email protected]>> Subject: Re: [kylegregory/EmmaSharp] Archiving Members (#36) @MilSix<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMilSix&data=01%7C01%7Cmnguyen%40foundation.fsu.edu%7Cd690f64b6b8c40f22efe08d5cd52163b%7C92acbb4de6d24e85a77671e615222e90%7C0&sdata=6SvBwSAbjWlnV1ARa8pEoRD12ArPWnk0u9vCE8xx4to%3D&reserved=0> Just received clarification from Emma on the Delete endpoints in Member. DeleteMember<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapi.myemma.com%2Fapi%2Fexternal%2Fmembers.html%23delete--%23account_id-members-%23member_id&data=01%7C01%7Cmnguyen%40foundation.fsu.edu%7Cd690f64b6b8c40f22efe08d5cd52163b%7C92acbb4de6d24e85a77671e615222e90%7C0&sdata=c3gwgcsS9LY5ncf5bi1bIDdv4XtrBnnHZ%2FYfWC2Wj%2FA%3D&reserved=0> and DeleteMembers<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapi.myemma.com%2Fapi%2Fexternal%2Fmembers.html%23put--%23account_id-members-delete&data=01%7C01%7Cmnguyen%40foundation.fsu.edu%7Cd690f64b6b8c40f22efe08d5cd52163b%7C92acbb4de6d24e85a77671e615222e90%7C0&sdata=3qVnIK2Nr%2FhmiR%2B7DJUr0WC2j9%2BW1vVNfoSRFDJvTog%3D&reserved=0> are "hard deletes" that remove the account and all history. Checking on the existence of an "archive" or "soft delete" via the API, similar to the front-end. Kyle — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkylegregory%2FEmmaSharp%2Fissues%2F36%23issuecomment-395791731&data=01%7C01%7Cmnguyen%40foundation.fsu.edu%7Cd690f64b6b8c40f22efe08d5cd52163b%7C92acbb4de6d24e85a77671e615222e90%7C0&sdata=Qz93SAbbPNtxm87jPnK0QAOTTqWPiZXB4ZCJSIsnAFM%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAfgqvY-W6RHZ4Pr6eDPVaMlaXjEoBc3jks5t6pQVgaJpZM4Ubv6t&data=01%7C01%7Cmnguyen%40foundation.fsu.edu%7Cd690f64b6b8c40f22efe08d5cd52163b%7C92acbb4de6d24e85a77671e615222e90%7C0&sdata=Ymr%2FX6fOsx0JddKMeqTG1eLdlCJ7cfmUj0ieSj2TrzY%3D&reserved=0>.