Student Success Community Call

Hey buddy, welcome.

And give us a couple seconds to have everybody Rollin.

Thanks for coming.

Good to see everybody. Hi, what's up Elliott?

Hey Amanda, got some tunes blasting in the background this time for you guys.

What's up? What's up? What's up, yes, drop in the chat where you're from, what the weather is like.

Here in.

End of Winter, Connecticut is cold today, but I think this is kind of one of the last days.

Sunny petsburgh

We got some folks.

Some favourites on the call, so thanks for coming cold and sunny. I'm getting a lot of that myself.

Yeah.

Yeah, cold and sunny.

Glad the middle of the country is kind of.

And I think for the most part, out of the, you know, ridiculous, ridiculous run that they that they went through over the last couple weeks.

Cool well welcome for couple of minutes in already. Yeah there we go sweet we think we got handful of people here which is fantastic. Hello everybody ain't Nicole Nickerson what's up cool so welcome. Hi Ann Ron yeah cool say what's up in the chat say hello where you're from like I said and welcome back to iteration number three of our students success community call. We had a couple of these at the tail end of.

2020 and we're back again. For the first one of 2021, so I'm happy to be here with you all today. My name is Ken Higgins. For anybody who doesn't know, May. And I'm the general manager of student success here at technicians, and I've really kind of liked using these calls these Community calls to really focus on a topic or two or three kind of of whether it's a recent feature enhancement or a new feature.

Or just something that can really help or or benefit your use case inside of sleep. I know we kind of called the student success community call so this kind of sub cohort of of our users in colleges and universities were using slave for student success efforts advising retention so on, and so forth, but I know that there are others. At least I know on this call specifically even Raymond since. You said hello. Already, I'll call you out, you know who might be from another area of the University or be using slate in a different way.

We're happy to kind of have any and all as part of this conversation. So I appreciate you all being here and hopefully we get some we get through some good stuff today, so happy happy to be with you all.

And I know like I said, you guys are my you guys are my favorite people so I enjoy talking with you all. Learning from you guys and and being able to share some some good stuff. Some bits of information. So let's rock and roll. OK I have kind of limited slides today and we're going to be doing a lot inside of slate for the three topics of recovering, but just as an FY, I kind of conversation. The General info slide. This webinars being recorded. I'm going to make it available as a recording or kind of in the knowledge base.

There's a section in underneath the student success and advising kind of area of knowledge base where there's some kind of slate TV.

Links the previous community calls are all there and then this one will be as well up in the upper right hand corner. Closed captioning can be enabled by clicking the CC button if you're interested in full screen viewing, which is just so wonderful in full blasting blaring 1080P or whatever you have now, you can click that full screen if anything starts to sound funny or if you lose your audio or video and you need to re sync, you can just hit the refresh your share window.

And then obviously questions and comments and communication in conversations throw it into the chat. There I will be kind of monitoring throughout as we're talking through stuff and hopefully be able to get to all and any questions that that you have. If you have comments about something that you want to do or questions to ask, just throw 'em up there and I'll get to them either right there when they're asked or will wait until the tail end. Typically whenever I start these things or whenever I advertised.

These calls me so I guess you want to talk about these three things with these four things. These two things and I always realize after the fact, I think I've said this before in the previous call after I start building out in China. Kind of make the hour one call. I realized quickly that like I always try to, I'm I'm over ambitious in terms of topics to cover, so we'll try to get to the three things the three items on the agenda today. And sorry if we don't, we will go one kind of another kind of.

PSA if you're interested in student success, right? And you might be on this call because you used to use late for student success. You might be on this call because you don't use late for student success, but you're thinking about it. You might be on this call because you're just kind of interested in listening to what others have to say about student success. So if you fall into any of those categories and you have questions, don't hesitate to reach out to me. Obviously you've got the service desk. You know you have your engagement with us with slate through.

The service desk, but if you want to talk about stuff conceptually or theoretically and say we're thinking about student success or not sure, I love those calls. I have them quite often, so please don't hesitate to reach out to me. We also have our lovely community forum which has had some really, really nice, robust and kind of lively conversation threads as of late, so there's a sub cohort or sub community forum. There's the Big Q Slate community form, and then there's a sub forum for Community community student success and advising so.

You know, if you're interested in kind of seeing what others from the community have to say, or best practices, or get their thoughts, that's a really nice kind of melting pot to get some opinions. Best practices. As always, there's knowledge base, which is our kind of encyclopedic area for documentation and videos and kind of instructional. Know how learning Lab, particularly if you're new to slate for student success and or your new new to slate. And I say this.

Maybe not for those of you that are on the call, but as slate for student success efforts are growing and expanding at a really rapid rate. If you have new users at your University who are new to slate and need to learn slate from the perspective of student success or learning, lab fundamentals courses are available online through the resources section of your database and there are really great that we've got some really good feedback about it. You know there are real conceptual understanding of how slate works and all the fundamental tools so.

If you have new users, please encourage them to take that. If you want to get to know site and then last but not least with the astrex there, the last thing we have our wonderful innovation festival. This year we are going to be at you all. Got the notification about it. You know in terms of.

The the only thing that isn't happening obviously, is that live in person component, which we're excited about for next year, but I wanted to talk about it today or I wanted to reach out to you all and maybe solicit what we're doing. If those of you who attended previous summits before you know, kind of the core content sessions, we actually have a similar type structure for this innovation festival called Slate Stage and Slate Stage is really taking the opportunity for users to amplify a solid use case.

Or a creative way of doing something in slate. So actually this is my call to action on you all. If you have something that you're doing in Slate, which is that she thinks, pretty cool and you say, wow, you know, I think others could benefit from what I'm doing inside of Slater, what my University is doing in slate for student success. If you reach out to me, let me know, because what we want to do is start amplifying those conversations in those use cases to the larger community and say hey, just similar to right are the old.

For content sessions, um, when we're in person at the summit, we want. If you want to be, we want you to be able to tell others what you're doing inside of Slate. So if you think you got a great idea, or you say, oh man, I don't know if this is cool or not, right? Either way, reach out to me. Um, we'd love to. I'd love to talk to you about it. What what? You might be able to do for us and participate in present to your colleagues at the Innovation Festival. So that's my kind of that's my plug for the innovation festival. And if you haven't signed up already.

Please do so. It'll be it's we got some great content lined up for you guys.

Cool, I think those are the the.

Housekeeping items OK, So what are we going to talk about today? We're going to talk about 3 things 33 topics 3 areas of slate first being the query library. This is a something newish to slate new enhancement to the query tool and we're going to dive into that in a little bit more detail and talk about some good use cases. We're going to talk about the research tab. This is a continuation of the conversation that happened last week for those who are able to join Sean and I.

Sean really lead the conversation on what is this?

Again, a new thing inside of site, this research tab and talked through some of the real basics of what it is, what it's used for, how to build out examples we're going to continue that conversation. Borrow some of what we talked about last week, incorporated a little bit more into this. We can talk about specific use case and then we're going to talk about custom dashboards. Actually, this is this is something comes up very frequently on a number of the calls and conversations that I have the use.

Of custom dashboard queries and custom dashboards and how to really.

No, I say spice it up or amplify and trick out, you know, a really nice, highly customized dashboard query that's that's what we'll talk about today. So I'll try to keep it into the hour. I will try to touch all of the topics. And like I said, we'll be diving into Slate very briefly here. And yeah, keep keep the questions or comments or anything like that in the chat an will get wrong. OK, topic numero Uno.

Let's talk about the query library.

So a little background, right? It's a new enhancement to the the query tool to configure joins the query tool and allows you to have institution specific or whatever you want institutions desired or specific exports and filters to be created and and kind of standardized in saved.

You know, really it ultimately kind of makes redundant or eliminates the need to build the custom right from kind of the past. The custom filters and exports that would need to live on a local query base, right? As as the freight train or whatever you know this massive object that is configurable joins is slowly kind of moving into all parts of slate, the need or the use cases of those local query base is kind of continually get shifted.

More and more into the configurable joints world, so you no longer need to build those custom filters and exports on the local query base in kind of exports and filters area of slate you can actually do it right in this query library and we'll talk about it a little bit more as we build them out. Just kind of the ease of how to do it. You know how you can save them at a pretty decent clip and then you can define who needs access to these exports and filters and.

Who's the the most the you know? Who needs them the most? I guess right? Which is which is something we'll talk about you no longer need to recreate detailed subquery exports and filters. I should put exports and filters constantly in there right now for anybody who has practiced and practiced and gotten the gist of configurable joints at any level of expertise, you know that you know you no longer have the.

This need with this library to create these somewhat complex right deep levels, or we call it the inception level right of a subquery filter within a subquery export. That is concatenate versus dictionary export. That is comparing two different things, right? You know and even me saying that that didn't even make much sense, but you no longer need to recreate detailed structures of those queries.

Every single time you're creating a new query, write another thing kind of behind the scenes or under the covers when it's when all of this stuff is happening. It also doesn't need like you might have a query that you're building that already has joins you already attaching joins by yourself and and the addition of some of these exports or filters that are created from the library can add the join. Specifically, it can dedupe kind of extraneous joints that aren't needed at the.

At kind of the top level of join, there's a lot of really, really nice features in the details of this of this query library, so it's something that you know I love I. I started using immediately and I would encourage that you guys do too, or at least start kind of. I'd say practicing with it right. Where is it in slate, right? If you navigate to the query tool on the right side menu, you'll see a list of queries and then query preview query. Parentheses preview is the second option down. That's where you're going to access.

The query library right once you click into there, you're going to have uh queries option defaults to the queries option on the right side menu again. It will choose the last option there. The second option there titled Query Library right and then you're going to it's going to prompt you to create a new library write an at this point. Let's just dive right in and let's let's talk about let's let's do a little showcase of what we're talking about here.

So you guys should be seen Slate. Now this is the student Success Showcase which is not yet available to all I know. I made some false promises. Last community called that it would be available in short order, but time is always my enemy. So here we are. But it will be available for you to provision as part of your clean Slater test environment. Excuse me. Clean slate environment. So if we navigate we're here in Slaton, navigate over to the query tool.

Just like the screenshot will navigate over right side menu to the query preview.

That's going to take us to kind of this. All alternatives, different looking interface, right? But we're going to bounce right over here to the query library, right? Typically it's blank. I've done connected to the Julia Childs method here, where I've got some some pre baked examples. You know the the cake already in the oven that's done while will also build out some examples for kind of from scratch, but it's going to prompt you to create a new library, right? And this is kind of where you'd want to think about. OK, So what kind of?

Exports are queries. Do I want to think about for this specific library, right? The way that I thought about this actually was one thing that I.

That I'm typically interested in, but that sometimes I guess with with a lot of practice I get better with, but the joining from maybe the person base to something like forms and events, right? Or forms forms and events and as opposed to all forms and events versus a specific form or a specific event, a template versus an individual event. Sometimes that language can be a little nuanced, right? So I actually dictated I created a new library and I called it the person library. Just I should. I could have just called it test or whatever.

But when you do create a new library, it's going to prompt you to say what do you want to call it. It's defaulting to configurable joints, 'cause that's where we are. You still select your your category and your base. So I actually selected records and person because that's the base that I wanted to start on. When you when you choose the base right, those library exports that you create. After creating this library, those exports that you create upon creating this library that are part of this library.

Will become instantly available as exports and or filters whenever they choose that base that you created this library offer so.

Bear with me right? 'cause I chose the the persons base right, but in fact the the exports that I'm adding to this library are sub subquery experts that are joining in.

The foreman event form registration form response right and a particular type of form or event. I one of the things that when I was practicing with configure windows tricked tricked me up was like OK. I'm interested in maybe like an aggregate account of how many up forms a particular person has submitted or how many events has it person attended right just give me that number. Give me that count, I don't I wasn't.

Maybe necessarily interested in starting from the form responses base. I wanted one row per person right? So for this example I wanted to create these somewhat complex joint where I had to make a joint. You know you had to join out to some other base to be able to get these exports out, but this year creation of them makes them constantly available whenever anybody creates a query that's on this person base, so will get there, right? So I said.

I'm interested in an aggregate count.

Of this is where I made the join out to my virtual academic advising event and I wanted account of you know how many of those events.

Is exists where the registration statuses in attended? I then wanted to copy that out and nothing really changed here. I still want an aggregate count of though that same type of event that I chose the template actually of active virtual academic advising. But I wanted to see account of no shows and then I wanted to see account of registered but maybe not yet attended or no show. I wanted to see account of all those cancelled, so this is kind of like I'm looking across these registration statuses.

Better associated with the form of the with the event, the form event. But again, I'm still starting from the person space, but I don't want to recreate these subquery exports every single time. Thank you Noel for the for the love. Could you use question? Could you use folder as well so you could we'll talk about that in a little bit. Kathy good good question like folders right? You could use folder you could use. I defaulted to the template right? So the type of.

Form or event was the template 'cause I said I generally want to know I want to be able to pull anybody who attends this type of event. I just want to aggregate this stuff. I also created a filter out so not only did I create these exports because this takes a little bit of time, it's it's a join, right? It takes some time to create this every single time from scratch, but I also want to be able to create a filter 'cause maybe I want. I don't want just one row per person for every single person in my database to show up with a bunch of zeros.

I really maybe only want to return results where somebody has at least one advisement event so that specific event where they are have a registration status of anything like have they registered or been marked as attended, or no showed or cancelled, right? So this is going to trim down those results significantly to get say filter down only right? So you're using for this query library. You're using the same interface, right? This looks like you're building query 'cause you are.

But what it's actually doing kind of behind the scenes is when these joins are created there are saved to this library, right? We're going to pop up here in preview. Our results. OK, so this is prompting me to my exports if I actually were to borrow. We don't want this to be a query library export because we know this is pretty basic. When somebody else creates a query and pulls from library, we don't want this to be just listed there too, because it's pretty straightforward. At least I don't want to do for this example, so I've got our buddy Kendrick I can see.

The information for Kendrick specifically. So again, this is kind of the Julia Childs method, but let's back out from her career library and I might be interested in something else that's really, really simple, but I want to start from the configurable joint space of the actual form or event.

And I want to pull the form title right? That might require a join to the form from form responses to form another kind of it's one join away, but again, it takes that step to make those those joints right? An if you're creating a query N number of times for your users or for yourself that then you know costs seconds on the minute and maybe minutes on the hour, right?

So let's stick. I'm going to. I'm not going to pay attention to this one. Let's focus on this part. This one that we started on the person's base, right?

We've created our joints. We've created our exports. We've created our sample filter, these by default now are part of the query library. These become available and I'll show you how iaccessible they are up here. If you were to choose sharing permissions, you can now control who you would like to have access to these query exports. Let's say I have a particular user or set of users or group or role who really, really is dependent.

On this information, but I don't want them asking me every single time to create a query. They don't have the joins experience. Maybe an but they really they asked me every day for the for query with this information, but they want to change so I have to go back through. I can't just save my query 'cause you know they might have date specificity or something like that. So I'm just going to give them specifically. I'm going to give that user access to these exports and Noah.

Your user would be able to see them. You can also do this by permission by role, and then within each of these kind of grantee types you can choose the permissions that you want to allow. You can just have them display it or or run the query and or have edit capabilities. Alright, so let's back out everybody with me right? So these now by default by creating them they've become a part of the query library. So I'm backing out regular slate I come in.

And I have access to the query library. I mean user this that has access, right? I'm going to create a quick query. I'm choosing the base of person 'cause I'm interested in pulling some information about a person or I won't run one row per person. Alright, great slates prompting me through. What do I need to do? I need to have add exports. You will see that now the thing that persists at the top, the first kind of library.

Of exports that they see are those query library exports that I just created. Alright, so I no longer have to create every single individual sub query expert where I have to join out to the number 50 where I have to join out to the form responses so on and so forth, right? So by default I've got that I can also add the filter here again because this was part of that library as well. Every time I choose the person.

Configurable Joint person base those library filters and exports that I created become available right? So I said oh great, this is actually telling me exactly what I need. So I kind of need this basic and there it is. There's my.

There is my query right and I want to add a name here because that's important and but I don't want to have the name be a part of the query. There we go so I can see that my buddy Kendrick and I've got specific counts in each exporter. Each column has the number of advisement events.

And that's the query library. It is a in terms of a kind of how to be efficient and production productive. This is kind of a real game changer. For those of you that have.

It really kind of enhance your expertise and your configurable joins acumen, right? You typically also become the go to person, right? Hey, can you help me with this configurable joints or you know, I can't figure out how to join from this to this or it's not coming up the way I expected it to take advantage of the library to set these. Set them and forget them kind of thing. Build up your library for all of those joins that have maybe some level of complexity that you don't want to be relied on. You don't have to have your users be relied on.

Offer to use every single time. This may also cut down on kind of let's. I don't want to call it user error, but when they're creating, you know when folks are creating users are creating queries on their own. You want to make sure that the data that they are pulling is is the right data. You know if it's account you want to make sure that they're making the right joins and they're starting from the right base, so use use the query library to your benefit. OK, hopefully that was good. I know. Like I said, it's already.

2:30

two more topics, though, so that's that's the. That's the query library. Use it very much to your benefit.

And create out as you see fit all of those potential exports and all of those potential filters that you need.

OK, we're pivoting.

The research tab. OK, the research tab is a new also kind of a new object, a new thing, a new tab inside of Slate, the the details of it is it? It's a standardization of grabbing point in time, kind of contextual and qualitative information about a particular record.

But it's particularly good for is iterative data or information that could be coming from multiple or many different sources. The examples that I have in there in the sub indent are are if you have an early alert form or early alerts that come from faculty that comment or give you information for a.

A class, right? Uh, class attendance you have it. You may have advisor notes for the folks on your advising team that are meeting with the students may be relatively regularly or have some type of interaction with them and you want to kind of log those notes as well. You have this third kind of area of use of slate, right? Coaches that may be inside of slate, but you want to capture some type of their notes. This really feeds to that conversation about Slate being this centralized data repository.

Where all the information about the student hits this kind of one stop shop, right? It's very very helpful from a I'll say this like a student of mission driven student success perspective, right? You want to consume all this information so that then you can report off of it. You can query upon that data and maybe make it, you know, infer a decision or or get details that might help, intervene and assist that student with with getting what they need. Getting the assistance that they need, or whatever it might be.

Right?

Um Ron yeah, nice thing we found with that library is that it puts it in a grouping by the name of library right? Can use person which puts it in the person group of exports, but if you call the advising it would. Yeah good call. So naming convention right? If there's it adds clarity to the those types of exports or filters that exist by by calling them out by category. Good call around. Thank you.

This is borrowed a little bit from what we were talking about last week, so this new introduction that's a part of research and the research tab are these data keys. These data keys are kind of defined. What type of information is being stored on that research tab, and you can see it kind of borrows from the data types that you may see in like the field and prompt settings.

Got real real numbers? Integers? If you're talking about money prompt values that can be associated with a prompt list. If you just wanted to be kind of open or free text, you can pull in strings and then dates or times. It can be associated with these data. Keys can be associated with one source or with many sources. Will talk about that next right. The source of information. This is something that we talked very briefly about last week, but let's say source A. Write the highlighted in green.

Um?

This this the private keys that, let's say, source A is the coaches notes or the faculty early alert. They have private keys that are only associated with that particular those particular sources, but they have a shared data Kia shared point of information that no matter the source, let's take risk assessment right. The first block in the middle column. Their risk assessment risk assessment is A is a category or a number.

That we want standardized across all of these sources. So no matter if you're a coach or an advisor or faculty, you all have your little notes that you're putting in that are nuanced and complex to your specific subjective evaluation. But we're going to use risk assessment as the standard across all of those sources that we're going to ask you each and every single time, and that shared Keith can then be kind of query dapon as this standard, no matter what the source of information is.

We know that risk assessment is is kind of shared among all of them, right?

I'm going to jump back into Slate now just to talk a little bit about what that looks like, so if you haven't already and if you're interested, you are going to have to activate early access to the research configuration. So where if we bounce over to our database, we're going to jump over to configuration keys.

And we're going to scroll all the way down here and we are going to take a look not to there, but we're going to take a look up here. Database configuration. Second, from the bottom is early access features. You're definitely going to want to check off this research if you are interested in. Note that it takes about 15 minutes for it to be kind of, quote, unquote, activated in the system, bounce back over to our database, and then after about that 15 minutes of refresh, right when everything catches up.

You will notice something under configurations that was not there before called research configurations.

This is where you're actually going to create the specific research sources that you that you want associated with the person record OK?

I've created a couple already that we've talked about. Again, the Julia Childs method. Note the right hand menu over here. You've got research sources, you've got data keys in the library, won't talk too much about the library today will just focus on the research sources and data keys. So if I were to add a new research source, which I already did a couple of them right, it's going to prompt me with some pretty basic settings. What do you want to call this research source? OK, it's going to default to active. Do you want it in a particular folder? Folder structure is always fun and important.

What scope? What are we talking about? What you know? What data set record what record is this research going to be associated with? And then, as we often have conversations with our community with our student success group, the Realm Ification conversation.

When I say ramification often, I don't think it's a real word, but the realm ification of databases, particularly in shared databases. You know should this belong to the admissions realm or advising realm meaning.

You know this research tab or this research source would only be viewable to folks who had two users who had the advising realm or belonged to the advising round from our security and permission standpoint, right?

We're going to leave it unrestricted just for the just for the sake of it.

Um, let's call it coach notes.

Alright.

It's then going to probably through to say, great, you've got your source, you you know what you're called. It's called. It's not particularly restricted to a certain realm. Now let's create some data keys. What do you want to do? What do you want to capture? I might simply want to add a new key that is pretty basic, right? I want to add a new key that's called Coach Concern notes because I have the expectation of the coaches to come into slate and add this research in every time they have a concern about one of their players.

I wanted to live on the details tab and it's actually good, just it's going to consume a string right key here. Keep unintended. This key is actually this key, doesn't really, it doesn't belong. It isn't associated with the advisors research or with my faculty early alert research. This is just for coaches. Know I'm going to create this key as a private key. Alright, but I also want to what we talked about before that kind of common theme I've created already.

A key that exists elsewhere that that exists in all three of these research sources. I want no matter what I want, not only the coach to put in their concern notes, but I want them every single time they put in this bit of research to analyze the risk assessment. This is this qualitative kind of across sources. Doesn't really matter. It's agnostic to the source, but each one of them is going to put in this risk assessment I've already associated with this, with a prompt list, but this gives you that sense of.

What's common, right? What are my? What are my shared data keys versus what are my private data keys for this specific? For this specific research source?

Very simply, I created the coach notes. I created my advising and alert notes. We can look at that. This is also really, really simple. It's actually nothing, nothing more than I just want. Anytime an advisor comes in to create a new source. I just want to put in them to put in notes and then evaluate their risk assessment.

One thing to note here, I may want a research source to come from somewhere else. I may actually want a research source to be populated by way of a form or a form response. Something like a faculty early alert form, alright?

Let's bounce over to the student record to see how this looks and how this is going to wind up by way of creating a research source. Then if you were to bounce over to a record, you can see a tab that did not exist before. Alright, and this tab may be empty for some will take a look at Eugene over here because oh, actually yeah, so you can see that Eugene has no research sources associated with him, but by way of me creating research.

Configurations the tab automatically pops up, so just an FYI. OK, let's go to Kendrick, who actually has some information in there.

This view this dashboard display is actually kind of standardized, right? You also have the ability to add and kind of push what's viewable right here. It kind of pushes it down and you can occupy the real estate up here with a further customized dashboard if you like.

But then, So what this is, is this dashboard kind of provides an over a quick quick overview. Alright, how many data sources exist for this particular record? What was the first source and what's the most recent source we want to dive into? Actually see that in a list form and we can see that Kendrick has a couple of them already, right? I created some of these today to say this faculty early alert form was submitted, but by way of its submission it actually created a row it created.

An element in this research source.

You can see the default tab opens up by. This is default because standard exists and there are some standard fields that populate the created. That kind of metadata. You can set the priority that defaults to the date you can choose, verified or unverified, and then it has a standardized notes tab, right, but you can also add out N number of tabs over here. To say I've got all of this kind of customization of data that I want to add in tabs.

Format so these fields are being populated by the submission of a faculty early alert form that I have over here, OK.

So this faculty early alert form. In fact I have. I don't want my faculty actually to be inside of slate accessing the person. This let me talk about the use case, right? I don't really want my faculty members in here bouncing around the person's record. They don't need to be. They don't want to be. But I still want to consume information from them. So you throw them a portal or or. However, they're kind of accessing this form like this, and they say I've got to type I. I have an early alert that I need to.

Add in about Kendrick right? I'm going to search across the database here. Math 101 is the court's name or whatever it is, and here are my details right? And then my overall risk assessment, right? This kind of across the board I this is kind of medium. I'm not really sure if I were to hit submit.

It would populate this form OK. Attendance missing class with past two weeks risk overall risk assessment medium, whatever it is. OK, you note that you can map these fields to research elements, so research data keys exist and operate an awful lot like fields and problems. OK, it's going to say OK, great. You can choose your.

Dedicate your research datakey

and choose which which datakey it's pulling from OK.

You can then list out, imagine like I said that came by way of a form, let's say right, but I I'm an advisor and I just want to come in and add this note to Kendricks record, 'cause I ran into him. It was kind of an ad hoc conversation. Nothing to worry about here. Very low, but I want to log this type of interaction right? So really basic. Good way to keep the notes clean so on and so forth. To answer your question. Also right? So Elliott first can you batch import research? I'm picturing this would be.

Capture point in time student data from the LMS Elliot Beautiful use case. And yes, you absolutely can. You can map directly to these research research fee data keys and that's a perfect example. Yeah, LMS data, SSIS, you know data points, right? That are iterative and you want to kind of capture them in comparing overtime. What's ultimately going to happen here is you're going to get this really rich, robust across sources timeline.

Chronologically of kind of these these research methods with these research efforts, here is what our coaches had to say about Kendrick multiplied out by 25 instances. Here's what our faculty have had to say, and all of this information can be queried appan across the different sources. So you get this really clear picture for talking about kind of research to be able to kind of categorize and view data, right?

Um, can you map these fields in from event forms if you had sessions as events, right? So similar things. Same thing as a form, right? So you can pull in information from a former an event you know an event for. Laura Lions does the addition of research data show up on the timeline, and then know I'll say hey, what's up with this timeline? A constant question that comes up? I need really lock down access of this type of information and if I have really lock down access on the person record.

Um, what sometimes you know comes up is like but they can see this right. If I were to create a new, let's say coaches notes.

Um?

Testing

research source. I just created it. It does not appear on the timeline.

If I were to create a new advising alert.

Another test.

It does not live on the timeline.

If if a.

A research source is associated and tide to a form that form response will live and be accessible on the timeline. Something to think about that's all OK.

So if you're very interested in the security and kind of the access to the timeline, then it may be who've you to create these research sources at this kind of ad hoc administrative level or importing right, importing information, right? OK, so good questions, right? Rob? So this is essentially entities on steroids.

Not to put too fine a point on it. There are still certainly great use cases for entities. For somebody on the call Amanda, I borrowed this kind of concept from Amanda. You know, I want.

A standalone tab that just has all of my advising notes right in this kind of chronological order, right? We just, you know, kind of wanted to, you know, categorize all this we wanted to kind of have one stop shop. Everybody's here on this. Same on this same custom tab, but what this research does Rob to your point is to say, well, cool, I want to see advising notes, but also the other types of notes and also the other types of notes and also any kind of stacks them on top of each other.

Again, this in a similar display structure or interface to entities to your point, but the beauty is, you know, you can then query kind of across these sources. These research sources in a really robust way using the query tool.

Did you do OK so it's OK, right? Yes, can you map these fields in rent right? I'm looking at their show. Is there a showcase site for student success? Only Roberta. Great question. What we're looking at is this. Is it the challenges this is not yet provision aghbal so you you don't have access to provision this into your clean slate environment. Yet there are still like examples and use cases that I need to build out in this showcase environment. However, in relatively short order, I promise, you know.

You will be able to provision this success only kind of student success. Only showcase environment into your clean slate. Good question but good realm. Take care of privacy on the timeline.

Um?

I don't believe so. Good question Brandy.

I believe the timeline supersedes the aggregate. You know the way that it displays on the timeline might be readonly, right? But they could see if they don't have access to that realm that the that that object is in. There wouldn't be able to see any of the data behind it, but they would still be able to see that a form was submitted on it.

Right and more? Yeah, right. Same kind of thing locked down the form itself by ranting, grow, roll form submission shows up that it happened right? OK, so alright, good good good sorry, just trying to keep up plus one it would be really helpful to totally agree right? And I hear you loud and clear. They were just what often happens. Full disclosure is I get I filled out so many examples and I'm like Oh my gosh but there's something else. And then there's something else. And then there's something else. So I want to make it as robust as possible for when it actually becomes available.

I'll still update it throughout, right? So you can re provision it. Kind of after we kind of go live with it, but there's still. I still want a really, really robust kind of 1st version of it so that you have kind of a one of everything model. So it's coming, I promise.

Um?

So we're going to jump, so that's research, right? I want to make sure it right and Benjamin has a wonderful, wonderful, wonderful feature request in feedback or feedback request. Which kind of allows if you know the feature or the setting on a deliver message right where you can structure hide from timeline.

It would allow that kind of feature. The suggestion is to kind of make that option kind of persist across all things, right? Check off that I want this form hidden from timeline an. I can get that link or Ben if you've got the link handy for sure. Toss that out and an upvote. Upvote it's a. It's a very good idea. OK, cool, OK, sorry, so we're running out of time and you guys like to research, which is awesome.

Let me get back to the.

Custom dashboard queries. OK, fine, so you've got your query library. You've got your research tab. You're rocking and rolling with all these new things insight. Let's talk about something that's existed for a long time inside of Slate, and there are folks that have really taken full advantage of this. But I want you to be able to take advantage of it as well, and I'm going to go through this a little bit quicker. So we've got like 5 minutes for questions as well. So the details? It's a custom display of read only data that's displayed on the record dashboard. It's applicable on any data set.

Record and in other areas. We just saw this kind of dashboard kind of concept is available for the research tab. It's available in the reader. It's available in a couple of different places, right? You can create a multiple dashboard queries and display them on a person's record as well. Use the example for on a persons record dependent on population.

Ultimately, I think the ultimate goal or what's what's constantly being asked is this kind of concept of a one stop shop. How do I create a robust, complex kind of dynamic custom dashboard so that the my end users consume everything that they may need to be interested in visually, right when they get to the person's record? I don't want them clicking into tab into tab, into tab into tab where I don't want them scrolling and clicking and opening other items. I want them to see the 10 things are the five things.

Or the 15 things that are really, really the most important right. This also allows a high level of customization. An Raymond if you're still on the call as well, I will. I will call you out for being one of the Kings of kind of mega tricking out a custom dashboard query and being able to link out to other places and other, you know, embedding links so that you automatically login and pass through parameters to other places. Other records on campus. So it's pretty amazing what you can do OK?

Let's jump in and I want to show you a little bit of what we're talking about.

Because what often happens in what an awful lot of you have asked about, right when? If we're having a conversation you say, wow, cool like I actually really like this advisor snapshot. I like the look of it like can I just have that be in my in my site database, right?

The answer is absolutely yes, right? But where you're ultimately going to navigate? I'm not going to go through the the real basic steps of creating a custom dashboard query, but it is pretty basic, right? It is in the query tool. The thing that a couple of kind of details in the settings when you create it is that you're going to want to make sure that you choose the folder of system and then it's going to prompt you for a system key and you want to say this is a dashboard. I want to call it a dashboard and you're going to. You can ramify it and do which whatever you like, right?

But once you save that up, there are two things that then become rich, two elements that become really important. You're going to build your query. These are the bits of information that you want to be available to display on this dashboard and what we're talking about here is this piece of real estate right? That kind of is right above this biographic information that all of the other information on the dashboard gets pushed down in terms of real estate. When you create out this this custom dashboard query.

It can look different depending on the record that you're looking at, right? So if we bounce over to Alexander Hamilton, he is a person who is an applicant or belongs to a certain population that doesn't dictate him requiring dictate him showing this custom dashboard that looks different than Kendricks, right? Kendrick is in a population where we want this information to show to those users, so it's dependent on population. But note the kind of area of real estate that this is taking up. Kind of this is the custom dashboard query for.

Our applicants and this is the custom dashboard query for our currently enrolled students, right?

Um?

But where, where where the customization comes in is when you edit the query, you're going to want to give them all kind of computer friendly names, because ultimately they become fields that you want to call appan or merge to be able to show and pull the information in OK. So anything that I may be interested in displaying, I want to have exist in this query couple of things to point out, though I may really be interested in having some dynamic.

Or conditional behavior happen. So again, we're talking about these high level visual alerts. I may be interested in.

If there, if anything pops up in this area in tags, I wanted to default to a certain color. So anytime any tag appears, if if the query is is pulling it in, I want it to display as a certain color. Alright, so once you have your query displayed, excuse me. Once you have your query created, you have your.

Your exports in your filters. You want to only show this for for students that have status of enrolled or in a population. You then want to bounce over to the dashboard. So for the folks who say, I just really want to kind of copy and paste exactly what you have, that kind of structure and you might say I don't have the HD, I can't do the HTML of the styling or whatever, but I will really kind of just wanted to look the way yours look so I don't have the same fields to pop in there. I want to customize those, but I really just want to. I want that kind of framework. What you can do is copy and paste.

Literally, this HTML and styling. Where right you can set you know kind of the look of the table, how it's displayed, what, how it wraps you can justify or you can set all the padding margins, all of those details for what it actually looks like and then what you're going to do now to populate each of these boxes. What ultimately these become is you're dictating. Kind of what?

Lives in these particular areas. It's not wildly difficult, relatively intuitive. Once you've got your copy and paste. And again, I know this is for folks that.

You don't, you know, you know I don't have. You know HTML skills beyond kind of like seeing what I'm looking at and consuming and doing a little bit of editing so.

Huh, your each of the boxes are going to kind of live within.

Within the the kind of outline structure, right? And that's where you were going to put in those merge fields that you pulled in via your query, OK?

But I might say, you know for this tags box, so this this box that's displaying text. I want it to default to a color every single time no matter what thing what piece of information pops up in there. So you can call it a specific color to find you know and you can find the hex code or whatever it is Pantone color and insert that into the style Dave to call it a specific color. You can also say I actually there's some information on this dashboard.

That I kind of want to have to change it does it might be red sometimes, but if it's good it might be green, and if it's kind of OK, it might be yellow or orange, right? That kind of red, green, blue. What I would recommend for that?

Is the creation of and hopefully everybody is still with me is the creation of translation codes.

So translation codes are really good way in slate to call some, identify something, then be able to call it something else, right? So for that particular field, cumulative GPA or whatever I dictate, I want to set some minimum and maximum values, and if that integer if that that range is met for that particular field, it's going to default to a color that I set. In this case, that's a color or a red right? And then I want to set another.

Code over here that say, hey, if there's somewhere in this 2.0 range is going to be orange or it's going to be yellow, whatever it is, and then if they're doing OK I want to set this to green. You will then then you. You'll do this kind of. You'll build this out right for each of these types of fields that you want to be dynamic or change color essentially right.

You then actually want to include those translation codes into your query. Alright, so I've got my my export that's pulling my major GPA, but I also have my cumulative GPA font and I'm pulling it in as a translation as an export value, right? And I'm calling it a real. Now I'm choosing the format type so that it recognizes that recognizes it as a real number like I've created the translation codes and corresponds to the color scheme.

So you want to include those various exports in your.

Query what ultimately winds up happening in the source, and again, so this is kind of this is the most technical thing that we're talking about in terms of the subjects today, so I apologize if this is getting a little bit further down into the weeds.

When we're talking about our GPA right? Let's look at it right here. Here's this box where I'm capturing the cumulative GPA. Here's the text. Here's the actual field that's going to pull the number, but then it's also going to call on that translation code to say, well, I'm going to take a look at that number. And depending on what the translation code is, it's going to change color depending on what the value is, right? And you can do that kind of across anything.

Really, anything that you might want to kind of provide this high level of styling and color scheming and changing so that it becomes this really visual high level visual alert right that that may borrow something from just just whatever those visual indicators are from what an advisor or what a faculty member is used to seeing. You can also.

Within that dashboard query, if we go back to our source here when you edit your dashboard, you can insert it, whether it's through the source or right. There you can insert. You could say I want you to go.

To a form I want to link out link you out to a form so you actually don't even have to leave this person's dashboard to be able to submit something about the student. I want to bounce you right over to the earlier alert form so you can have whatever you need without having to click through tabs or really kind of mess around at any other icon inside of inside of the slate database.

2 minutes till I wish I could have spent more time on the customizing dashboard 'cause you can also use a liquid markup and have a lot of conditional displaying of data within this within this real estate. Here if a student is an athlete, I may want to display other pieces of information there, but only if a certain criteria is met. So that's that's a good use case for Liquid markup. And obviously like I said, I've talked too much and I've smashed us right up against the end of the hours. So if there are any questions right?

If you want to vote up for.

Bands feedback post this is fantastic. It's a great idea and it's got a. It's got a lot of good information there. Joy. We did record this. It'll be available probably tomorrow will put it in the article section in the documentation section of student success and it will be a link that's iaccessible out to the recording. I appreciate everybody's time. I love you know interacting with you guys. Can we do this more often? Super helpful. I will do them as much as.

The time allows and as long as you guys keep showing up I will continue to have these conversations. I hope you found it beneficial but but this was great. I love talking you guys love reading the comments. Thank you all and until next time we'll see you later.