Sakai 23.3 - endless list of recent courses

[David Eveland]

Hey there- as long time Sakai users - we’re slowly getting used to the left-hand column navigation for course and in-course navigation. However - our ID teams is struggling - because (as it happens) we navigate hundreds of courses every term and the list of recents grows ever longer.  Is there a way to expunge or reset the recents list?

DAVID N EVELAND 

EXECUTIVE DIRECTOR OF ONLINE EDUCATION

EDS IN HIGHER EDUCATION LEADERSHIP MANAGEMENT

C: 865-274-3225  

O: 865-251-2320  

A: 7900 Johnson Drive Knoxville, TN 37998 

 

 

[Daniel Merino]

Hi David, this can be globally configured in sakai.properties, and the default is only 3.

# Configure the maximum sites to show in the recent sites section of the site navigation
# DEFAULT: 3
# portal.max.recent.sites

But it seems that this setting doesn't work very well without this patch: https://sakaiproject.atlassian.net/browse/SAK-51667

It's weird because I do see three recent sites as maximum in our 25.0 and we haven't applied this patch.

HTH

El 22/1/26 a las 15:56, David Eveland escribió:

-- 
Daniel Merino Echeverría
daniel...@unavarra.es
Gestor de E-learning - Centro Superior de Innovación Educativa.
Tfno: 948-168489 - Universidad Pública de Navarra.

[alan.regan]

Dave, has your institution implemented Delegated Access?

This way, you don't need to enroll people into each class. They can use the Delegated Access process to access the classes they need to work on, etc. Of course, if there are specific sites that someone wants to be listed in (as a roster member), then that's another story.

Our instructional designers and support staff in the past used Delegate Access to save them from manual enrollments into hundreds of sites. It also improved their user experience and reduced system load (we were on Sakai 22 and earlier, so large "Sites" menus ate up resources loading pages, etc.). Plus, folks would receive faculty announcements if enrolled and that wasn't desirable for people just designing or helping sites, etc. Teams would often use a Google Sheet with a list of all the sites for a given to work on, with direct links listed for easy access. The spreadsheets also communicated who was assigned each site and the status... Not Started, In Progress, A11Y Check, Complete, etc.

Now... to reiterate, we used Delegate Access in Sakai 22 and earlier. I am not sure how the tool works in 23 and beyond. I uncluded the Sakai 25 link above, so hopefully it's accurate for the current implementation.

Anyway... just an idea!

-- Alan