224 lines
9.4 KiB
Markdown
224 lines
9.4 KiB
Markdown
# Anthology
|
|
|
|
## 01/26/2023
|
|
|
|
### Content Intro
|
|
|
|
Microsoft Shop - Teams, Word, etc.
|
|
|
|
All are Global Ed Services
|
|
Katie is one team
|
|
KC is another team - this is one of many projects in Global Ed Services
|
|
|
|
KC - Main person
|
|
Mike Highfield - Solutions Architect, Solutions, Learning Ed team
|
|
Aaron Odden - LX architect, works with content creators, Learning Ed team
|
|
Katie Felton - Director for the academies, oversee all content creators & the teams. Ultimately responsible for the strategic direction
|
|
Nicole Melander - Exec Sponsor
|
|
|
|
Met with Patrcyja and got an overview. They still have a lot of questions.
|
|
|
|
* KC is responsible for project plan & the entirety of launch and running. She needs to understand what their team has to deliver.
|
|
* Needs to better understand what is in their subscription model, data tagging, extracts, etc.
|
|
* They have 1558 courses built.
|
|
* Nicole, "as we build courses now, are there things they should be doing differently on Northpass?"
|
|
|
|
Where to start: when they think about their structure of learning, what is the nomenclature and hierarchy of content?
|
|
Content types:
|
|
|
|
* Passive
|
|
* Playlist
|
|
* Videos
|
|
* Active
|
|
* Course (milestones, etc)
|
|
* ILTs and Live Events - both synchronous and asynchronous
|
|
|
|
They don't want to move people from Blackboard learning to Northpass - it doesn't make sense for them to move.
|
|
There is cohort (8-12 weeks) and non-cohort learning.
|
|
MVP Launch, but unsure of what the users and products would be.
|
|
Each product has various
|
|
|
|
This will be a one-stop shop for all knowledge and data.
|
|
|
|
Seven tags per object, course, person, etc.
|
|
|
|
Companies are groups
|
|
|
|
* Inside each company are people, LPs, and Courses
|
|
|
|
Norm to ask KC:
|
|
|
|
* What is a constituent, learner, and global?
|
|
* What is the main group & course structure? Company is the most common.
|
|
* What data needs to be tagged to each object in Northpass? You mentioned 7 tags per object.
|
|
|
|
## 02/16/2023
|
|
|
|
### Data Needs with P,K,A
|
|
|
|
Scoreboards (Encompass)
|
|
Memberships (Encompass)
|
|
Decision Analytics (Encompass)
|
|
|
|
if learner.group contains "(Encompass)":
|
|
add learner to "()" group
|
|
|
|
Student, Encompass, Reach, Finance, HCM <-- Common arrangement or combination of products.
|
|
All enterprise products - ERP, CIS, CRM, and maybe for their alumni association.
|
|
Userbase of reach... which means:
|
|
Reach, Student, Finance at Enterprise level.
|
|
Encompass at Essential
|
|
|
|
KC working on logic to make sure we can know what to design
|
|
Logic is:
|
|
|
|
* Is their domain Anthology.com
|
|
* if no: are they a known subscriber?
|
|
* if no: contact CXM
|
|
|
|
Question from Patrycja - what is the difference between async and sync courses?
|
|
|
|
* Cohort, 8-12 weeks, facilitated by "teachers", and they exist only in Bb academy --> Want to add to Northpass, but not a
|
|
priority.
|
|
* Async, move through it at your own pace.
|
|
|
|
Roles in their current academy:
|
|
|
|
Currently using nested folders for differentiating content based on roles. What they are thinking is
|
|
|
|
## 02/23/2023
|
|
|
|
### Questions from KC
|
|
|
|
As we think about our existing content and products, they are at different states of maturity for the learner experience
|
|
of that product. For example, has the most advanced and cohesive content regarding the product. Student, on the other hand, is all short, micro-learning without a whole bunch of cohesiveness.
|
|
From their perspective of "selling" the academy. As a client, you'll get LPs, ILTs, etc. For student, there won't be any
|
|
courses anytime soon - so how can we sell value with the "resources" library, etc?
|
|
|
|
* Question: can we hide sub navigation links depending on the product/setup? <-- YES!
|
|
* The problem they are looking to solve by this question is when marketing, they say, "your academy has xyz" and then
|
|
client's complain when something isn't available.
|
|
|
|
This will be a similar setup across the entire customer base. Some products will have ILTs, some will have LPs, some
|
|
will have courses and others won't They will need to hide navigation for any non-available course.
|
|
|
|
Question from Mike: KC mentioned the BB side of things. They have a separate instance and they are working on how to get
|
|
that content ready so it is part of the new combined academy. The most useful exercise in the sandbox for him is to
|
|
dummy it.
|
|
|
|
They have "playlist" type courses. 4x videos of 2:15 in length. They want to keep these distinct, and don't use the
|
|
language of "course" because it's not a course. They need a course property boolean to skip overview page; completion
|
|
page, etc.
|
|
|
|
## 04/06/2023
|
|
|
|
DONE: Ask if we can invite KC to their Wistia Project
|
|
DONE: Create ExcelSheet for what Northpass needs to accurately update the SRT file.
|
|
WARN: Wants to start uploading within the week
|
|
|
|
Content Creators will begin again with 1.0 versioning
|
|
Content creators will also be updating content "once in a blue moon" or when the product necessitates it.
|
|
|
|
## 05/24/2023
|
|
|
|
### Implementation Update & Questions
|
|
|
|
Questions:
|
|
|
|
* From last meeting, wanted to discuss LinkedIn Learning. They have an LiL account that all employees have access to.
|
|
How to integrate it into Northpass? Anthology has Enterprise Account.
|
|
* Wilson's Scenario: Learning Path in Northpass for CS agents. In that1, they want to bring in Product training1, and
|
|
also go through a LinkedIn Learning video on "CS fundamentals". He wants it to be "presented" to learners as a
|
|
seamless experience in learning.
|
|
* Manju: can he take LinkedIn Learning analytics into Northpass? No.
|
|
|
|
## 06/29/2023
|
|
|
|
### Random Questions and Tasks
|
|
|
|
DONE: Can "allow retakes" default to yes for all newly created courses?
|
|
|
|
## 07/14/23
|
|
|
|
### Launch Day Nervousness
|
|
|
|
ALl good! It went smoothly.
|
|
|
|
## 08/25/2023
|
|
|
|
### Post Launch Meeting
|
|
|
|
#### Attendees
|
|
|
|
* KC Williams
|
|
* Norm Rasmussen
|
|
|
|
#### Notes
|
|
|
|
* Ideal regular meeting - every week until we are "more finished" and polished.
|
|
* Fridays at 9:30 am EST
|
|
* Is very happy that there's no confirmation email for pre-reg sign ups
|
|
* Two common cases for learners with no course:
|
|
* Users signing up with their Gmail email
|
|
* A random person who isn't part of Anthology, finds their academy, might be interested to learn more, works in
|
|
higher ed, and then signs up. -- This is much smaller of a use case.
|
|
* This could also be for international clients, students, non-english speakers, or just random person in higher ed.
|
|
* If someone else types their email in incorrectly, that's a possible use case.
|
|
* At some point in the future (next FY-July-June) they will have some things published in the catalog.
|
|
* They are months out from that. Courses aren't developed yet.
|
|
* For the edu users that aren't on the list should:
|
|
* Sign up as normal and make it past the first screen
|
|
* Ideally they will not see the Tell us More Screen.
|
|
* However, it's okay if they fill that out and then land on the /app page with the warning.
|
|
* They should NOT see an empty catalog.
|
|
|
|
DONE: Add warning for any personal email addresses entered into field. And make button unclickable.
|
|
|
|
#### Search and Filter Needs
|
|
|
|
* This is priority one. Internally people are asking and external people are complaining.
|
|
* They _need_ search and filtering capability. Right now, it's not really working as they need.
|
|
* UX has asked KC to ask us for strategic advice. They need to look at it not just from how the screens look, but how
|
|
they work too.
|
|
* The original filter screen was removed from the main page cause it was causing confusion.
|
|
* The experience should be that if you filter and then search you will search only WITHIN that filter.
|
|
* Can we not use Ocean Academy to search and then filter?
|
|
DONE: Can we do a "page search" bar that doesn't use Northpass searching? Some library?
|
|
|
|
#### Roles and Content Grouping
|
|
|
|
* They are still thinking through something like an Ocean Academy example of grouping content
|
|
* The roles for using engage will be different than the roles for reach
|
|
* Sysadmin for Engage could be different than Sysadmin for Reach. It may not even be sysadmin - it would be "general
|
|
technology".
|
|
* Student is the "par excellence" where anything goes and all content is mixed.
|
|
* Engage on the other hand has everything planned. They would have 14-15 permutations of different tagging of content.
|
|
* Maybe we lead with a well-organized product.
|
|
|
|
## Other
|
|
|
|
* Amhit will be doing some people and content mapping. There's a QA doc for him to review. He will be doing clean up.
|
|
* Abishek is on his team but unsure of responsibilities.
|
|
|
|
## 09/02/2023
|
|
|
|
### Check in/Standing Meeting
|
|
|
|
#### Notes
|
|
|
|
* KC asked for the icon+product names should be an icon and text.
|
|
* Removed Northpass branding in comms by resetting default content. Marek and Comms team needs to figure out why it's not automatically refreshing.
|
|
* She mentioned that the higher ed user group is crazy pedantic. So if the sender domain isn't Anthology, they will ask if they got hacked.
|
|
* KC interested in using Workato's Outlook node to connect their sender domain via Workato and not just via Comms.
|
|
* They use Comet, currently, as their main email sender/SMTP server.
|
|
* Building off of the search functionality, she wants to build on that. The filter
|
|
and search is the single biggest user experience piece.
|
|
* This is what people complained about in the previous system. She wants to know if
|
|
we can continue to add filter, such as user role.
|
|
* KC to send Norm list of priorities for 2024
|
|
* Full launch by EOCY.
|
|
- [X] Ask Austin to see if we can do the search. It should be more important than Rachel's request.
|
|
- [X] Push search functionality to production
|
|
DONE: Ask Austin to see if we can do the search. It should be more important than Rachel's request.
|
|
DONE: Push search functionality to production
|