- The document discusses proposed changes to the Sakai framework to introduce the concepts of hierarchy between sites and sections (groups) within sites.
- This would allow sites to be connected in parent-child relationships and for permissions and content to flow down the hierarchy. It would also allow additional groups to be created within sites.
- Tools would need to be designed to optimally make use of these new capabilities, either ignoring hierarchy, rolling up/down content, or being fully aware of hierarchy. The framework changes would enable both hierarchy and sections to be implemented before redesigning tools.
Laravel is a powerful PHP web framework that provides tools like authentication, routing, caching and database migration out of the box. It uses an MVC architecture and Eloquent ORM for database access. Key features include its Artisan CLI, resource controllers, routing system and Blade templating engine. Laravel also includes facilities for caching, queues, events and security.
This document summarizes the journey of a library to provide seamless access to electronic resources for on- and off-campus users through integrating Koha, EBSCO Discovery Service (EDS), and OpenAthens. Initially, the library used IP authentication and referring URLs, but saw issues with this approach. The implementation of EDS within Koha helped provide a single search but could not manage all access controls. OpenAthens was then added for centralized single sign-on, with an OAuth2 integration with existing systems like Moodle and Koha's ILS. While challenges remained, the combination of Koha, EDS and OpenAthens through OAuth2 helped achieve the goal of one login for all library
This document discusses using open source applications to support library operations. It begins by debunking myths about open source software, noting that while intermediate computer skills are helpful, advanced skills are not essential. It also states that open source software is not necessarily bug-ridden or difficult to support. The document outlines the top five qualities to look for in open source solutions, including a stable community, solid documentation, recent updates, pathways for feedback, and the ability to try before committing. It then discusses performing a cost-benefit analysis and introduces four specific open source solutions: the Koha integrated library system, SubjectsPlus guides platform, Omeka digital archives and exhibits software, and ResourceSpace digital asset management platform.
A presentation from Leading Edge Libraries Conference, September 22, 2017, hosted by the Florida-Caribbean Chapter of the Special Libraries Association. This presentation covers web-scale discovery solutions and discovery layers,
and summarizes the top five discovery products on the market. The second half presents a case study of implementing EBSCO Discovery Service at Schaff Library at Lancaster Theological Seminary.
Presentation from Leading Edge Libraries Conference, September 22, 2017, hosted by the Florida-Caribbean Chapter of the Special Libraries Association. This presentation introduces OpenAthens, explains how it differs from proxy-based authentication, and presents the adoption and implementation process in a small library.
This document introduces Wei Xia, a computer software professional born in 1982. It summarizes his educational and professional background, including graduating from the University of Electronic Science and Technology of China in 2003 with a bachelor's degree in computer science. It describes his work experience in software development and technical roles at various companies and projects between 2002-2012, including developing websites, an object-relational mapping tool, and cloud computing platforms. It also lists some of his personal interests and hobbies.
Laravel is a powerful PHP web framework that provides tools like authentication, routing, caching and database migration out of the box. It uses an MVC architecture and Eloquent ORM for database access. Key features include its Artisan CLI, resource controllers, routing system and Blade templating engine. Laravel also includes facilities for caching, queues, events and security.
This document summarizes the journey of a library to provide seamless access to electronic resources for on- and off-campus users through integrating Koha, EBSCO Discovery Service (EDS), and OpenAthens. Initially, the library used IP authentication and referring URLs, but saw issues with this approach. The implementation of EDS within Koha helped provide a single search but could not manage all access controls. OpenAthens was then added for centralized single sign-on, with an OAuth2 integration with existing systems like Moodle and Koha's ILS. While challenges remained, the combination of Koha, EDS and OpenAthens through OAuth2 helped achieve the goal of one login for all library
This document discusses using open source applications to support library operations. It begins by debunking myths about open source software, noting that while intermediate computer skills are helpful, advanced skills are not essential. It also states that open source software is not necessarily bug-ridden or difficult to support. The document outlines the top five qualities to look for in open source solutions, including a stable community, solid documentation, recent updates, pathways for feedback, and the ability to try before committing. It then discusses performing a cost-benefit analysis and introduces four specific open source solutions: the Koha integrated library system, SubjectsPlus guides platform, Omeka digital archives and exhibits software, and ResourceSpace digital asset management platform.
A presentation from Leading Edge Libraries Conference, September 22, 2017, hosted by the Florida-Caribbean Chapter of the Special Libraries Association. This presentation covers web-scale discovery solutions and discovery layers,
and summarizes the top five discovery products on the market. The second half presents a case study of implementing EBSCO Discovery Service at Schaff Library at Lancaster Theological Seminary.
Presentation from Leading Edge Libraries Conference, September 22, 2017, hosted by the Florida-Caribbean Chapter of the Special Libraries Association. This presentation introduces OpenAthens, explains how it differs from proxy-based authentication, and presents the adoption and implementation process in a small library.
This document introduces Wei Xia, a computer software professional born in 1982. It summarizes his educational and professional background, including graduating from the University of Electronic Science and Technology of China in 2003 with a bachelor's degree in computer science. It describes his work experience in software development and technical roles at various companies and projects between 2002-2012, including developing websites, an object-relational mapping tool, and cloud computing platforms. It also lists some of his personal interests and hobbies.
Parallel session on 'An Introduction to WAI-ARIA' given by Dan Jackson, City University at the Institutional Web Management Workshop 2009, University of Essex, 28 - 30 July 2009.
See http://iwmw.ukoln.ac.uk/iwmw2009/sessions/jackson/ and
http://lanyrd.com/2009/iwmw09/srfxk/
Cytoscape Tutorial Session 1 at UT-KBRIN Bioinformatics Summit 2014 (4/11/2014)Keiichiro Ono
This document outlines a tutorial on biological data analysis and visualization using Cytoscape. The tutorial covers basic concepts like networks and tables in Cytoscape, data import, network analysis features, and visualization techniques. It discusses loading sample network data, calculating network statistics, filtering networks, basic search functionality, and applying visual styles. The tutorial is intended to provide a practical introduction to Cytoscape's core features through examples and demos.
Lightning Web Components Cairo Salesforce Developers Meetup focused on:
1) The evolution of Salesforce's UI and UI components, specifically comparing Lightning Web Components (LWC) to Aura components and new LWC enhancements in Spring '20.
2) How LWC builds on modern web standards like ES6, Custom Elements, and Shadow DOM for enhanced performance and compatibility.
3) A demonstration of building the first LWC, including the anatomy of an LWC and development tools available.
Rundeck Office Hours: Best Practices for Access Control PoliciesTraciMyers6
This document summarizes a Rundeck community meeting on access control policies. It introduces Nathan Fluegel as the speaker and provides an agenda that includes an introduction to ACL policies, an overview of access control basics, questions from the community, and a demo. It then discusses Rundeck architecture, authorization, and how ACL policies can control access to resources and actions at both the system and project levels. Examples of ACL policies are provided. Recommendations are given around storing policies at the project level and limiting key access. The community Q&A addresses controlling key storage and admin access permissions. Relevant documentation links are also included.
Rundeck Office Hours: Best Practices Access Control PoliciesRundeck
Join us this month for an AMA discussion followed by a live Q&A led by technical experts from Rundeck’s engineering, product, and solution engineering teams. Experts are available to provide advice on your technical architecture, give recommendations for operational best practices, review current Github issues, or dive into the open source code itself.
Don’t miss the opportunity to learn Rundeck product best practices and ask experts your questions about Rundeck.
https://www.rundeck.com/rundeck-office-hours
The document summarizes the history and architecture of Sakai releases. Key points include:
- Sakai 1.0 and 1.5 used an older "monolithic" framework that was improved over time but became difficult to maintain.
- Sakai 2.0 introduced a new Framework II with a re-factored, more modular architecture using Spring and components for improved isolation, flexibility and maintenance.
- Sakai 2.0 focused on integrating new tools like Gradebook and improving existing tools while transitioning to the new framework. More changes are still planned to further improve the architecture.
Oracle 12c framework latest version is out with a bunch of
new exciting features. Thanks to some cutting edge
components and the flexibility of declarative components,
this new version ADF framework increase dramatically the
productivity levels.
This document provides an overview of SharePoint and guidance for working with the platform. It begins with an introduction to SharePoint that outlines its popularity and capabilities. It then covers logical architecture, governance, the paths for different user roles, development tools, debugging techniques, deployment strategies, and the importance of the community for support. Helpful tips are provided throughout for avoiding common pitfalls when working with SharePoint.
Scoring at Scale: Generating Follow Recommendations for Over 690 Million Link...Databricks
The Communities AI team at LinkedIn generates follow recommendations from a large (10’s of millions) set of entities to each of our 690+ million members.
LvivCSS: Web Components as a foundation for Design SystemVlad Fedosov
Let’s see how web components can help us to build accessible, test covered and consistent implementation of our design system that will play well with any technology.
The Recipe for Making Accessible Widgets!Rabab Gomaa
The document provides an overview of making accessible widgets. It discusses the key layers involved, including using semantic HTML, WAI-ARIA roles and attributes, and keyboard interaction. An example of an accessible tabbed interface is used to demonstrate these layers. Design considerations for widgets are also covered, such as using accessible patterns, managing focus, applying the KISS principle, and properly using ARIA roles.
Database Engine Control though Web Portal Monitoring ConfigurationIRJET Journal
This document summarizes a research paper on database engine control through web portal monitoring configuration. It discusses:
1) Splitting development between a database engine layer implementing business logic and a presentation layer implementing user interfaces, allowing independent and faster development.
2) The proposed system architecture with a presentation layer, business layer, and database layer communicating with a SQL server database.
3) How the automated system will help management access fees details, student addresses, balances and other data in real-time, reducing costs and increasing productivity compared to a manual system.
The document is a slide presentation on Software Defined Networking (SDN) and the SDN control plane. It discusses key characteristics of the SDN architecture including flow-based forwarding, separation of the control and data planes, externalization of control functions, and a programmable network. It describes the main components of the SDN control plane including the SDN controller, network control applications, and protocols like OpenFlow. The SDN controller maintains network-wide state and interacts with control applications and switches using northbound and southbound APIs respectively.
This document discusses web application frameworks and principles. It outlines desired characteristics for web frameworks, including database mapping, request routing, view selection, component-based asynchronous rendering, security, testing, and deployment. Specific frameworks mentioned that exemplify some principles include Rails, Seaside, and Lift. The document also provides information about getting started with Lift and development tools for Lift.
1) The summary discusses a Friday session notes document that outlines an agenda including a discussion on Sakai 3 and why it is happening now from 9:30-10:30am and closing remarks at 3:15pm.
2) It also provides room location notes for where various sessions will take place.
3) The document then goes into details on the goals and new features of Sakai 3 from a user, technology and community perspective focusing on improved content management, academic networking and workflows across tools.
1) The summary discusses a Friday session notes document covering topics from 9:30-10:30am including a discussion on College of the Redwoods' Sakai deployment and closing remarks at 3:15pm.
2) It provides room location notes for the Empress room on the 14th floor and Charles View room on the 16th floor.
3) The document discusses reasons for Sakai 3 including functionality and user experience improvements, using new technologies, and adapting to changing community practices and culture.
Accessibility of HTML5 and Rich Internet Applications - CSUN 2012Steven Faulkner
This document summarizes a presentation on the accessibility of HTML5 and rich internet applications. It discusses how ARIA roles, properties, and live regions can be used to make dynamic and interactive content accessible. It provides examples of how to make buttons, trees, grids, forms, dialogs, and live regions accessible. It emphasizes proper labeling, keyboard support, and ways to handle updates and alerts.
The document discusses various techniques for managing performance and concurrency in SQL Server databases. It covers new features in SQL Server 2008/R2 such as read committed snapshot isolation, partition-level lock escalation, filtered indexes, and bulk loading. It also discusses tools for monitoring performance like the Utility Control Point and Performance Monitor. The document uses case studies to demonstrate how these techniques can be applied.
Next-Generation Completeness and Consistency Management in the Digital Threa...Ákos Horváth
The document discusses challenges in maintaining consistency, completeness, and correctness (3C) across disconnected engineering data silos. It proposes using links and transformations to connect models between systems engineering and electrical design tools. Validation rules can then check that connections and components are properly mapped between the silos. The IncQuery Validator was used to import a model from E3.GENESYS into its knowledge graph and generate a validation report checking for 3C issues. Tracking link management and validation results over time provides visibility into the progress of the "digital thread" across the engineering lifecycle.
LTI Advantage: The Next Big Thing in LMS IntegrationCharles Severance
LTI Advantage is the next major integration standard for learning management systems (LMS). It uses new technologies like JSON Web Tokens (JWTs) and public/private key infrastructure (PKI) to securely launch tools and access user data and grading services. The presentation provides an overview of the LTI Advantage specification and code samples for implementing launches, user authorization, and accessing LMS services using libraries available in Java. While adoption of LTI Advantage promises tighter integration between LMSs and external tools, there are also transition challenges as vendors continue to evolve their systems.
Tsugi and Koseu are open source software tools that allow anyone to easily build and deploy standards-compliant educational websites, content, and learning applications.
Tsugi acts as an "app store" that hosts learning applications and provides API libraries for developers to integrate their tools using open standards. Koseu is an educational website builder and content hosting platform, providing a simple "LMS-like" environment.
These tools aim to lower the barrier to developing and using interoperable educational technologies, helping train developers and allowing institutions and individuals to quickly create customized learning solutions.
More Related Content
Similar to Sakai Hierarchy Framework Changes Overview (not implemented)
Parallel session on 'An Introduction to WAI-ARIA' given by Dan Jackson, City University at the Institutional Web Management Workshop 2009, University of Essex, 28 - 30 July 2009.
See http://iwmw.ukoln.ac.uk/iwmw2009/sessions/jackson/ and
http://lanyrd.com/2009/iwmw09/srfxk/
Cytoscape Tutorial Session 1 at UT-KBRIN Bioinformatics Summit 2014 (4/11/2014)Keiichiro Ono
This document outlines a tutorial on biological data analysis and visualization using Cytoscape. The tutorial covers basic concepts like networks and tables in Cytoscape, data import, network analysis features, and visualization techniques. It discusses loading sample network data, calculating network statistics, filtering networks, basic search functionality, and applying visual styles. The tutorial is intended to provide a practical introduction to Cytoscape's core features through examples and demos.
Lightning Web Components Cairo Salesforce Developers Meetup focused on:
1) The evolution of Salesforce's UI and UI components, specifically comparing Lightning Web Components (LWC) to Aura components and new LWC enhancements in Spring '20.
2) How LWC builds on modern web standards like ES6, Custom Elements, and Shadow DOM for enhanced performance and compatibility.
3) A demonstration of building the first LWC, including the anatomy of an LWC and development tools available.
Rundeck Office Hours: Best Practices for Access Control PoliciesTraciMyers6
This document summarizes a Rundeck community meeting on access control policies. It introduces Nathan Fluegel as the speaker and provides an agenda that includes an introduction to ACL policies, an overview of access control basics, questions from the community, and a demo. It then discusses Rundeck architecture, authorization, and how ACL policies can control access to resources and actions at both the system and project levels. Examples of ACL policies are provided. Recommendations are given around storing policies at the project level and limiting key access. The community Q&A addresses controlling key storage and admin access permissions. Relevant documentation links are also included.
Rundeck Office Hours: Best Practices Access Control PoliciesRundeck
Join us this month for an AMA discussion followed by a live Q&A led by technical experts from Rundeck’s engineering, product, and solution engineering teams. Experts are available to provide advice on your technical architecture, give recommendations for operational best practices, review current Github issues, or dive into the open source code itself.
Don’t miss the opportunity to learn Rundeck product best practices and ask experts your questions about Rundeck.
https://www.rundeck.com/rundeck-office-hours
The document summarizes the history and architecture of Sakai releases. Key points include:
- Sakai 1.0 and 1.5 used an older "monolithic" framework that was improved over time but became difficult to maintain.
- Sakai 2.0 introduced a new Framework II with a re-factored, more modular architecture using Spring and components for improved isolation, flexibility and maintenance.
- Sakai 2.0 focused on integrating new tools like Gradebook and improving existing tools while transitioning to the new framework. More changes are still planned to further improve the architecture.
Oracle 12c framework latest version is out with a bunch of
new exciting features. Thanks to some cutting edge
components and the flexibility of declarative components,
this new version ADF framework increase dramatically the
productivity levels.
This document provides an overview of SharePoint and guidance for working with the platform. It begins with an introduction to SharePoint that outlines its popularity and capabilities. It then covers logical architecture, governance, the paths for different user roles, development tools, debugging techniques, deployment strategies, and the importance of the community for support. Helpful tips are provided throughout for avoiding common pitfalls when working with SharePoint.
Scoring at Scale: Generating Follow Recommendations for Over 690 Million Link...Databricks
The Communities AI team at LinkedIn generates follow recommendations from a large (10’s of millions) set of entities to each of our 690+ million members.
LvivCSS: Web Components as a foundation for Design SystemVlad Fedosov
Let’s see how web components can help us to build accessible, test covered and consistent implementation of our design system that will play well with any technology.
The Recipe for Making Accessible Widgets!Rabab Gomaa
The document provides an overview of making accessible widgets. It discusses the key layers involved, including using semantic HTML, WAI-ARIA roles and attributes, and keyboard interaction. An example of an accessible tabbed interface is used to demonstrate these layers. Design considerations for widgets are also covered, such as using accessible patterns, managing focus, applying the KISS principle, and properly using ARIA roles.
Database Engine Control though Web Portal Monitoring ConfigurationIRJET Journal
This document summarizes a research paper on database engine control through web portal monitoring configuration. It discusses:
1) Splitting development between a database engine layer implementing business logic and a presentation layer implementing user interfaces, allowing independent and faster development.
2) The proposed system architecture with a presentation layer, business layer, and database layer communicating with a SQL server database.
3) How the automated system will help management access fees details, student addresses, balances and other data in real-time, reducing costs and increasing productivity compared to a manual system.
The document is a slide presentation on Software Defined Networking (SDN) and the SDN control plane. It discusses key characteristics of the SDN architecture including flow-based forwarding, separation of the control and data planes, externalization of control functions, and a programmable network. It describes the main components of the SDN control plane including the SDN controller, network control applications, and protocols like OpenFlow. The SDN controller maintains network-wide state and interacts with control applications and switches using northbound and southbound APIs respectively.
This document discusses web application frameworks and principles. It outlines desired characteristics for web frameworks, including database mapping, request routing, view selection, component-based asynchronous rendering, security, testing, and deployment. Specific frameworks mentioned that exemplify some principles include Rails, Seaside, and Lift. The document also provides information about getting started with Lift and development tools for Lift.
1) The summary discusses a Friday session notes document that outlines an agenda including a discussion on Sakai 3 and why it is happening now from 9:30-10:30am and closing remarks at 3:15pm.
2) It also provides room location notes for where various sessions will take place.
3) The document then goes into details on the goals and new features of Sakai 3 from a user, technology and community perspective focusing on improved content management, academic networking and workflows across tools.
1) The summary discusses a Friday session notes document covering topics from 9:30-10:30am including a discussion on College of the Redwoods' Sakai deployment and closing remarks at 3:15pm.
2) It provides room location notes for the Empress room on the 14th floor and Charles View room on the 16th floor.
3) The document discusses reasons for Sakai 3 including functionality and user experience improvements, using new technologies, and adapting to changing community practices and culture.
Accessibility of HTML5 and Rich Internet Applications - CSUN 2012Steven Faulkner
This document summarizes a presentation on the accessibility of HTML5 and rich internet applications. It discusses how ARIA roles, properties, and live regions can be used to make dynamic and interactive content accessible. It provides examples of how to make buttons, trees, grids, forms, dialogs, and live regions accessible. It emphasizes proper labeling, keyboard support, and ways to handle updates and alerts.
The document discusses various techniques for managing performance and concurrency in SQL Server databases. It covers new features in SQL Server 2008/R2 such as read committed snapshot isolation, partition-level lock escalation, filtered indexes, and bulk loading. It also discusses tools for monitoring performance like the Utility Control Point and Performance Monitor. The document uses case studies to demonstrate how these techniques can be applied.
Next-Generation Completeness and Consistency Management in the Digital Threa...Ákos Horváth
The document discusses challenges in maintaining consistency, completeness, and correctness (3C) across disconnected engineering data silos. It proposes using links and transformations to connect models between systems engineering and electrical design tools. Validation rules can then check that connections and components are properly mapped between the silos. The IncQuery Validator was used to import a model from E3.GENESYS into its knowledge graph and generate a validation report checking for 3C issues. Tracking link management and validation results over time provides visibility into the progress of the "digital thread" across the engineering lifecycle.
Similar to Sakai Hierarchy Framework Changes Overview (not implemented) (20)
LTI Advantage: The Next Big Thing in LMS IntegrationCharles Severance
LTI Advantage is the next major integration standard for learning management systems (LMS). It uses new technologies like JSON Web Tokens (JWTs) and public/private key infrastructure (PKI) to securely launch tools and access user data and grading services. The presentation provides an overview of the LTI Advantage specification and code samples for implementing launches, user authorization, and accessing LMS services using libraries available in Java. While adoption of LTI Advantage promises tighter integration between LMSs and external tools, there are also transition challenges as vendors continue to evolve their systems.
Tsugi and Koseu are open source software tools that allow anyone to easily build and deploy standards-compliant educational websites, content, and learning applications.
Tsugi acts as an "app store" that hosts learning applications and provides API libraries for developers to integrate their tools using open standards. Koseu is an educational website builder and content hosting platform, providing a simple "LMS-like" environment.
These tools aim to lower the barrier to developing and using interoperable educational technologies, helping train developers and allowing institutions and individuals to quickly create customized learning solutions.
Exploring the Next Generation Digital Learning Environment with TsugiCharles Severance
Tsugi is a next generation digital learning environment that allows for an educational app store and interoperability between different learning tools and content repositories. It fills gaps between existing standards like IMS Learning Tools Interoperability and IMS Common Cartridge. For the first time, an app store or learning object repository can be created without proprietary extensions. Tsugi aims to make educational technology startups and tools that teach easier to build, enrich open educational content, and allow for seamless integration and reuse of content across different systems through open standards.
CloudSocial: A New Approach to Enabling Open Content for Broad ReuseCharles Severance
This document summarizes several projects related to open educational resources and learning management systems. It discusses the CloudSocial project, which aims to enable tools from any learning system to be embedded in open web content. It also mentions the University of Michigan Medical School's efforts to develop a next generation LMS beyond traditional course-based systems. Finally, it introduces CloudCollab, an open source LMS written in Python that intends to implement IMS standards and allow hosting tool instances for multiple organizations.
The document discusses the next generation of digital learning environments (NGDLE). It argues that the NGDLE will not be a single application like current learning management systems, but rather an ecosystem of learning applications from an app store. Standards like IMS Learning Tools Interoperability (LTI) and the emerging IMS Content Item and CASA App Store specifications will allow learning applications from different vendors to integrate and interoperate within the NGDLE ecosystem. The NGDLE is predicted to have over 100,000 learning applications accessible to teachers and students.
This was my presentation at "Jornada TELSpain: "eLearning 2020: empresas y universidades"
http://symposium.uoc.edu/event_detail/3133/detail/jornada-telspain.html
The document summarizes how universities are using MOOCs (Massive Open Online Courses) to reimagine teaching and learning. It provides examples of positive results from MOOC programs at the University of Michigan and Coursera. Enrollment numbers and revenue from Coursera courses are increasing significantly each year. MOOCs allow universities to offer educational opportunities to millions of students worldwide at low or no cost.
Charles Severance discusses the future of Sakai and next generation teaching and learning systems. Key points include:
1) Sakai-11 will have an improved, more flexible user interface and improved lessons tool. It will move to a continuous upgrade model and improve multi-tenancy.
2) Standards adoption is increasing and Sakai scores well compared to other learning management systems.
3) Next generation teaching and learning systems will have small modular learning management systems with features from abundant app stores and content repositories. This will allow scaling from hundreds to millions of students.
The document discusses the next generation of teaching and learning tools beyond traditional learning management systems (LMS). It outlines some of the key tenets of next generation tools, including being smaller and scalable, relying on external app stores and content repositories, and having more powerful authoring capabilities. Some early examples in this emerging space are mentioned, focusing on repositories, app stores, and platforms that combine small LMS functionality with external apps and content. Standards alignment is also discussed as important for next generation tools. The document concludes by suggesting how open source projects like Sakai could ensure survival by embracing these next generation approaches.
The document summarizes the history of learning management systems (LMS) in three acts based on a three-act story structure. Act 1 describes the early days of individual LMS vendors. Act 2 covers the period of rapid adoption and growth of many LMS vendors during the "gold rush". Standards organizations like IMS began working on interoperability standards to connect different systems. Act 3 suggests the LMS market is shifting towards a more open, interoperable "post-LMS" ecosystem driven by external tools and empowering teachers through standards.
1. Tsugi is a tool hosting framework that allows LTI tools to be installed and run within its PHP or Java-based container.
2. It emulates Moodle APIs and provides a multi-tenant environment for tools while keeping user data secure.
3. The framework supports LTI 1.x and 2.x specifications and can integrate other IMS standards like Caliper and CASA to host tools from an app store or custom sources.
Charles Severance discussed the history and updates of open standards for learning tools interoperability. He covered the development of LTI versions 1.0, 1.1, 2.0, and upcoming versions 2.1 and 2.2. LTI aims to allow learning tools from different providers to integrate securely with learning management systems. Version 2.0 introduced a RESTful architecture using JSON and registration of tools to share capabilities. Version 2.1 will add re-registration capabilities. Common Cartridge and Caliper analytics standards also relate to advancing open interoperability.
I gave this talk about the state of Sakai at Apereo15. It featured a kitty video.
http://lanyrd.com/2015/apereo/sdmmmq/
https://www.youtube.com/watch?v=MbcKGYUsCTU
The Trials and Tribulations of Predicting the Future of Educational TechnologyCharles Severance
This is a talk I gave the 2015 LAK15 conference in Poughkeepsie, NY
http://lak15.solaresearch.org/
There is an associated video that is not inluded and not available anywhere. I did not have permission to use the video so I only showed it during my live presentation.
International NCSC ONE Conference 2015
14-April-2015
https://youtu.be/27rFAcUSKSc?t=7h13m6s
https://www.ncsc.nl/english/conference/programme/day-2.html
This presentation was provided by Racquel Jemison, Ph.D., Christina MacLaughlin, Ph.D., and Paulomi Majumder. Ph.D., all of the American Chemical Society, for the second session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session Two: 'Expanding Pathways to Publishing Careers,' was held June 13, 2024.
Level 3 NCEA - NZ: A Nation In the Making 1872 - 1900 SML.pptHenry Hollis
The History of NZ 1870-1900.
Making of a Nation.
From the NZ Wars to Liberals,
Richard Seddon, George Grey,
Social Laboratory, New Zealand,
Confiscations, Kotahitanga, Kingitanga, Parliament, Suffrage, Repudiation, Economic Change, Agriculture, Gold Mining, Timber, Flax, Sheep, Dairying,
Chapter wise All Notes of First year Basic Civil Engineering.pptxDenish Jangid
Chapter wise All Notes of First year Basic Civil Engineering
Syllabus
Chapter-1
Introduction to objective, scope and outcome the subject
Chapter 2
Introduction: Scope and Specialization of Civil Engineering, Role of civil Engineer in Society, Impact of infrastructural development on economy of country.
Chapter 3
Surveying: Object Principles & Types of Surveying; Site Plans, Plans & Maps; Scales & Unit of different Measurements.
Linear Measurements: Instruments used. Linear Measurement by Tape, Ranging out Survey Lines and overcoming Obstructions; Measurements on sloping ground; Tape corrections, conventional symbols. Angular Measurements: Instruments used; Introduction to Compass Surveying, Bearings and Longitude & Latitude of a Line, Introduction to total station.
Levelling: Instrument used Object of levelling, Methods of levelling in brief, and Contour maps.
Chapter 4
Buildings: Selection of site for Buildings, Layout of Building Plan, Types of buildings, Plinth area, carpet area, floor space index, Introduction to building byelaws, concept of sun light & ventilation. Components of Buildings & their functions, Basic concept of R.C.C., Introduction to types of foundation
Chapter 5
Transportation: Introduction to Transportation Engineering; Traffic and Road Safety: Types and Characteristics of Various Modes of Transportation; Various Road Traffic Signs, Causes of Accidents and Road Safety Measures.
Chapter 6
Environmental Engineering: Environmental Pollution, Environmental Acts and Regulations, Functional Concepts of Ecology, Basics of Species, Biodiversity, Ecosystem, Hydrological Cycle; Chemical Cycles: Carbon, Nitrogen & Phosphorus; Energy Flow in Ecosystems.
Water Pollution: Water Quality standards, Introduction to Treatment & Disposal of Waste Water. Reuse and Saving of Water, Rain Water Harvesting. Solid Waste Management: Classification of Solid Waste, Collection, Transportation and Disposal of Solid. Recycling of Solid Waste: Energy Recovery, Sanitary Landfill, On-Site Sanitation. Air & Noise Pollution: Primary and Secondary air pollutants, Harmful effects of Air Pollution, Control of Air Pollution. . Noise Pollution Harmful Effects of noise pollution, control of noise pollution, Global warming & Climate Change, Ozone depletion, Greenhouse effect
Text Books:
1. Palancharmy, Basic Civil Engineering, McGraw Hill publishers.
2. Satheesh Gopi, Basic Civil Engineering, Pearson Publishers.
3. Ketki Rangwala Dalal, Essentials of Civil Engineering, Charotar Publishing House.
4. BCP, Surveying volume 1
Temple of Asclepius in Thrace. Excavation resultsKrassimira Luka
The temple and the sanctuary around were dedicated to Asklepios Zmidrenus. This name has been known since 1875 when an inscription dedicated to him was discovered in Rome. The inscription is dated in 227 AD and was left by soldiers originating from the city of Philippopolis (modern Plovdiv).
Leveraging Generative AI to Drive Nonprofit InnovationTechSoup
In this webinar, participants learned how to utilize Generative AI to streamline operations and elevate member engagement. Amazon Web Service experts provided a customer specific use cases and dived into low/no-code tools that are quick and easy to deploy through Amazon Web Service (AWS.)
Philippine Edukasyong Pantahanan at Pangkabuhayan (EPP) CurriculumMJDuyan
(𝐓𝐋𝐄 𝟏𝟎𝟎) (𝐋𝐞𝐬𝐬𝐨𝐧 𝟏)-𝐏𝐫𝐞𝐥𝐢𝐦𝐬
𝐃𝐢𝐬𝐜𝐮𝐬𝐬 𝐭𝐡𝐞 𝐄𝐏𝐏 𝐂𝐮𝐫𝐫𝐢𝐜𝐮𝐥𝐮𝐦 𝐢𝐧 𝐭𝐡𝐞 𝐏𝐡𝐢𝐥𝐢𝐩𝐩𝐢𝐧𝐞𝐬:
- Understand the goals and objectives of the Edukasyong Pantahanan at Pangkabuhayan (EPP) curriculum, recognizing its importance in fostering practical life skills and values among students. Students will also be able to identify the key components and subjects covered, such as agriculture, home economics, industrial arts, and information and communication technology.
𝐄𝐱𝐩𝐥𝐚𝐢𝐧 𝐭𝐡𝐞 𝐍𝐚𝐭𝐮𝐫𝐞 𝐚𝐧𝐝 𝐒𝐜𝐨𝐩𝐞 𝐨𝐟 𝐚𝐧 𝐄𝐧𝐭𝐫𝐞𝐩𝐫𝐞𝐧𝐞𝐮𝐫:
-Define entrepreneurship, distinguishing it from general business activities by emphasizing its focus on innovation, risk-taking, and value creation. Students will describe the characteristics and traits of successful entrepreneurs, including their roles and responsibilities, and discuss the broader economic and social impacts of entrepreneurial activities on both local and global scales.
🔥🔥🔥🔥🔥🔥🔥🔥🔥
إضغ بين إيديكم من أقوى الملازم التي صممتها
ملزمة تشريح الجهاز الهيكلي (نظري 3)
💀💀💀💀💀💀💀💀💀💀
تتميز هذهِ الملزمة بعِدة مُميزات :
1- مُترجمة ترجمة تُناسب جميع المستويات
2- تحتوي على 78 رسم توضيحي لكل كلمة موجودة بالملزمة (لكل كلمة !!!!)
#فهم_ماكو_درخ
3- دقة الكتابة والصور عالية جداً جداً جداً
4- هُنالك بعض المعلومات تم توضيحها بشكل تفصيلي جداً (تُعتبر لدى الطالب أو الطالبة بإنها معلومات مُبهمة ومع ذلك تم توضيح هذهِ المعلومات المُبهمة بشكل تفصيلي جداً
5- الملزمة تشرح نفسها ب نفسها بس تكلك تعال اقراني
6- تحتوي الملزمة في اول سلايد على خارطة تتضمن جميع تفرُعات معلومات الجهاز الهيكلي المذكورة في هذهِ الملزمة
واخيراً هذهِ الملزمة حلالٌ عليكم وإتمنى منكم إن تدعولي بالخير والصحة والعافية فقط
كل التوفيق زملائي وزميلاتي ، زميلكم محمد الذهبي 💊💊
🔥🔥🔥🔥🔥🔥🔥🔥🔥
Elevate Your Nonprofit's Online Presence_ A Guide to Effective SEO Strategies...TechSoup
Whether you're new to SEO or looking to refine your existing strategies, this webinar will provide you with actionable insights and practical tips to elevate your nonprofit's online presence.
This document provides an overview of wound healing, its functions, stages, mechanisms, factors affecting it, and complications.
A wound is a break in the integrity of the skin or tissues, which may be associated with disruption of the structure and function.
Healing is the body’s response to injury in an attempt to restore normal structure and functions.
Healing can occur in two ways: Regeneration and Repair
There are 4 phases of wound healing: hemostasis, inflammation, proliferation, and remodeling. This document also describes the mechanism of wound healing. Factors that affect healing include infection, uncontrolled diabetes, poor nutrition, age, anemia, the presence of foreign bodies, etc.
Complications of wound healing like infection, hyperpigmentation of scar, contractures, and keloid formation.
3. Comparison
• Sections are additional groups/rosters
*within* a Sakai site
• Hierarchy is the relationship between
sites, and can be used to describe the
relationship between other entities in
the Sakai system (sites, files, folders)
4. Tool Impact on Hierarchy
• Like Sections, tools can be written which are
completely unaware of hierarchy - these tools
simply operate in a “Site” and effectively
ignore any parent, child, or other sites.
– Content/Resources - Likely to be very aware and
affected greatly by hierarchy
– Chat tool will probably ignore hierarchy
• Deciding how to use/present hierarchy is a
decision left up to the the tool designer.
5. What is a “Site”?
• It is “one tab” across the top of the Sakai GUI
• It is a set of pages and tools which operate
“together” in a context.
• The concept of a site does not change across
these framework improvements
• However Sites become more capable and
flexible as these new framework capabilities
are added.
6. Sakai Site - 2.0
Site: EECS280
Roster
Tool List
Chat
Info
…
The roster (realm) contains both membership and permission
information. The roster can be fed externally or internally.
Message
Folder
File
File
Annc
7. Sakai Site - 2.1 - Sections
Site: EECS280
Roster
Tool List
Chat
Info
…
We add sub-rosters or Sections. Some of the entities/objects/tools will
be changed to set permissions and reflect sections as part of their
security. Other entities will not be section aware in 2.1 and their
security will be determined by the Roster/Realm for the whole site.
Message
Folder
File
File
Sec A Sec B
Annc
8. Sakai Site - Hierarchy
Hierarchy allows sites to become “connected” in various parent and
child relationships. Permission and inheritance can flow down the
hierarchy depending on the configuration of the site’s relationship with
its parent.
Site: EECS280
Rr
Tool
Chat
Info
…
Sec Sec
Site: EECS220
Rr
Tool
Chat
Info
…
Site: EECS240
Rr
Tool
Chat
Info
…
Site: Computer Science
Rr
Tool
Chat
Info
…
Site: EECS240-LEC 1
Rr
Tool
Chat
Info
…
Site: EECS240-LEC 2
Rr
Tool
Chat
Info
…
9. Possible Tool Changes
• Each tool must be carefully designed as
to how it will be affected by hierarchy
• Several approaches for a tool
– Ignore Hierarchy (Chat tool)
– Roll - up or down objects below based on
some configuration of the tool (Schedule)
– Make tool fully aware of hierarchy - make
hierarchy an implicit part of the tool
(Resources)
10. Hierarchy in the Portal
QuickTime™ and a
TIFF (Uncompressed) decompressor
are needed to see this picture.
Sites
EECS280
.. Up to Computer Science
EECS280-LEC1
EEGS280-LEC2
EECS280-LEC1 EECS280-LEC2
11. Rolling up Hierarchy in a Tool
QuickTime™ and a
TIFF (Uncompressed) decompressor
are needed to see this picture.
Schedule
EECS280
Include schedule items
from sub-sites in schedule
All sub-sites
Depth
EECS280-LEC1 EECS280-LEC2
Options
2
12. Implicit Hierarchy in a Tool
QuickTime™ and a
TIFF (Uncompressed) decompressor
are needed to see this picture.
Resources
EECS280
Syllabus (folder)
Properties | Add Item | Delete
Images (folder)
Properties | Add Item | Delete
xyz.ppt
Properties | Add Item | Delete
EECS280-LEC1 (Sub Site)
Properties | Add Item | Delete
EECH280-LEC2
Properties | Add Item | Delete
Other Sites
Search Repositories
EECS280-LEC1 EECS280-LEC2
13. Summary
• SubSites (Hierarchy) and Sections (Groups) are
complimentary notions
• The Sakai framework Authorization, and Site APIs
will support both hierarchy between sites and
grouping within sites
• Tool modifications will need to be designed to make
ideal use of these capabilities from an end-user
perspective.
• It would probably be a good idea to make the
framework changes for both hierarchy and sections
and then redesign the tools once - considering both
issues at the same time.
27. Looking for C93
SAKAI_GRANTS
Grantee Function
or F-Set
Node or
Entity
Blockable
A99 content.
read
C93 Yes
G50/TA maintain N17 Yes
G50 access N20 Yes
G40 maintain N20 No
G86 access N15 Yes
CONTENT_ENTITY
GUID Node
C94 N17
C94 N22
C95 N29
C93 N23
SAKAI_INHERIT
Child Parent Block
N20 N15 B
N17 N20 B
N17 N15 B
N22 N20 N
N22 N15 B
N29 N22 N
N29 N20 N
N29 N15 B
N23 N22 B
N23 N20 B
N23 N15 B
28. Looking for C94
SAKAI_GRANTS
Grantee Function
or F-Set
Node or
Entity
Blockable
A99 content.
read
C93 Yes
G50/TA maintain N17 Yes
G50 access N20 Yes
G40 maintain N20 No
G86 access N15 Yes
CONTENT_ENTITY
GUID Node
C94 N17
C94 N22
C95 N29
C93 N23
SAKAI_INHERIT
Child Parent Block
N20 N15 B
N17 N20 B
N17 N15 B
N22 N20 N
N22 N15 B
N29 N22 N
N29 N20 N
N29 N15 B
N23 N22 B
N23 N20 B
N23 N15 B
Editor's Notes
This document describes and expands up the notion of Sakai Section/Sub Group Awareness and is expected to be the following work once sections are fully supported in the framework.
We are adding hierarchy to the framework - to decide how each framework capability is used in each tool is up to the designers of the tools over time as each tool is considered.
Over time, tools will be redesigned and decisions will be made w.r.t. Whether or not the tool is to be section aware.
In this example, EECS220 is a single site, EECS280 is a single site with multiple sections and EECS240 has two sub-sites. All three of the main sites are sub-sites within the Computer Science site.
This document does not purport to design any tool changes - this document only show what tool changes are possible given the anticipated framework changes.
It will be up to the designers of each tool to decide how or if they want to adapt the tool in the presence of hierarchy.
You will see the sites you have access to will appear in the navigation bar regardless of their position in the hierarchy - the portal will simply look across all sites and ask the AUTHZ question - “which sites does the current use have the ability to visit?”
In a tool like Schedule we may choose to provide options as to whether the display will include readable items from sub-sites - perhaps there will be a user selectable depth and possibly an option to look all the way down the tree of sub sites for readable schedule items.
A tool like Resourses naturally displays a tree of information. The Resources area for each sub-sites appears as a folder in the site. The user naturally navigates up and down the tree. By entering the sub-site content folder, it does not mean that the users has “switched sites” (I.e. tool bar will not change to reflect the sub site tool configurations) - it simply means the the resource tool associated with this placement is looking at the resources in the sub site.
Now we switch gears from what is required GUI-wise and how course management API is related to the framework, we will look at how the framework will work.
Objects like Announcement or Calendar entries are stored and owned by their Manager (Service). Each tool placement within a site knows which site it is part of - this is the “context” of that placement. When the tool is executing in a context, the current context value.
Each object (like an announcement) records which site/context it is part of. When the service is looking up the announcements for a site, it uses these context indicator to gather up the announcements associated with the site indicated in the context.
Each Site/Context has an associated Realm where there are users granted permission sets (access or maintain) which represent a set of basic application permissions (annc.read, sched.write, etc.)
As each announcement (A1, A2) is read, the permission to do so is checked using a realm which is directly associated with each site.
The Context (N20) will be separated from the Site (S15). The Site (tools, placements, configurations) is just one object associated with the context/Node. The Context is simply a node in the hierarchy. If this context has a site, it will be associated to the the context. The arrow directions indicate that it is the Site’s responsibility to store its association with the node. The “current site” is the site object that is associated with the current Node/Context.
The replacement for “Realm” is a set of grants to the context. A grant can be done from an individual, group, or group/role combination. In the above example “G50/Learner” is members of group G50 with the “Learner” role and this set is being granted the “access” permission set. A permission set is simply a nice handle for a set of low level atomic permissions. In OSID terms, this would be “function set” and “functions”.
A key aspect of permission sets is that they are contextualized by contextNode (I.e. the “access” set is different for each Context). The site maintainer can make new permission sets. It is also possible to grant an individual permission/function in addition to a permission/function set.
The site’s context node lives in a hierarchy. In this example, Node N20 has three children (N17, N18, N19). This is a configuration where there is one course site, and three “sub-contexts”. There are three sections/groups associated with the course (G50, G51, G52). In the course the instructor group (G49) has maintain and the others have “access”. Each sub context is set up to serve one of the sections. N17 grants maintain to the instructor group (G49) and maintain to the TA’s in G50 and access permission of the Learners in G50.
Note that there is no access control inheritance between nodes (indicated by the circle with the “X” in it) - so the instructor group is granted maintain permission in each of the sub-contexts (N17, N18, N19). Also note that the TA role is granted maintain in each of the sub-contexts while they were granted access permission in N20 (the course site). Because the entire group G50
So far, all of the node to node links have blocked inheritance because we have needed to give less power at a child node than at a parent node. Node N17 is an example of this. Note that because inheritance is blocked, we had to copy the G49 (instructor) grant to node N17.
If we allow a node to be a folder, we can add some file Entities (C91 and C92) as children of N20. Like any other entity, we can add fine-grained authorization such as allowing C91 to be publicly viewable.
Since N22 is not blocked, it inherits the grants from N20. Similarly C92 inherits permissions from N20. C94, N21, and C95 all inherit from N17 (but not N20 because of the block).
N23 is blocked from inheriting from N22 (or N20), so we copy the G49 (instructor group) maintain permission down. Below N23 we create two folders. N26, we add a grant allowing Agent 99 to create and view content. Since there is no block between N26 and N23, G49 also has maintain permission on N26. N26 is effectively a drop box for Agent 99.
Looking at N24, G49 has maintain, but Agent 007 has the maintain permission set. If maintain includes site.maintain, then user could actually create a Sakai site hanging off N24. This last use case is not currently a 2.1 requirement but only included to show the flexibility of the data model.
If we add the capable to mark a grant as un-blockable (indicated in red above), it reduces the need to copy the “very powerful” instructor grants to the various nodes below a block. Another term for this concept is an “admin” grant. If you notice, every time we added a block, we immediately added a grant of “maintain” to G49. If our intent is for G49 to have maintain from N20 on down, lets just indicate this on the grant..
This eliminates the grants at N17, N18, N19, and N23 and significantly simplifies the instructor’s maintenance responsibility each time a new node is made with a block indication.
This also allows tools to make nodes with blocked inheritance automatically as part of a wizard without having to figure out which of the grants above are to be copied to newly created sub-nodes which block inheritance.
This also allows the trivial addition of a whole new group of guest instructors for weeks 4-6 of the class (G63) and then remove the permission at the end of week 6.
This allows us to have less grants and reduces unnecessary copying of permissions and also reduces the need to patch permissions when some aspect of the course permission structure needs to change.
Continuing, we can imagine granting broad capabilities to department or college level administrators. By making these grants non-blockable, power flows down regardless of the block indicators.
N15 is a departmental node where a departmental administrator's group (G86) is given “access” permission for all nodes/courses/sites within the department. We could even place a site S11 (add some tools) at Node N15 and grant “maintain” to the G87 group. Because of the blocks, the G87 group has no power beyond Node N15 while G86 has broad access power at N15 and below.
At node N1, Group G85 is given some very broad powers over the whole tree. It is not blockable at all :)
As each node is added to the hierarchy, the transitive closure is computed (Orange links) so that all parents of a node can be determined in a single database query.
As the transitive closure is being computed, once a block is encountered, all remaining transitive links as one goes up the tree are marked as blocked.
Note that there is no transitive closure computed for an entity like content blob C93. Nor do any fine-grained object permissions participate in transitive closure computation. By not requiring any transitive closure for every entity, we significantly reduce the size of the transitive closure tables.
From C93, we can get the entire parent tree and for those parents marked as blocked, drop the “not-un-blockable” grants. This yields all of the applicable grants in a single sub-select. Permission sets can be expanded to permissions and group membership can be expanded as well. The permissions will be filtered down to “content.read” and we simply check to see if there are any direct or group membership, or group/role grants which enable content.read. With proper database design, this can all be done in a single query. (See Appendix S)
This is not really SQL - it is an outline of the needed SQL.
If you look at adding node N29 which would be added *with* inheritance, we simply add the N29->N22 row and make a copy of the N22 rows changing the child to N29. All of the block settings for N22 are already correct for N29.
If you look at adding node N23 which would be added without inheritance, we simply add the N23->N22 rows and make a copy of all of the N22 rows marking them all them all “block” while changing the child row from N22 to N23. Because if the new node is blocked to its immediate parent - it is blocked all the way up - regardless of the parent is blocked.
We assume that Grantees resolves into Agents and Function Sets resolve simply into functions without showing the table detail to accomplish the joins. Also the mapping from permission set (and associated filtering) is not shown.
Also it needs to be clear that permission sets are contextualized to the nodes they are associated with (I.e. each node can separately define “access”)
Looking for the permissions on C93, we first look for any direct permissions and find the A99 permission. We union this with any permissions granted on the transitive parents (N23, N22, N20, and N15) of the C93’s designated nodes. We filter these permissions based on whether the node relationship is blocked and whether the grant is blockable. In the case where the grant is blockable and the inheritance is blocked (G50 and G86) the grants fall out of the join.
C94 is a bit trickier and will require some subtle design on the JOIN query to do it all in a single join. The fun comes in around Node 20 and the G50 access.
Because of the C94 -> N22 -> N20 path is “inherit” we need to apply the G50 “access” grant to C94. We must be careful *not* to throw the grant away because the C94 -> N17 -> N20 has a “block”.
As long as the JOIN is written to accumulate permissions and do the block/blockable filtering logic separately on each intermediate tuple generated by the join, this should be feasible.
There may be other challenging multi-linked situations which may need working through.