Research: An Overview

Good everyone joining in welcome. Welcome on this Tuesday.

How are things going where you are here in Connecticut? Can I? It is a cloudy, rainy drizzly day here.

But it's not.

But it's not freezing cold, it's 40 degrees.

Sport that is true. I am so thankful that snow is melting.

Cool.

As everyone joins, if you want to give a quick shout out in the chat, just sort of introduce yourself and get a sense of who's here. Maybe where you're dialing in from.

Who we are. Where you're from. What's the weather like? Hopefully those folks in the middle of the country, in the Southwest or Midwest have.

Survive the rolling blackouts and the ice and the snow and the craziness that was last week.

Yeah.

Health people from all over with New Orleans, Kansas, Illinois, Chapel Hill, New York, Great.

Stilwater

Mississippi.

Sick.

OSU on the upper 60s. Raymond, that's cool. I'll take that.

Who upper 60s sounds very nice right now.

Does does.

Creams for marriage be down in Houston. John Michael great oh 70s wow.

But

70 Mississippi to.

I'm pining for odear.

That's great.

Amanda, UNC.

Huh?

Well, cool, well we can be jealous for the next hour of the.

Search

Of all the nice weather that you all are having and glad to hear the folks from the middle of the country are like yeah survive survive that was that was pretty crazy times. At least that's what I saw on the news and on social media so.

crane there we go cool. Hey Bobby, thanks for the shout out.

Jason, wonderful.

Cool, we can do you feel you want to go ahead and get started when you give folks a few minutes?

Yeah, let's rock and roll. We've been. I think we got everybody got a couple of minutes here we can get going. Hey Jessica from Trancy hope all is well in Lexington.

Grant, yeah.

Yeah, let's rock and roll.

Let's dive in. So today we are talking about research, new bit of functionality that has now rolled out. So we're going to give just an overview of what it is today where our thoughts are on how it can be used, leveraged in your different databases. We have a couple of use cases to walk through and then of course we have other things to talk about in terms of other ways of using it. If you have external integrating partners, things like that, but we're just going to have a very high level overview today.

And of course be available to answer your questions. If you have any follow UPS or one specifics, post this web and are either in a focused call. We also have documentation about this out so really having this be the start of the conversation. So let's go ahead and let's dive in today what we're going to talk about. We're going to define what research is from our perspective. The tool that exists in slate that we're calling a research, we're going to find what research sources are and how those connect to what we're calling data keys. So a bit of new terminology.

Yeah.

That were dropping on you in terms of sleep speaks. It will define what those are as we get to it. Then we also walk through. Sort of how this information gets added to records. You know how we associate things like materials to it or querying or having dashboards for research or permissions that go along with it. So we'll talk about all those various elements and more. And I think if you have questions throughout, feel free to throw him in the chat. Ken and I are keeping an eye on that so will either answer them.

In real time, or will perhaps wait till the end to answer some questions there too so.

Yeah, and Jack from Walla Walla. Just a couple of housekeeping things. Yeah we are recording this and we'll make it available to everybody and anybody in the knowledge base. Eventually over the next couple days. Maybe later this week. Once it gets recorded. If you want to turn on Closed caption It, you've got a couple options in the upper right hand corner of the screen. If you want to hit full screen that will pop up into full screen and door closed captioning is available to so just.

Yeah.

You know, getting used to the share web and our platform. If you need any of those resources.

And if anytime something is out of sync, like the voice or the video, just do a refresh in your browser. Everything will sync back up again.

Yep.

Cool, So what is research were throwing out a definition? We're saying it's a very standardized way of storing point in time contextual and qualitative information about a record, right? So what does that actually mean? Well, it can mean really a number of things that could mean that this research is something like a well screaming where you actually going in screening records and storing the return data in a very standardized way that's accurate about that record at that point in time that it was screened.

Or maybe it's something that is really just something that your staff does its research that they're doing. They're digging through their finding news articles. They're finding you know historical information about your records, and they're adding it to it. It's stuff that perhaps the the record of the person or the student may not even know themselves, but you're adding this contextual information to their record. It doesn't have to exist on just people, and just on students, it could go across your datasets. So as you're storing information.

That you found out about it, and perhaps a company or maybe a school. It's storing that type of information on those records as well, and then can you know for your folks as well this sort of early alerts or doing some scoring actually on the student records? So it's a broad definition of what researches and can have these various ways that you're adding this research to a record an what that actually looks like.

Anything to add to that camp?

Yeah, no. We we. We wanted to kind of talk about this with you all. First. This has very very practical use cases. Kind of kind of no matter where you are. What you you sleep for, right? We had posted in the advancement and student success kind of forms. You know these kind of cohorts to talk with you guys about it first. But it is most certainly applicable in admissions or whatever the use case for for us, late or inside of Slate is whatever those processes are.

Still.

There's there's absolutely use case for it, so it's not. You know it's not exclusively for advancement or student success. Admissions is still included with a lot of use cases.

So I thought perhaps one of the best ways to sort of know what we're talking about here, right when there is sort of a new feature functionality is to actually just dive in, show a few examples as it exists on various records that we have just sort of showing what it looks like. Starting from that perspective, and then diving back to talk a little bit more functionality. How are the pieces actually put together from a more technical perspective? So let's actually dive over into Slate.

And we will take a look at what this looks like. So here we are wearing our advancement showcase environment will just go take a look at Alexander Hamilton's record and we'll notice that there's now a new standard tab called Research.

Click on to this tab, we get something that's just a very dashboard esque. It's an overview that just describes where these sources of information are coming from, how many of them are there? They verified unverified the dates. Things like that. You also have the ability to add your own custom dashboard here. So for all your advancement folks this works just like your giving Dashboard where anything you add to that dashboard essentially pushes down these three boxes so you can display any sort of custom information that you want up top over here.

Over on the right hand side, this is where we actually see those various research sources and the data that they contain. So here are just a few examples that we have. If we open up one like a staff research type of source, we can see that there is 1 tab here, a default one, but we also see other details that were perhaps capturing from this sort of staff research source perspective. Something like an estimated capacity that the staff member just happens to know and is able to fill out here. Or maybe there's some sort of.

Proprietary rating that you have or some sort of institutional rating that you have where you're giving a score right on scale of 1 to 100. Alexander Hamilton is an 87 whatever that means to you. These elements down here or what we were going to refer to as data keys. It's the actual information that you're storing and those are associated with a particular source. If there's ever any ambiguity or you looking for more descriptive information about what something is, you can go ahead and click this little icon here that will actually describe OK. What is this estimated capacity?

Here, right? So we can go ahead and add that we also notice that here we're linking out to any documents of materials can be associated these. So I think of these more is like primary source materials. So if you're ever looking to have the backup reasoning as to why you're entering certain values about a research item, you'll be able to sit in this case, it's Alexander Hamilton's sort of obituary from the Washington Post, but you're able to link out to those different documents, so this is 1 example. There are other examples as well.

So we've worked with well screening company Zywave and Owner Search thus far to be able to bring things in a standardized way. You'll notice that they have links out to their records. They have more tabs here because we're classifying a lot more data keys that are associated to this source. So we're keeping track of a bunch of these items here.

And then maybe something like, are you know another type of staff research. It's just storing different information with different items on different tabs.

Can anything to add here you wanna go look at a couple of examples from your side of the house?

Yeah, just found it yet, but but sticking on Alexander Hamilton for a second, you know that one that one of the things that John showed staff research right was pretty basic. You know the capturing of a a couple of data points right? And then bouncing over to Hwy project. Supposing that against I wave, which is like a source that's coming in, that's not somebody's. You know, Manuel hey, I'm going to type in these ratings, but it is this vastly kind of robust multi tabbed out horde of information right there. Capturing it can be both of those things. They aren't mutually exclusive.

And the fact that you can kind of stack them here all on the research tab is one of the benefits that we wanted to talk to you about. Yeah, before jumping to Kendrick and will show you the example for an example record in student success use case with Kendrick.

Same concept right? Where I have a lot of.

Staff or user research or kind of touch points that are associated with a particular student and a lot of those use cases. Often you know default two tabs, custom tabs with with entities right? But let's say I kind of want this this structure of all these entities kind of stacked on top of each other in a digestible format so that I can have multiple sources. In this case, I have listed advising notes, early alerts that may be populated.

From a form, right? So when the form is submitted, it's populating one of these research sources. I've got coach notes, so you've got these various sets of users that are interacting and entering information about the particular student, but it's kind of like I said, kind of stacking on top of each other so that they're not relying on living separate. You know, very various tabs in entity format, so and this is an example of capture.

Let's say there was admissions research data that kind of persisted through this. This kind of goes to both advancement and student success. Clients. You know, it kind of lives there. On the research tab and persists through the students life cycle. So as the admissions use cases build up and they add little tidbits of research into the research tab. Note that that's then available to become more and more kind of robust and built upon for student success and out through advancement if you want.

Oh yeah.

So Ken sucking about it here on a person record. I was looking at a person record 2 can also is a great example of looking out across organizations, right? So kind of you and talk about NCS or another source of data like that too.

Sure, right so so we're talking about data set types of records. Here you know the person record obviously is one of the focal points. But note that this research is available for other of other types of data set records. If if there is a particular interest in a in an organization or a high school, or a company, or you know something like that, some other data set record. You can also carry it across there and pull in rich robust information from these various sources. NCES is the government.

Organization that provides like iPads, data and NCS is you know, national clearinghouse of educational statistics. Whatever it is, right? So you can take a look and aim for the student success use case that I was really thinking about here. You can call back on school level data to take a look. Dig into Kendricks or Alexander Sean Kelly's record and say let's look at Sean Kelly and what type of.

High school program that he came from? Could it better serve us or could it better inform us on how to advise or to serve him or like intervention methods? You know if if we had a really good crisp history of some statistical data of where he went to high school. So the example here is just to show that you can also house these types of research data points on our records too.

Yeah, you may be asking yourself how do we set this up? Right now we have it behind an early access setting, so if we actually go to the configuration keys section in your database and you scroll all the way down, there's a section here for early access features, so it's called research. Just click it about 15 minutes will propagate throughout your database and you'll be able to sort of access the configurations for setting up these different research sources and keys.

Where it's located? If you go to the database tool and we Scroll down under the configurations section, there is a research configuration and this is really where you're able to set up the sources, right? So NCS is a source. I was a source staff researches the source as well as data keys. We're going to go into what data keys actually are and just a moment in the side, but just know that all of this is sort of within that configuration section within the database. So let's pop back over to our presentation. So that was sort of.

Big picture what this thing is, what it could do will talk a little bit more about that here. So what our research sources right kind of alluded to this. It's where the data ultimately comes from. This could be something like databases that are out there, or data leaks that are out there that you're sort of appending all this rich information from. I would join your search or good examples of that. This could also be human intelligence, human capital intelligence. It's stuff that you just know about the person or your staff, your researchers have.

Done a bunch of digging and information. They're looking to add it to the record in a way that's queryable, that's reportable that you can log in and add, you know, sort of all that information in one unified space. It can come from outside companies, so you can mention capture if you're doing any sort of prospect scoring or student scoring, or they have some sort of secret sauce that they're using to say that somebody is more likely to give less likely to give. Someone is more likely to be retained. Less likely, those type of elements you can.

Have as a research source. It also could just be stuff that's out there in the news, right? You're you know somebody has a. You know somebody passed away in their obituaries out there? That's a source of information that maybe has a material associated with it as a backup to say this is, you know this is legitimate. This happened so news sources are other great examples of a research source.

So that's if that's sort of step one is defining the sources. Step 2 are what are the elements or information we're looking to store on each source we refer to those as data keys. So what type of information is being stored? This could really be pretty much anything. I think Sarah had a question earlier about candy on the beat words, right? Like qualification. Yeah, absolutely you can have things that are a data key that stores sort of that stage right there in an have a prompt list associated with that particular data here that list.

All these different stages that somebody may be in, it could be real numbers. It could be money, strings, date times, links, out to that news article links out to that person's record in another software service that provided a bunch of that sort of screamed information. But think of data keys really as the information you're looking to capture and store and associate to a source. There are two general ways we think about associating those data keys to source. Really one to one type of relationship and a 110 minute type of relationship.

So something like you know, estimated capacity, somebody's capacity to give money. You know I may have my own sense of what that is right? As a staff member, I can say somebody's capacity is X screening company might have their own idea of what an estimate capacity is. Another company might have their own version of what that should be. They may even call it all different things, but if really what we're talking about is common between them, that's going to be a shared data key, right? This is sort of a key differentiator between something like research and maybe something like entities where you're.

Able to have sort of these single keys that are able to be associated to and referenced by a bunch of different sources, so we can now not only query information from a single source, but we can start to look at that value as it exists across many different sources.

Yeah, student success case ratio is talking about, you know, wealth screening and stuff like that. Think about the expanded users right? That are more and more of them are being developed into slate. Same concept for something like you know, a risk assessment score. You know a coach might be giving that in some shape or format form or format in advisor of faculty member, another staff member, right? And the concept of that shared key is it's this commonality between all of those.

Sources right? Even though they all might have their own maybe is kind of sub definitions of what that means. It's that shared key as opposed to something that is kind of private or proprietary to just one of those users.

Yeah, and that private thing is is a a private key would be what we call it, and so that's the other option for data key where you have something that is that secret sauce or that specific way of rating. So like your donor search scores, right? That's applicable just to that one company, not necessarily to, well, you know your regular staff member who may be adding something in right. So that was where we're looking at something that's private versus a shared type of key.

Just looking at it visually, this might help with sort of an example. So say for instance you have two different data providers. You have this Bank of shared keys, but also some private keys, data provider number one. They may be providing information about the giving capacity of the count of gifts and obituary, record household income and then have their own sort of proprietary rating or proprietary calculated scoring that they do. But then you also may have another company that maybe uses some of those same keys, right? 'cause the data they're returning really is.

Similar or the same that those keys can apply to the second company as well as their own set of secret sauce or private keys that are applicable just to them. And we see this over on the student Success Side 2. Can you want to chat about these guys here?

Yeah, that same exact concept, same exact kind of structure. You have shared elements that could kind of go across no matter how the what's input or what the input is like. Risk assessment or overall concern. If it's a piece of data or data factor that is coming, fries defined somewhere else from the LMS or from the SAS, right? That's that's one structure, you know.

And then there are private keys that are kind of specific to that input or specific to that source. So again, in that kind of user case that I called back on, you know something like number of missed practices, if that's if that's an element that wants to be captured, you know an advisor probably isn't going to be filling that out. That might be specific just to some type of coaches interaction or early alert beings specified. Having specificity too, like class attendance, right?

Um, so you've got this mixed kind of bag of shared keys that you want across the board to be applicable across courses across resources. And then you've got a private ones that are really specific to just one kind of cohort or one source or two.

Cool, so that would be fun to walk through. Sort of an example right of just a basic staff researcher, researcher, type of source just to show how the pieces come together, talking about how they can be added to records. Let's look at getting you know where materials are coming through dashboarding querying. So let's go ahead and we'll dive into sleet so.

We're going to the database tool set down here in research configurations as we're going to set up both our sources as well as our data keys, so we'll go ahead will add a new source here. I'm going to call it.

Researcher source that sounds great. We can go ahead. We could put it in a folder, have one called stuff research. We'll go ahead and just leave that there. This is where you're able. Just set your scope so we have person comes in. Foundations, funds, organizations, organization Contacts over different datasets, including people to the question that some of you may have about. When does the Research tab show up on your record right? The research tab will show up on a record if there is a source that is scoped to that record.

So in case of persons there has to be at least one person scoped research source for that tab to show up and you have to have permissions to be able to to view the research tab. Now there's a separate permission just for that as well as realms and other things that will get to a little bit later in this web and R, but just if you're wondering, sort of how this appears. It appears by the existence of a research source.

Israel.

Yeah, and then that last option here for settings you know as we slip into the conversation towards the end. About permissions you know. Note that the realm Ification as Sean and I often call it. I don't know if it's a real world word or not, but you know, Realm becomes this kind of default. Hey, do you want it in a realm or not? Because we know that you're likely in this kind of shared environment. So do you want to set a realm on this research source from the start from creation?

Yeah, so we leave it as unrestricted right now, which means that anyone who has access to view this research item will be able to see it, so we'll go ahead and click save.

Yep.

And here we are. So this is the the source, right? And we'll be able to start to see any data keys that we want listed here, as well as any private keys that we can manage. So maybe we want to do something where we add a source to this. That is something like a let's go a private 1 first. Can what do you think something? Just like a? I'm going to call it my researcher rating right? And it's going to be proprietary to the source. No one else is going to use it because we have some special way of calculating this raping, so we'll go ahead.

Will add a datakey.

We already have data keys that exist, so you know based on us adding sources from other providers. So we have a whole list here. You can either choose one that exists already rather than recreate the wheel, or we can add a new one, so will add a new one, will click next. We'll give it a name. I'm going to call this something like our secret sauce rating.

Huh?

Yeah.

Rating sauce that sounds fun. The memo? This is if you remember that little I that we saw when viewing a particular data key that describes what this is. If you want to explain to your users what this Gore actually means, right? If it's scale of 1 to 100, or if it's some of their secret coded message that you have that describes what the rating is, you can describe that here. I'll leave it blank for now.

Member provides a nice coat, little pop up right, you know? So if you do click that information that lurk is I little button next to it, it'll it'll come up with popup that explains exactly what it is.

So we go ahead. We'll add it to a category so we have some categories that already exist because other some other of our data keys are associated with these different categories. So maybe this is just something that's on the details category, which are categories ultimately become as they ultimately become. The tabs that you see when viewing a research record. There are ways to have you know, we saw that we had some.

Things are on that default tab. There are ways to modify these categories to be able to show them on the default tab versus standalone tabs will talked about those in just a moment, but just know right now that category it's a way of grouping your data keys together and it also translates to tabs when viewing it research record.

Will say it's active and we'll go ahead and choose our data type. So this in this particular case and maybe we want it to be a real number. This is also where we're able to say. Is this something that is private just for this researcher source, or is it something that can be shared and added to other sources that exist, right? So if this wasn't a secret sauce rating, but was something more general that multiple sources could provide the same information, we can add it to those multiple sources here, since this one really is only ever going to come from this researcher, source will go ahead and say that it's.

Private just for researcher look like save.

And there we go, we can see it's on this details category. We can see it's a real number. We also see it showing up over here as part of our private keys.

So maybe we want to do something that is something that's shared, right? We can do the same thing where we can add a data key. We can either create something brand new or we can say we know that there's other ratings out there. We know that there's a major gift likelihood type of score. It's going to be an integer. We know we made that for other sources. We can go ahead, click save. It's going to add it, and it's kind of already automatically put it into that rating category here, so we can very quickly start to build up what these data keys ultimately look like.

So this is feeling pretty good for now, just as a again high level example of the connection between these different items. If we navigate back over to Alexander Hamilton.

Could our research tab?

We can click the new research data and now we'll start to see are different sources. So we see research. We can set a priority on it. We can set the date they'll default to today.

Click next, but now we can go ahead and add the data that we want. And if your researcher notes any other sort of long paragraph explanations of why they're adding this, what made it a good source? Any other details you want associated? We can go ahead type those in here. We're able to put in that secret sauce rating. Maybe I wanted to do 88 there if I want to, and then rating that major give likelihood that sort of common shared data key is over here on this ratings tab. 'cause that was the category it was in, right? So maybe again, this is a number.

Maybe something like 76?

Then go ahead and save it and there we go. We always pop back in. View it edit if you have the appropriate permissions to do that as well, and you're good to go so you have sort of your research source which is connected to data keys. Those data keys can be either shared or private.

Amanda, great.

Does research show on the timeline? Yeah, so we are auditing everything, so anytime that we're setting these different values you'll see it here on the audit log. If you have that appropriate permission.

Question.

Yeah, and Amanda, if you're asking for maybe the converse question like I don't want something like this to show on the timeline, right? You know this is information that maybe we want to avoid having on the timeline because the timeline so accessible right? By kind of all users. It depends on how the information is collected into that source into that research source. So I have one example on Kendrick where if you want to video.

Look at forms. I think I pinned to form up there in for regular forms in research example alert form. So I actually built this out so if it's populated via a form I 'cause I wanted to show this example for the student success folks out there who may have faculty or your staff that are filling this out who aren't inside of slate. Maybe they're filling S via portal or something. The submission of the form will show on the students timeline and also populate the research Source Research tab.

If you want to avoid it showing on the timeline, it may better serve you to access it via and created basically via this person's record and actually create it right there on the research tab as opposed to having it populated by form. Definitely something to consider though depending on kind of the nuances that you're using the form for or that you're using the research form or.

Yep.

Yeah, it's also kind of a great segue Ken into sort of how do we get things added to the record, right? So we saw the example of doing it directly from the record itself, but you could also map directly from a form. So looking over here will create research items for every source that exists. That way you can map directly to.

If you're doing that, coaches notes all those different items that are associated to that added to a form. This same type of destination mapping is of course going to carry on over to your upload datasets. So as you're getting files and you're bringing them in a mass, you'd be able to map to those different research destinations. In fact, if we go take a look at some of those, this is another great example of looking at sort of the other benefit.

Research, which is the standardization in terms of a library, so we're creating an ever growing library starting with two things right now, but growing in. Sort of adding in elements that are needed for these different sources. So for something like I wave, we've gone ahead and packaged together all the different things that you need in terms of data keys that you know they require in terms of prompts that may be associated with their data keys that have their specific methods of insights or categories or ranges.

As well as screening queries and source formats so that source format is when you get the file back from them, you're able to go in and actually see the information. So if we go take a look at our source formats, we see that the highway I wave one's been added. It's been pre mapped based on us collaborating with the folks over I wave. Same for over at donor search, but we're doing the same sort of thing where we're doing that mapping to sort of I wave research source and then saying what that data key is that we're looking to store that information.

So while this is standard, if you're ever looking to map things to, you know you want to make your own keys, your own type of information. Do any sort of transformations. You can also double map to these. You can change the mappings, it just comes with what is standard, but you can of course customize it so.

Yeah, and Sean brought up a good point. We've got these two right to start the library or the available options with with these various advancement, focusrite or student health screening focused services right that library list. You know we're looking to grow right? That's not just going to remain too. So as the admission, all of the use cases that come up in fact, you know when you click on the library, it's going to say if you don't see something there, but you have a source, you know that you're interested in.

I've already had a couple of conversations with students success folks that say, hey, we've got some regression model analysis that we want to bring over from. We have another system on campus that does some of that for us, but we want to have that be a source where you can populate that information in from the other from the other system. You know, we call these sources that may exist in library to, you know, maybe the source is your SSIS, right? So it it doesn't have to be these kind of we treat them as like third third party vendors, right? It could be something that is.

A third party, but it's it's on campus. It's one of your kind of part of the campus ecosystem. So Sisc or LMS or the Rez life system, whatever, whatever it might be called a source so that you can bring some of that data.

Brian.

Yeah, me athletic systems right? It would take us. We have season tickets passes, all that sort of stuff. You can now be contextualized in terms of its research. It's additional information that we know about the person.

Is this where we're talking about? Kind of when to do it?

Then decide.

I.

We're talking about, yeah, just just one say I want to just briefly show the materials inquiring just for a moment. So we mentioned that you can have materials associated with it. We saw an example of this newspaper clipping here, so it works very much. The same materials work across all of sleep where you can create a material type. It could be scoped appropriately, and then when you go to your materials tab we can start to upload this instead of being associated with the gift over to the Folio.

Alright.

Will see all these different research sources down here, so you can choose which one in particular you're looking to associate it with. A quick word 2 on sort of the queering of this data, right? 'cause we're now starting to append records with a lot of really good, interesting action. Will type of information. So what does it look like from a query perspective?

We are able to if we come down to the related section, you'll notice that in research here we have sort of research research data as well as a base for all of the different sources. So if you want to query on all of that researcher, one that we just did, or the iwave ones, or the donor search ones, you can do that. You also can start from something like a like a person or like accompanying foundation. Start from here and then start to join in things where you're saying I want to look.

Not just at a particular source, but I want to look across all of the different sources. So as you start thinking about what those shared keys are, maybe you want the the highest rated giving capacity, right? What's the top end of that? Regardless of the source? Or maybe you want to limit it to just one source or another. Or maybe you wanted to do concatenation that shows the three most recent ratings, regardless of where that reading is coming from. If that's a shared key, you can start to do that.

Joining across all the different sources, or you could say now I just want to stick with just one, right? I want this particular information from this particular source, so a lot of options there from a configurable joins querying perspective.

Can I think now we're hopping back over?

Yeah, so it's a good good conversation and say OK, well you know how am I going to use this information? How can I access it right? What it how can I call on the data that I need to in easily or kind of intuitive way?

We're talking about permissions in a little bit, but yeah, part of the conversation needs to be like we said at the beginning. What's the information that's being captured, right? What what do we? What are we doing? Are we collecting information from the student or from the alumni or from the potential donor prospect? Or is it research? Again? It kind of goes back to that definition. Am I putting in as the user? Am I putting in something that isn't specifically, you know, being gathered from the student? It's kind of my evaluation.

And that's kind of this research. First entity conversation that we're having is Sean and I had a lot of internal conversations about this, right? Like, OK, Well, should we? We have a lot of you guys on the call specifically, but just generally who love using entities, right? It's a nice way to display kind of that.

Nice Rd out or kind of the chronological display iterative display, but again to the point that showing up on the screen, what's the information? Is it known by the person? Does it take time or effort to figure this out right to Shawn Shawn's point about the dinner? Is there some type of investigation being done? Or research literally Nope on or is it contextual information that's really kind of at the core of like?

Why should I use researcher versus? Why should I use an entity?

Yeah, sorry sorry.

In a in use on the screen, we just skip past permissions. Cameras going this direction so will hit. This will go back to permissions, but this first point of research facility is actually really key, right? It's it what is the information you're looking to store? Is it require this effort? Does it require somebody taking the time to dig in to find out this additional information that the person or the student may not know themselves? Even right, so you give somebody a rating? That person probably doesn't know what you've rated them, nor should they probably ever know what you rated them.

But it's that additional contextual information that would otherwise be unknown about that person. So that's sort of the key thing. The other sort of thing to consider is when you're evaluating is this a research thing? Is that an entity thing? Ask yourself, do we need to look across shared data points, right? The ability to have these shared data keys that can span sources as a really neat function of research that you can't necessarily get at inside of an entity.

The other thing about research is it is very standardized, so you can say this is what we're capturing from this particular source and our library. You know, as it exists in as it grows will have all these other resources that are going to be included to help you leverage that particular source right in the case, if I wave and owner search, it's things like a screening query, a source format, the data keys, the prompts, those things that you'll actually need to be able to send and receive information.

What?

And then the other thing too is materials and this sort of greater permissions capabilities around research versus something just like an entity where you can have a material associated with a research record, you can have permissions around sources and verified sources in the tab itself, versus just perhaps relying on custom permissions or tabs that have permissions to control who can views or your entities for sort of key points.

Sure, 10 any other things to add here?

You know basically everything you just said, right? You know thinking about again if we're calling like, OK, So what is the difference, right? You know? Sure a lot of similarity in display and function, right? But there is certainly individual and specific use cases for each, respectively. I think the fact that you know the view of the research tab kind of becomes this like stacked form of entities right where it's these multiple sources across campus, right? That are kind of in.

In order right that can be accessed individually, but you can also just kind of get this general sense of how all of these all these bits of information are collecting up overtime as opposed to let's say you've got tabs and entity you know, tap excuse me, an entity on a tab, right? You could go that route, but then it would be an entity stepped on an entity. You start fooling around with the real estate on the page where you gotta scroll top to bottom. Kind of a lot or go to left to right in terms of tabbing out. All of these various entities.

So the option really comes or excuse me, the thought of like OK could this is is it going to benefit us ultimately to live all on the research tab?

Yeah.

Yeah.

Yeah, I like to use the example of somebody's involvement on campus, right? So you're keeping track of somebody's committees that there are part of right. You have an entity for that where you're keeping track of the committee name, their role in the Community, the start date, the end, a notes about it. To sort of this, this row that keeps all that information together, I would bet that that person who was on that committee would tell you that they were on that committee. You know they were on that committee. They know they were on that committee.

Yes.

It's not anything new that you're sort of that they're telling you, or that you're adding, so that's you know goes back to your question. Number one up here, which is, you know, is it known by that person? If they would just as soon as tell you, maybe that's something like an entity versus something that actually requires research or effort, or sort of additional things. So that's just one example of a good use case. I think of an entity that probably doesn't translate to research.

Uh.

I looked ahead so I'm sorry. Now we gotta go back.

Yeah, well, we'll go back over here. Not a problem 2222.

So although we just talk about him one by one here in terms of permissions we talked about, when the research tab appears right. So if there's a research source for the scope, it will show on those records as long as you have the appropriate permissions to view it. Other permissions that exist there is this edit configurations permission where you can actually go in and have the ability to go to that research configuration section. An ad sources of research right being able to go and modify the keys or add a new source.

That's what they had. It configurations is edit data is where you're actually able to. You can see of course the the research tab, but going in and actually changing data points that exist there, right? So maybe the thought that the rating was in 88, but it actually was a 68. Being able to go edit that bit of information, so that's the editing of data permission.

Then there's verified data. So if you're receiving information from a verified source right, you're doing something through upload data set. Maybe it's coming in from my waiver toner search, where I'd say, quote unquote. Verified you know it's a source that was set up, and they have certain ways of storing information, and you don't want somebody who's just a normal staff member to go and modify what those things are necessarily.

You can not grant them that edit. Verified data permission right? So if it's coming in, if it's verified they can't edit it unless they have this type of permission. And then there's the viewing of the data, right? This is probably what you would give to most of your users in terms of accessing this research. That's just the availability to view research on the record, and if you don't have you data, even though a source made exist for the scope of the record that you're looking at, you won't see that tab. If you can't see.

Research data at all so that last one down there is probably the one most likely to give out to the majority of your users, and then, as we alluded to before, the ability to put individual sources and realms. So the idea of maybe you have certain sources like your you know stuff you get from third parties that you don't want your everyday stuff Members to see. You can put that in a realm only people with access to that room will be able to see that source of information even if they have the ability to view data.

Right or added data? They don't have that realm. They won't be able to see it.

Yep, yeah, similar conversations that are constantly swirling around kind of ramification and permissions is what type of sensitive data may exist as you expand your user network across departments where you have many users from many different offices that may or may not be should may or may not need to see certain types of notes like this. Actually, you know this is a really good conversation. Have surrounding research to say. Are there sources that exist on this tab that the daily kind of view only user really shouldn't?

Be able to access a read or take note of it should we should only be kind of Privy to a certain office that it requires to see that type of sensitive information. If it is sensitive.

Yeah.

Tell about these things, so I think we're at the point now, Jenn.

Yeah, this is.

What questions do you all have right? We can hop back into sleep. We can answer questions if you want to throw him here in the chat and also understand that this is all new, right? So you probably have swirling pods, but we're happy to answer and any initial questions that you may have.

Yeah, these are. These are new sleep words that were throwing out, you know, data keys, shared keys, right? And as with any new feature, new enhancement or whatever new thing Insight takes a little bit of practice to get used to it, but we wanted to get this out and talk to you guys about it for that ultimate effort of of.

You know assisting you in your goal, right? You're collecting information you can report on that information to make an impact on the student record or the person record whatever record it is right. If it's the student success to ultimately help them in their how you're serving them are helping them retain or persist or graduate. And in in the advancement case, how much information you're arming your your prospector's or your gift officers about to know about the person. It's it's really, really valuable.

But anyway, so.

Ron's talking about priority coming into play.

Yeah, good question. Um priority maybe if if something needs a so you got the timestamp right? So no problem getting the date and put it in kind of sorting. It's a date order. Let's say that you have multiple sources, but one of them requires attention immediately, right? So a source that is coming into some kind of high visual or high priority alert like you need to intervene with the student. I'm talking from my use case right? But you've got similar. You know something that needs attention.

Right then and there, because you could also trigger automation off of these things too. That says if a high priority source comes in, you know send a message or trigger something to Sean that says Sean you have to go do something in Slate now because something requires your attention.

Yeah, I think priority, like all things, we have priority in Slate right? It's open for any use case that you're thinking of for it, right? It's going to be different for every single institution you know. Some people like Ken's a great example. Some other people may be looking at priority as a sense of, you know. Is this information useful to me? How helpful is it? Was the quality of it almost as a proxy for quality? Well, of course be doing rankings. We know when things are created when they're updated, we can always get the latest and greatest one.

But maybe you have a staff research or you know source that has information contained in it. That's actually really important that you want to be able to quickly identify, or you know it's a single. It's that researcher source, but because the data inside of that source is at such a level, you want to trigger some sort of alert, right? So you can query off of this, or elevated to maybe show on the dashboard on this research tab, just to sort of sources that are high priority in certain information within them.

So it's just another thing I like to think about most things in Slate as just another data point that allows you to sort of flag or add additional details or layers to that sort of row of information.

Yeah, it was good. Good another piece of information at your at the ready Laura. Great question. Can you adjust this view right? OK, so Sean you want to tackle that one?

Yeah.

Yeah, you can't. So just like other areas inside of slate, you can come down here. You can click the customize view section. You'll need to do a few additional joins from here to actually get to the data, so you may need to actually join from research actually to the research data. Again, define you know throw offsets here. Which piece of information you're looking to grab or not. So maybe I'll just go forward with this. Sure this is great.

We can start to add, you know, different pieces of value. Things like this.

Yeah, maybe that's the value matter could do any type of information, right? So something that's just like I don't know the time stamp.

Yeah.

Or just the.

I've got it. I've got a user. I've got a user export on one of my own on the other record, right? If you wanted to capture, you know if it was an individual user, may be where the forts, yeah?

Created or something like that, right? You can just go ahead and add it in. It's going to save.

Yeah, it says you're getting a resource unavailable error, Laura.

Yeah, we could look into it.

Yeah.

It's weird you should get the back custom indexing thing at the bottom so.

Gotcha.

Philipine API with external utilities you're talking about just sort of sending and receiving this research type of data. I'm going to sign in a little bit more automated of away this is going to work just like any other sort of way. We think about queries referring to use any sort of web services or some sort of scheduled export import process to be able to send and receive information. Works the same sort of way. I sort of think that.

You know this, this sort of method and we want to get your feedback on it right? Does this work? How this library things at work late? Of course, as everyone on this chat knows is a very iterative process. So if there is something additional you want to see out of this functionality, create that feedback post. Let us evaluate it. I can certainly see value in doing sort of individual types of screens or research, right? So it's not just a screening query that you're sending out to another type of service, but maybe there's a button here. There's something that does it as sort of a one off API call.

Welcome back to the thing, not current, but it is something that could be something in the future, right? We want to hear your thoughts on it inside of feedback.

Yeah good good good Cauchon tell us more about it. You know if you if there's things that you want to add it to the library, same kind of conversation. Let us know how you're using it and maybe how you want to use it, right?

Right, Ron Ron made a good point about the maybe getting there. If nothing's creative, there's no research configurations created yet.

It might not allow you to customize what it looks like if there's nothing there populating. If you already have that school, which on and I'll look into it either way.

Take a closer look.

Any other questions? Those were good, really good ones. A couple of really good ones.

Do you have any other suggestions for one off all screens? For example, we often just run a screening on an individual, not a whole file. People want to put that into research too and love not to hand enter it.

It's a great question, Raymond. I you know there isn't a way to do it in sort of a one off manner right now. Although I would say when you have your you know your screening query that you're doing the filter criteria that you add on to. This can be totally custom right? So you have these ones that we built that you know those type of services require. But say you know whatever criteria is, maybe you set an interaction on their record that says I want this person screened right? And maybe it's just a.

You know, once a day thing where you said that on five different records throughout the day, then all of a sudden you have those people falling into this query that then you do that, screening the upload to download and have it come in via the source format. So you're not hand entering it every time.

Uh, that's the only way I can think of doing it right now in terms of a one off way quite feel like the marketing if your screens, yeah?

You know this in in terms of, you know, for your guys who are doing this sort of wealth screening type things. This filter criteria here can be based on any number of things, right? So you think about it in terms of you know every time somebody submit your online giving form, if they haven't been screened within the past six months, throw them into the to meet the criteria for this particular query and then maybe it's just the daily or nightly process that you're able to then screen those people. That's right, so there's a little bit of a delay because you need to.

Create the project file in the sort of the other vendors platform, but then you're able to bring those things and sort of on mass or on small Maps. If it's like 5.

On on one.

One on one hand, right? That type of thing.

Yeah.

One person mass? Yeah, no good. Good questions. Laura brought up a good one too. If you give someone you know limited view for looking at the research tab, you know, but we still want to push him to a form. Will that still go into the research? Definitely? And that's a use case, right? I don't really want them kind of involved in the research tab, but I want. However they are engaging with slate to populate research. That's a perfect example. In fact, that was a lot in my head for the student success. We have users that we we don't need them.

Fit.

Yeah.

In research, but we need to collect their information into research so form that's populating. Research would be a great way to go, right? Have leave you know, given URL to the form through a portal or through the URL landing page and then that gets consumed. Yeah, totally agree. That's I'm with you, that's that was a lot of the impetus for this use case. Early alerts, faculty concerns, staff concerns where they don't need to be in slate fully right in these tabs are on the person record, but you need to consume information.

Yeah, and some other you know just we're talking high level about the tool here right? What are the pieces? How does it fit? Together, they're going to be fantastic use cases that I'm very excited to see everyone you know put into practice.

Sure.

One one that I'm excited about. I know Ken is 2. It's this idea that in the future would be able to have something like workflow or the sort of reader process where maybe you have a bunch of research type information, but then you're able to send people through flow and have all this research stuff be evaluated in a very reader type of process with forms being filled out to verify to say if somebody is qualified or not, and moving them to these different buckets and have that be really automated through the rules editor. Moving people through these workflows.

Yep.

I'm pulling all the information from various points of Slate, so that way a human researcher can actually evaluate and say, yeah, this makes sense. We're going to put this person into our major gift pile, or this is going to result in an opportunity or whatever else. It is so fantastic use cases, I think abound in terms of leveraging this information. Readers, I think going to be a really great one. I think communications operating off of this right so that point earlier about it stuff that the person may not even know you know.

But you can still act on the information. Maybe have drip campaigns that are going to people that meet certain criteria. They may not even know why they're getting this. This stream of communications, but because we're referencing it right in slate, they're flowing into these populations, or doing drip campaigns and things like that. So a lot of really great use cases. I'm sure we will have conversations about all of those different things in the future today. Really, just about sort of what the pieces and parts are.

Sure, sure, and John and I kind of always if you, if any of you knows which a lot of you do on the you know we always kind of geek out about this this data.

So.

Mine right? You know? If we're thinking about life cycle, another thing that Sean and I talk about an awful lot, right? You know, imagine this this research tab being comprised of admissions research sources, right? As they've got as a student, has gone through the admissions process since, like student success, early alert faculty concerns, right? So by the time they get to advancement, the screening, those screening folks they have this massive amount of data that they can call appan that that may come from a couple of different places in.

In sleep, but it's kind of truncated an easily digestible, more easily digestible Hall. On this research tab to really go to town and have a crisp understanding of what Alexander Hamilton's history looks like.

Yeah, yeah.

I know we're just short of the top of the hour and these are great questions coming in. Sorry I'm in your head, John Michael. I think we're probably thinking the same stuff in terms of reader and things like that. Yeah, lot of really sort of great use cases coming in there. We do want to sort of just highlight a couple other upcoming virtual events. Our colleague Erin Gore is talking tomorrow about slate.org. If it's, you know she's going to be talking about the new functionality that's allowing.

Absolutely.

Students to actually create profiles inside of like data or can sort of connect that way. So definitely check it out. It's going to be really cool. It's going to be, I think, a huge impact in terms of access to higher education. Can you talk about these two?

Oh yeah, yeah I'm coming up next week. I just posted it in the form. There's a student. Our third student success community call where I'm going to talk about 3 topics query library which actually is Alexander talked about in his last slate spotlight going to touch on that. I'm going to dive into research a little bit more and we're going to talk about something else. Customizing dashboard cruise for any student success folks who want to join an any. Actually, whoever, whomever on the call. If you want to join for that will be talking about that and then March 9th, Tuesday after next. We're going to be doing community conversation.

Highlight talking about grad professional admissions where we have some guests from partner institutions talking about, oh, you know, the opportunities and challenges that are facing grad and professional admissions in in the higher Ed Sphere as it exists today. So we were busy. We got stuff on the calendar and if you want to join for any or all of those we we always love to see you guys.

Yeah.

Absolutely.

Awesome, well thanks everyone for signing in today. Appreciate the time. The thoughtful questions, the commentary, all great. Really appreciate it. Let us know how this stuff goes at any point in time you want kinda ride to hop on? Maybe do another in depth type here for the greater community or even do focus. Call us to talk about use cases or putting this stuff into action. Always able to do that. Happy to do that. But yeah, big thanks to everybody. Have a great rest of your Tuesday and will see you guys again soon.

To carry one.

See you guys later.