diff --git a/perydAffilFwork.adoc b/perydAffilFwork.adoc index 3e62ce2..9c25b47 100644 --- a/perydAffilFwork.adoc +++ b/perydAffilFwork.adoc @@ -21,9 +21,9 @@ The departments in blue. We have different applications as well, like slate and Our CS instance is our um authoritative data source. So it it sends everything to uh employee.Smu. And also our setup data is authoritative in an employee Dot Smu, and syncs over to our campus solutions. Instance. From there also you can see that we do have some external affiliation sources that we manage. So in in these two boxes we have our employees and students, and we do have some sponsored identities that we select here based on um instructor data. So when we don't have the authoritative, you know job data to tell us this is an adjunct. We use the um schedule of classes and the instructor visor table to figure out who's teaching, and then we go ahead and give them a sponsorship that we call instructor-sponsored access. -we have other sponsorships down here represented that go into this box here, which is our current custom, identity management type uh Bolton that we created in peoplesoft and campus solutions which i'll talk more about. But then the end result is that we have our service provisioning, and even just physical access uh kind of directed by the logic that is running here in this engine. +we have other sponsorships down here represented that go into this box here, which is our current custom, identity management type uh bolt-on that we created in peoplesoft and campus solutions which i'll talk more about. But then the end result is that we have our service provisioning, and even just physical access uh kind of directed by the logic that is running here in this engine. -So for our current state. we have people soft as our person registry. We have this custom uh account maintenance automation, Ama Bolton that determines the person, affiliation and service eligibility. And then we have Tommy's power shell script, or maybe more than one script that actually performs the service provisioning, +So for our current state. we have people soft as our person registry. We have this custom uh account maintenance automation, Ama bolt-on that determines the person, affiliation and service eligibility. And then we have Tommy's power shell script, or maybe more than one script that actually performs the service provisioning, What we did with our affiliation. Framework. Um project is sort of just replace a piece of what Ama does, Which is this right here assigning what we call user types, and you will hear um me interchangeably use the term user type and affiliation. Um, throughout. @@ -44,39 +44,11 @@ And then we already talked about the little icon. So it is part of the constitue I don't remember when it was, but it was a while back we tried to implement affiliation framework and had a lot of hurdles. So we ended up just so that we could meet this need delivering. I just created like a sql script that the Dba's had on a cron job that would run every night to identify current employees, former employees, current students, and former students, so that when new apps came into the system it would check and see, because they did not want those applications to update any bio demo data for existing current employees, for example, or existing current students and things like that. So that's where that comes in currently. We've gone live with affiliation framework like two weeks ago when it went Live any discrepancies, you know, do doing, reporting. We can um use it to continue our co-manage integration efforts and things like that. But I thought it would be interesting to show you guys, some of the counts that we have with our current um affiliations. And I, broke out the instructor, one, because that one is not dependent on job data, obviously right. So So the ones that have, for example, adjunct faculty. There's three hundred and thirty-eight -but as you can see here, Um, we have e instructor assigned to six hundred and sixty-eight that are set up as instructor type adjunct in the instructor visor table, and that is because we do have an issue with getting those higher forms in a timely fashion and things like that. So the instructor. Affiliation code is intended to be sort of a high level. We don't want to say that you are an adjunct, because you can be a teaching assistant, or a Gsi, or graduate student structure, full time, faculty, or whatever. And currently, unfortunately, in our peoplesoft system. These instructor types are not maintained, So there's not a high degree of confidence, and using those as our as our source to say, Yes, you are now assigned right. We know of instances where, for example, we have full time faculty that come in, +but as you can see here, Um, we have e instructor assigned to six hundred and sixty-eight that are set up as instructor type adjunct in the instructor visor table, and that is because we do have an issue with getting those higher forms in a timely fashion and things like that. So the instructor. Affiliation code is intended to be sort of a high level. We don't want to say that you are an adjunct, because you can be a teaching assistant, or a Gsi, or graduate student structure, full time, faculty, or whatever. And currently, unfortunately, in our peoplesoft system. These instructor types are not maintained, So there's not a high degree of confidence, and using those as our as our source to say, Yes, you are now assigned right. We know of instances where, for example, we have full time faculty that come in, so they're in this table as full time faculty. They retire. They come back as adjuncts, and nobody updates their role to adjunct again. So we're moving in other projects to try to improve that data quality, and we have made a lot of progress in trying to sync it up with what job data says and things like that. But we're still not at one hundred percent confidence in those designations. But we're moving in the right direction, I feel, and I think and hope that by the time we're ready to go live with our new Im solution that things will be a lot more timely and accurate in our in our data. -244 -00:32:12.110 --> 00:32:29.800 -Pery Doan: so they're in this table as full time faculty. They retire. They come back as adjuncts, and nobody updates their role to adjunct again. So we're moving in other projects to try to improve that data quality, and we have made a lot of progress in trying to sync it up with what job data says and things like that. But we're still not at one hundred percent confidence +So how does the delivered Affiliation Framework process works. A lot of what you're gonna see are things that I took from the Campus Solutions Affiliation Developer Guide. I just copied this high level diagram of how it works where you have constituent information that's changing the system. For example, Admissions matriculates a student or HR terminates an employee, that's a change; or some self service utility that a student uses to change their address. -246 -00:32:38.840 --> 00:32:52.109 -Pery Doan: in those designations. But we're moving in the right direction, I feel, and I think and hope that by the time we're ready to go live with our new Im solution that things will be a lot more timely and accurate in our in our data. - -247 -00:32:54.630 --> 00:32:58.900 -Pery Doan: So the way that the delivered Affiliation Framework - -248 -00:32:59.430 --> 00:33:01.160 -Pery Doan: process works. - -249 -00:33:01.360 --> 00:33:07.640 -Pery Doan: Um. This I took from a lot of what you're gonna see are things that I took from - -250 -00:33:07.700 --> 00:33:27.500 -Pery Doan: the campus solutions, affiliation, developer, guide. So they have this high level diagram of how it works and it's. I just copied it exactly where you have constituent information that's changing the system, like say, for example, um. Some the admissions matriculates. A student or - -251 -00:33:27.520 --> 00:33:36.259 -Pery Doan: hr terminates an employee that's a change, or you know some self service change that the user does to change their address something like that. - -252 -00:33:37.160 --> 00:33:41.640 -Pery Doan: Then you have integration, broker messages that are published. And +Then you have Integration Broker messages that are published. And 253 00:33:42.740 --> 00:33:55.369