https://docs.moodle.org/501/en/api.php?action=feedcontributions&feedformat=atom&user=Dthies 2026-04-14T22:00:33Z User contributions MediaWiki 1.43.5 https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=153959 2025-09-09T17:54:45Z

<p>Dthies: /* Introduction */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=463717 Plenary meeting activity]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The '''Plenary meeting''' activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has an integration with [[Deft response]] block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. Two integration options are provided for [https://jitsi.org Jitsi meet]. There is a managed meeting form that provides similar functionality to the Deft response option, and there is a meeting form option that simply provides a standard Jitsi Meet room on the meeting page.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until this happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available. Whether seconds are required for a type of motion can be configured by the admin for the site.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss the question before less privileged motions.<br /> <br /> ==Meeting forms==<br /> The activity can configured for use in different contexts to be selected in the activity settings. This is done with meeting form plugins. The following meeting forms are included.<br /> <br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the chair and the person who has the floor can share audio and video to speak to the pending business. When a new motion is allowed on the floor, the previous speaker is dropped and the person offering the new motion is automatically given the capability to share a camera and microphone.<br /> ===Jitsi meet===<br /> If a [https://jitsi.org Jitsi Meet] server is available, the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. Some actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. This form is useful for small groups that are familiar with using traditional web conferencing rooms.<br /> ===Managed Jitsi meet===<br /> The behavior of this meeting form is similar to the Deft meeting integration above, but is able to work with self hosted Jitsi meet servers as a back end.<br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> === Moodle App support ===<br /> The Moodle Mobile App is supported by the activity. Participants can use the app to create, view and modify motions. The Deft meeting form allows watching other speakers, but not speaking.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> = Additional configuration =<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> == Configuring Deft integration ==<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> == Jitsi Meet ==<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from the developer at [https://deftly.us deftly.us] if you are unable to install locally. There are some additional features that are also available. You can create a free account there and a sample course from the user dashboard, and then submit a site support request for LTI Access.<br /> <br /> [[es:Reunión plenaria]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Deft&diff=153958 2025-09-08T23:43:05Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Block<br /> |entry = https://moodle.org/plugins/block_deft<br /> |tracker = https://github.com/dthies/moodle-block_deft/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=469745 Deft response block]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]], [[Stefan Scholz]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The ''Deft response'' block allows a Manager or Editing teacher to create multiple tasks consisting of short texts, discussions, polls, audio conferences and control remotely which ones are displayed and how students may interact with them.<br /> There is a external service that is available to push notifications to clients to update content. This can be configured easily from the plugin and is free for limited usage. Larger sites may need a service agreement in the future. More information and demos are available at [https://deftly.us Deftly.us]. Alternatively a self hosted Jitsi Meet server can be used to enable the content updating.<br /> == Managing tasks ==<br /> The block can be added the usual way to a block or course by a user with the Add instance capability. If the user has block/deft:edit or block/deft:manage capability on the block, a Manage button will appear in the block. Clicking the button opens a Manage Tasks dashboard for the block instance. Teachers can make the tasks visible and adjust other parameters on the dashboard and changes will by visible in learners' browsers.<br /> === Defining Tasks ===<br /> If a user has block/deft:edit capability, the dashboard should also have an ''Add text'', ''Add comments'', ''Add choice'', and ''Add venue'' button. Clicking one of the buttons opens a modal form to define a new task. Tasks should be named in a way that helps distinguish them from each other on the dashboard. When the form is saved a task card will appear on the dashboard, but the task will not be visible yet in the block.<br /> ==== Choice ====<br /> [[File:edit choice.png|thumb|Editing Deft Choice on dashboard]]<br /> The choice task allows teachers to poll a class. The editing form defines the a question or prompt and short response that will be available for the students to choose.<br /> ==== Text ====<br /> The text tasks contains simple text that can be later be displayed in the block individually. The text area can contain multiple lines and simple html formatting, urls that may display as links, emoticons, but no media tags.<br /> ==== Comments ====<br /> The Comments task allow student to respond in the block and interact with each other. With the active updates, students can see comments in real time. This allows the block to be used for small discussions or chats. More than one Comments can be added to handle separate or group discussions. The individual task can be shown or hidden to start or moderate the discussions.<br /> The order of the tasks can be arranged. All task are initially hidden from view in the block.<br /> ==== Venue ====<br /> [[File:venue.png|thumb|Users in Venue]]<br /> The Venue task allows learners to converse with each other in a small audio chat format. Each venue is a separate place that a group of students can meet. When the teacher makes the task visible, a button is displayed on the block. When users click the button, they enter the venue and are connected with any other users already present using a peer-to-peer WebRTC audio connection.<br /> <br /> A venue can also be configured to use a bridged connection. Audio is connected through a central server to allow more participants and provide better quality. A teacher or others may also be allowed to stream video in the venue. An appropriate service agreement may be required to use the bridge server or a local instance of Jitsi Meet needs to be configured.<br /> === Deploying tasks ===<br /> [[File:task dashboard.png|thumb|Manage tasks dashboard|alt=]]<br /> A non-editing teacher, teacher, manager or any role with block/deft:manage capability will see a Manage button on the Deft response block. Clicking the button will open the manage task dashboard and change display options for the tasks. The user will not be able to create, edit or move task without the block/deft:edit capability.<br /> Display options can be changed with a form that appears on the task card. Changes will be visible only after they are submitted. <br /> == Installation and initial setup ==<br /> === Installation ===<br /> There are several options how to install the deft response block:<br /> ==== Option 1: Install from Moodle.org ====<br /> * Login as an admin and go to Site administration &gt; Plugins &gt; Install plugins. (If you can't find this location, then plugin installation is prevented on your site.)<br /> * Click the button 'Install plugins from Moodle plugins directory'.<br /> * Search for &quot;Deft response&quot;, click the Install button then click Continue.<br /> * Confirm the installation request<br /> * Check the plugin validation report<br /> ==== Option 2: Install from zip package ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Login to your Moodle site as an admin and go to Administration &gt; Site administration &gt; Plugins &gt; Install plugins.<br /> * Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if the plugin is not automatically detected.<br /> * If your target directory is not writeable, you will see a warning message.<br /> * Check the plugin validation report<br /> ==== Option 3: Install manually on server ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Upload or copy it to your Moodle server.<br /> * Unzip it in the `/blocks` directory.<br /> * In your Moodle site (as admin) go to Settings &gt; Site administration &gt; Notifications (you should, for most plugin types, get a message saying the plugin is installed).<br /> For more detailed info, visit &lt;nowiki&gt;https://docs.moodle.org/400/en/Installing_plugins&lt;/nowiki&gt;<br /> === Initial setup ===<br /> &lt;code&gt;All features of the Deft Response block will now work, but they won't be instant i.e. the page won't auto-update until the registration has been completed.&lt;/code&gt;<br /> <br /> To enable updating go the Deft response block admin settings and select the server type to use. The complete the appropriate steps from the corresponding section below that.<br /> ==== Configuring Deftly server ====<br /> ===== Automatic registration =====<br /> * [[File:Deft activaition.png|thumb|Service Activation]]After the installation, please go to Administration &gt; Site administration &gt; Plugins &gt; Blocks &gt; Deft response<br /> * On this page, tick &quot;Enable updating&quot; checkbox and save and a activation button should appear.<br /> * Press the &quot;Activation&quot; button. This should create automatically a preconfigured external tool in Activities -&gt; External tool -&gt; Register tools to deftly.<br /> * A table showing usage will then be shown in the block settings instead of the button.<br /> <br /> <br /> You should now be able to add then block to a course or module and when tasks are changed they will be updated in all browsers where they are displayed.<br /> <br /> If that's not the case (i.e. tasks don't update instantly), automatic registration has probably not worked correctly and registration needs to be completed manually (see below).<br /> <br /> ===== Manual registration =====<br /> If automatic registration has failed, please sign up (free) for the deft service agreement on this page: https://bdecent.de/product/deft-service-agreement/<br /> <br /> We will contact you (via email) and provide you with all the information that you need to complete the manual registration.<br /> ==== Jitsi configuration ====<br /> If you wish to use Jitsi Meet, you need to install and configure a Jitsi Meet server locally. The server needs to be configured to use token based authentication. The Jitsi server will require an app ID and shared secret for the Moodle instance. The app ID and secret are copied to appropriate Deft response block admin settings.<br /> == Related plugins ==<br /> Other plugins can use the updating framework from this plugin. There are currently several plugins with this integration available. The [[Popup activities course format]] will update the course page to reflect changes in course content or completion conditions when enabled. The [[Plenary meeting]] activity provides an activity for managing meetings with parliamentary rules, and can use this plugin to update status and content and provide Audio and Video streaming. The [[VideoTime]] activity can add live chat to videos or provide video streaming.<br /> <br /> [[es:Ágil]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Deft&diff=153956 2025-09-08T15:04:16Z

<p>Dthies: Add related plugins</p> <hr /> <div>{{Infobox plugin<br /> |type = Block<br /> |entry = https://moodle.org/plugins/block_deft<br /> |tracker = https://github.com/dthies/moodle-block_deft/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=436763 Deft response block]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]], [[Stefan Scholz]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The ''Deft response'' block allows a Manager or Editing teacher to create multiple tasks consisting of short texts, discussions, polls, audio conferences and control remotely which ones are displayed and how students may interact with them.<br /> There is a external service that is available to push notifications to clients to update content. This can be configured easily from the plugin and is free for limited usage. Larger sites may need a service agreement in the future. More information and demos are available at [https://deftly.us Deftly.us]. Alternatively a self hosted Jitsi Meet server can be used to enable the content updating.<br /> == Managing tasks ==<br /> The block can be added the usual way to a block or course by a user with the Add instance capability. If the user has block/deft:edit or block/deft:manage capability on the block, a Manage button will appear in the block. Clicking the button opens a Manage Tasks dashboard for the block instance. Teachers can make the tasks visible and adjust other parameters on the dashboard and changes will by visible in learners' browsers.<br /> === Defining Tasks ===<br /> If a user has block/deft:edit capability, the dashboard should also have an ''Add text'', ''Add comments'', ''Add choice'', and ''Add venue'' button. Clicking one of the buttons opens a modal form to define a new task. Tasks should be named in a way that helps distinguish them from each other on the dashboard. When the form is saved a task card will appear on the dashboard, but the task will not be visible yet in the block.<br /> ==== Choice ====<br /> [[File:edit choice.png|thumb|Editing Deft Choice on dashboard]]<br /> The choice task allows teachers to poll a class. The editing form defines the a question or prompt and short response that will be available for the students to choose.<br /> ==== Text ====<br /> The text tasks contains simple text that can be later be displayed in the block individually. The text area can contain multiple lines and simple html formatting, urls that may display as links, emoticons, but no media tags.<br /> ==== Comments ====<br /> The Comments task allow student to respond in the block and interact with each other. With the active updates, students can see comments in real time. This allows the block to be used for small discussions or chats. More than one Comments can be added to handle separate or group discussions. The individual task can be shown or hidden to start or moderate the discussions.<br /> The order of the tasks can be arranged. All task are initially hidden from view in the block.<br /> ==== Venue ====<br /> [[File:venue.png|thumb|Users in Venue]]<br /> The Venue task allows learners to converse with each other in a small audio chat format. Each venue is a separate place that a group of students can meet. When the teacher makes the task visible, a button is displayed on the block. When users click the button, they enter the venue and are connected with any other users already present using a peer-to-peer WebRTC audio connection.<br /> <br /> A venue can also be configured to use a bridged connection. Audio is connected through a central server to allow more participants and provide better quality. A teacher or others may also be allowed to stream video in the venue. An appropriate service agreement may be required to use the bridge server or a local instance of Jitsi Meet needs to be configured.<br /> === Deploying tasks ===<br /> [[File:task dashboard.png|thumb|Manage tasks dashboard|alt=]]<br /> A non-editing teacher, teacher, manager or any role with block/deft:manage capability will see a Manage button on the Deft response block. Clicking the button will open the manage task dashboard and change display options for the tasks. The user will not be able to create, edit or move task without the block/deft:edit capability.<br /> Display options can be changed with a form that appears on the task card. Changes will be visible only after they are submitted. <br /> == Installation and initial setup ==<br /> === Installation ===<br /> There are several options how to install the deft response block:<br /> ==== Option 1: Install from Moodle.org ====<br /> * Login as an admin and go to Site administration &gt; Plugins &gt; Install plugins. (If you can't find this location, then plugin installation is prevented on your site.)<br /> * Click the button 'Install plugins from Moodle plugins directory'.<br /> * Search for &quot;Deft response&quot;, click the Install button then click Continue.<br /> * Confirm the installation request<br /> * Check the plugin validation report<br /> ==== Option 2: Install from zip package ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Login to your Moodle site as an admin and go to Administration &gt; Site administration &gt; Plugins &gt; Install plugins.<br /> * Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if the plugin is not automatically detected.<br /> * If your target directory is not writeable, you will see a warning message.<br /> * Check the plugin validation report<br /> ==== Option 3: Install manually on server ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Upload or copy it to your Moodle server.<br /> * Unzip it in the `/blocks` directory.<br /> * In your Moodle site (as admin) go to Settings &gt; Site administration &gt; Notifications (you should, for most plugin types, get a message saying the plugin is installed).<br /> For more detailed info, visit &lt;nowiki&gt;https://docs.moodle.org/400/en/Installing_plugins&lt;/nowiki&gt;<br /> === Initial setup ===<br /> &lt;code&gt;All features of the Deft Response block will now work, but they won't be instant i.e. the page won't auto-update until the registration has been completed.&lt;/code&gt;<br /> <br /> To enable updating go the Deft response block admin settings and select the server type to use. The complete the appropriate steps from the corresponding section below that.<br /> ==== Configuring Deftly server ====<br /> ===== Automatic registration =====<br /> * [[File:Deft activaition.png|thumb|Service Activation]]After the installation, please go to Administration &gt; Site administration &gt; Plugins &gt; Blocks &gt; Deft response<br /> * On this page, tick &quot;Enable updating&quot; checkbox and save and a activation button should appear.<br /> * Press the &quot;Activation&quot; button. This should create automatically a preconfigured external tool in Activities -&gt; External tool -&gt; Register tools to deftly.<br /> * A table showing usage will then be shown in the block settings instead of the button.<br /> <br /> <br /> You should now be able to add then block to a course or module and when tasks are changed they will be updated in all browsers where they are displayed.<br /> <br /> If that's not the case (i.e. tasks don't update instantly), automatic registration has probably not worked correctly and registration needs to be completed manually (see below).<br /> <br /> ===== Manual registration =====<br /> If automatic registration has failed, please sign up (free) for the deft service agreement on this page: https://bdecent.de/product/deft-service-agreement/<br /> <br /> We will contact you (via email) and provide you with all the information that you need to complete the manual registration.<br /> ==== Jitsi configuration ====<br /> If you wish to use Jitsi Meet, you need to install and configure a Jitsi Meet server locally. The server needs to be configured to use token based authentication. The Jitsi server will require an app ID and shared secret for the Moodle instance. The app ID and secret are copied to appropriate Deft response block admin settings.<br /> == Related plugins ==<br /> Other plugins can use the updating framework from this plugin. There are currently several plugins with this integration available. The [[Popup activities course format]] will update the course page to reflect changes in course content or completion conditions when enabled. The [[Plenary meeting]] activity provides an activity for managing meetings with parliamentary rules, and can use this plugin to update status and content and provide Audio and Video streaming. The [[VideoTime]] activity can add live chat to videos or provide video streaming.<br /> <br /> [[es:Ágil]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Popup_activities_course_format&diff=153953 2025-09-07T22:49:07Z

<p>Dthies: /* Deft response integration */</p> <hr /> <div>{{Infobox plugin<br /> |type = Course formats<br /> |entry = https://moodle.org/plugins/format_popups<br /> |tracker = https://github.com/dthies/moodle-format_popups/issues<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=420525<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> The Pop up activities course format displays resources and simple activities embedded in modals instead of redirecting from the course page. Otherwise it behaves as the [[ Course formats#Custom_sections | Custom sections]].<br /> <br /> If you are not using heavy server side assessment, but mostly resources and client side activities (SCORM, H5P), this format may help provide more interactive courses by opening the activities in popup modals instead of separate web pages. When students finish an activity or resource, they return to the course page by closing the modal without waiting for the course page to load again. The course page updates activity completion and availability when the modal is closed. <br /> <br /> This plugin uses javascript to add AJAX functionality to the standard topics format. Otherwise the format is the same as the [[ Course formats#Topics_format | Topics format]]. Currently [[Assignment]], [[Book]], [[Choice]], [https://moodle.org/plugins/mod_contentdesigner Content designer ], [https://moodle.org/plugins/mod_customcert Custom certificate ], [https://moodle.org/plugins/mod_etherpadlite Etherpad lite], [[External tool]], [[File resource]], [[Folder]], [[H5P activity]], [[Page]], [[Plenary meeting]], [https://moodle.org/plugins/mod_poster Poster], [[SCORM]], [[URL]], and [[VideoTime|Video Time]] activities are supported and can be displayed in modals. Other activities will open normally.<br /> <br /> Developers should be able to add similar functionality to other formats by copying the AMD call in format.php or section content renderer and adding this format as a dependency.<br /> == Capability ==<br /> Users will only see the popups for the supported activities if they have the capability 'format/popups:view' in the modules context. By default students have this capability. It can be given to other roles or removed at course or activity level.<br /> <br /> == Deft response integration ==<br /> This format includes an optional integration is with [[Deft response]] block that can enable the course page to be updated when something happens in the background that affects it, for example activity or completion changes. To use this the admin needs to check the box to Enable Deft response in the format admin settings and configure the service from deftly.us in the Deft response admin settings. When that is done, the course page will automatically update completion and other activity information without reloading, and course editing pages will also update.<br /> <br /> ==Configuration==<br /> When editing course settings select ''Popup activities'' under Course format. Other options are the same as Topics format. Teachers by default will not see popups, but students will. This can be changed by editing the role and changing permissions for capability format/popups:view.<br /> <br /> There are some site administration settings available to change navigation. Navigation links can added to the previous and next activities may be added to the bottom of the popups. In Moodle 4.0+ administrators can choose whether the course index will be available in this format or not.<br /> ==Demo Course==<br /> A demonstration course is available on the developer's site https://openlearner.org/popups.<br /> <br /> [[es:Formato de curso Actividades emergentes]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Popup_activities_course_format&diff=153952 2025-09-07T22:41:34Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Course formats<br /> |entry = https://moodle.org/plugins/format_popups<br /> |tracker = https://github.com/dthies/moodle-format_popups/issues<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=420525<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> The Pop up activities course format displays resources and simple activities embedded in modals instead of redirecting from the course page. Otherwise it behaves as the [[ Course formats#Custom_sections | Custom sections]].<br /> <br /> If you are not using heavy server side assessment, but mostly resources and client side activities (SCORM, H5P), this format may help provide more interactive courses by opening the activities in popup modals instead of separate web pages. When students finish an activity or resource, they return to the course page by closing the modal without waiting for the course page to load again. The course page updates activity completion and availability when the modal is closed. <br /> <br /> This plugin uses javascript to add AJAX functionality to the standard topics format. Otherwise the format is the same as the [[ Course formats#Topics_format | Topics format]]. Currently [[Assignment]], [[Book]], [[Choice]], [https://moodle.org/plugins/mod_contentdesigner Content designer ], [https://moodle.org/plugins/mod_customcert Custom certificate ], [https://moodle.org/plugins/mod_etherpadlite Etherpad lite], [[External tool]], [[File resource]], [[Folder]], [[H5P activity]], [[Page]], [[Plenary meeting]], [https://moodle.org/plugins/mod_poster Poster], [[SCORM]], [[URL]], and [[VideoTime|Video Time]] activities are supported and can be displayed in modals. Other activities will open normally.<br /> <br /> Developers should be able to add similar functionality to other formats by copying the AMD call in format.php or section content renderer and adding this format as a dependency.<br /> == Capability ==<br /> Users will only see the popups for the supported activities if they have the capability 'format/popups:view' in the modules context. By default students have this capability. It can be given to other roles or removed at course or activity level.<br /> <br /> == Deft response integration ==<br /> This format includes an optional integration is with [[Deft response]] block that can enable the course page to be updated when something happens in the background that affects it, for example activity or completion changes.<br /> <br /> ==Configuration==<br /> When editing course settings select ''Popup activities'' under Course format. Other options are the same as Topics format. Teachers by default will not see popups, but students will. This can be changed by editing the role and changing permissions for capability format/popups:view.<br /> <br /> There are some site administration settings available to change navigation. Navigation links can added to the previous and next activities may be added to the bottom of the popups. In Moodle 4.0+ administrators can choose whether the course index will be available in this format or not.<br /> ==Demo Course==<br /> A demonstration course is available on the developer's site https://openlearner.org/popups.<br /> <br /> [[es:Formato de curso Actividades emergentes]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Popup_activities_course_format&diff=153951 2025-09-07T22:40:36Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Course formats<br /> |entry = https://moodle.org/plugins/format_popups<br /> |tracker = https://github.com/dthies/moodle-format_popups/issues<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=420525<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> The Pop up activities course format displays resources and simple activities embedded in modals instead of redirecting from the course page. Otherwise it behaves as the [[ Course formats#Custom_sections | Custom sections ]].<br /> <br /> If you are not using heavy server side assessment, but mostly resources and client side activities (SCORM, H5P), this format may help provide more interactive courses by opening the activities in popup modals instead of separate web pages. When students finish an activity or resource, they return to the course page by closing the modal without waiting for the course page to load again. The course page updates activity completion and availability when the modal is closed. <br /> <br /> This plugin uses javascript to add AJAX functionality to the standard topics format. Otherwise the format is the same as the [[ Course formats#Topics_format | Topics format]]. Currently [[Assignment]], [[Book]], [[Choice]], [https://moodle.org/plugins/mod_contentdesigner Content designer ], [https://moodle.org/plugins/mod_customcert Custom certificate ], [https://moodle.org/plugins/mod_etherpadlite Etherpad lite], [[External tool]], [[File resource]], [[Folder]], [[H5P activity]], [[Page]], [[Plenary meeting]], [https://moodle.org/plugins/mod_poster Poster], [[SCORM]], [[URL]], and [[VideoTime|Video Time]] activities are supported and can be displayed in modals. Other activities will open normally.<br /> <br /> Developers should be able to add similar functionality to other formats by copying the AMD call in format.php or section content renderer and adding this format as a dependency.<br /> == Capability ==<br /> Users will only see the popups for the supported activities if they have the capability 'format/popups:view' in the modules context. By default students have this capability. It can be given to other roles or removed at course or activity level.<br /> <br /> == Deft response integration ==<br /> This format includes an optional integration is with [[Deft response]] block that can enable the course page to be updated when something happens in the background that affects it, for example activity or completion changes.<br /> <br /> ==Configuration==<br /> When editing course settings select ''Popup activities'' under Course format. Other options are the same as Topics format. Teachers by default will not see popups, but students will. This can be changed by editing the role and changing permissions for capability format/popups:view.<br /> <br /> There are some site administration settings available to change navigation. Navigation links can added to the previous and next activities may be added to the bottom of the popups. In Moodle 4.0+ administrators can choose whether the course index will be available in this format or not.<br /> ==Demo Course==<br /> A demonstration course is available on the developer's site https://openlearner.org/popups.<br /> <br /> [[es:Formato de curso Actividades emergentes]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Deft&diff=153950 2025-09-07T21:44:22Z

<p>Dthies: /* Venue */</p> <hr /> <div>{{Infobox plugin<br /> |type = Block<br /> |entry = https://moodle.org/plugins/block_deft<br /> |tracker = https://github.com/dthies/moodle-block_deft/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=436763 Deft response block]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]], [[Stefan Scholz]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The ''Deft response'' block allows a Manager or Editing teacher to create multiple tasks consisting of short texts, discussions, polls, audio conferences and control remotely which ones are displayed and how students may interact with them.<br /> There is a external service that is available to push notifications to clients to update content. This can be configured easily from the plugin and is free for limited usage. Larger sites may need a service agreement in the future. More information and demos are available at [https://deftly.us Deftly.us]. Alternatively a self hosted Jitsi Meet server can be used to enable the content updating.<br /> == Managing tasks ==<br /> The block can be added the usual way to a block or course by a user with the Add instance capability. If the user has block/deft:edit or block/deft:manage capability on the block, a Manage button will appear in the block. Clicking the button opens a Manage Tasks dashboard for the block instance. Teachers can make the tasks visible and adjust other parameters on the dashboard and changes will by visible in learners' browsers.<br /> === Defining Tasks ===<br /> If a user has block/deft:edit capability, the dashboard should also have an ''Add text'', ''Add comments'', ''Add choice'', and ''Add venue'' button. Clicking one of the buttons opens a modal form to define a new task. Tasks should be named in a way that helps distinguish them from each other on the dashboard. When the form is saved a task card will appear on the dashboard, but the task will not be visible yet in the block.<br /> ==== Choice ====<br /> [[File:edit choice.png|thumb|Editing Deft Choice on dashboard]]<br /> The choice task allows teachers to poll a class. The editing form defines the a question or prompt and short response that will be available for the students to choose.<br /> ==== Text ====<br /> The text tasks contains simple text that can be later be displayed in the block individually. The text area can contain multiple lines and simple html formatting, urls that may display as links, emoticons, but no media tags.<br /> ==== Comments ====<br /> The Comments task allow student to respond in the block and interact with each other. With the active updates, students can see comments in real time. This allows the block to be used for small discussions or chats. More than one Comments can be added to handle separate or group discussions. The individual task can be shown or hidden to start or moderate the discussions.<br /> The order of the tasks can be arranged. All task are initially hidden from view in the block.<br /> ==== Venue ====<br /> [[File:venue.png|thumb|Users in Venue]]<br /> The Venue task allows learners to converse with each other in a small audio chat format. Each venue is a separate place that a group of students can meet. When the teacher makes the task visible, a button is displayed on the block. When users click the button, they enter the venue and are connected with any other users already present using a peer-to-peer WebRTC audio connection.<br /> <br /> A venue can also be configured to use a bridged connection. Audio is connected through a central server to allow more participants and provide better quality. A teacher or others may also be allowed to stream video in the venue. An appropriate service agreement may be required to use the bridge server or a local instance of Jitsi Meet needs to be configured.<br /> === Deploying tasks ===<br /> [[File:task dashboard.png|thumb|Manage tasks dashboard|alt=]]<br /> A non-editing teacher, teacher, manager or any role with block/deft:manage capability will see a Manage button on the Deft response block. Clicking the button will open the manage task dashboard and change display options for the tasks. The user will not be able to create, edit or move task without the block/deft:edit capability.<br /> Display options can be changed with a form that appears on the task card. Changes will be visible only after they are submitted. <br /> == Installation and initial setup ==<br /> === Installation ===<br /> There are several options how to install the deft response block:<br /> ==== Option 1: Install from Moodle.org ====<br /> * Login as an admin and go to Site administration &gt; Plugins &gt; Install plugins. (If you can't find this location, then plugin installation is prevented on your site.)<br /> * Click the button 'Install plugins from Moodle plugins directory'.<br /> * Search for &quot;Deft response&quot;, click the Install button then click Continue.<br /> * Confirm the installation request<br /> * Check the plugin validation report<br /> ==== Option 2: Install from zip package ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Login to your Moodle site as an admin and go to Administration &gt; Site administration &gt; Plugins &gt; Install plugins.<br /> * Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if the plugin is not automatically detected.<br /> * If your target directory is not writeable, you will see a warning message.<br /> * Check the plugin validation report<br /> ==== Option 3: Install manually on server ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Upload or copy it to your Moodle server.<br /> * Unzip it in the `/blocks` directory.<br /> * In your Moodle site (as admin) go to Settings &gt; Site administration &gt; Notifications (you should, for most plugin types, get a message saying the plugin is installed).<br /> For more detailed info, visit &lt;nowiki&gt;https://docs.moodle.org/400/en/Installing_plugins&lt;/nowiki&gt;<br /> === Initial setup ===<br /> &lt;code&gt;All features of the Deft Response block will now work, but they won't be instant i.e. the page won't auto-update until the registration has been completed.&lt;/code&gt;<br /> <br /> To enable updating go the Deft response block admin settings and select the server type to use. The complete the appropriate steps from the corresponding section below that.<br /> ==== Configuring Deftly server ====<br /> ===== Automatic registration =====<br /> * [[File:Deft activaition.png|thumb|Service Activation]]After the installation, please go to Administration &gt; Site administration &gt; Plugins &gt; Blocks &gt; Deft response<br /> * On this page, tick &quot;Enable updating&quot; checkbox and save and a activation button should appear.<br /> * Press the &quot;Activation&quot; button. This should create automatically a preconfigured external tool in Activities -&gt; External tool -&gt; Register tools to deftly.<br /> * A table showing usage will then be shown in the block settings instead of the button.<br /> <br /> <br /> You should now be able to add then block to a course or module and when tasks are changed they will be updated in all browsers where they are displayed.<br /> <br /> If that's not the case (i.e. tasks don't update instantly), automatic registration has probably not worked correctly and registration needs to be completed manually (see below).<br /> <br /> ===== Manual registration =====<br /> If automatic registration has failed, please sign up (free) for the deft service agreement on this page: https://bdecent.de/product/deft-service-agreement/<br /> <br /> We will contact you (via email) and provide you with all the information that you need to complete the manual registration.<br /> ==== Jitsi configuration ====<br /> If you wish to use Jitsi Meet, you need to install and configure a Jitsi Meet server locally. The server needs to be configured to use token based authentication. The Jitsi server will require an app ID and shared secret for the Moodle instance. The app ID and secret are copied to appropriate Deft response block admin settings.<br /> <br /> <br /> [[es:Ágil]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Deft&diff=153949 2025-09-07T20:54:42Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Block<br /> |entry = https://moodle.org/plugins/block_deft<br /> |tracker = https://github.com/dthies/moodle-block_deft/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=436763 Deft response block]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]], [[Stefan Scholz]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The ''Deft response'' block allows a Manager or Editing teacher to create multiple tasks consisting of short texts, discussions, polls, audio conferences and control remotely which ones are displayed and how students may interact with them.<br /> There is a external service that is available to push notifications to clients to update content. This can be configured easily from the plugin and is free for limited usage. Larger sites may need a service agreement in the future. More information and demos are available at [https://deftly.us Deftly.us]. Alternatively a self hosted Jitsi Meet server can be used to enable the content updating.<br /> == Managing tasks ==<br /> The block can be added the usual way to a block or course by a user with the Add instance capability. If the user has block/deft:edit or block/deft:manage capability on the block, a Manage button will appear in the block. Clicking the button opens a Manage Tasks dashboard for the block instance. Teachers can make the tasks visible and adjust other parameters on the dashboard and changes will by visible in learners' browsers.<br /> === Defining Tasks ===<br /> If a user has block/deft:edit capability, the dashboard should also have an ''Add text'', ''Add comments'', ''Add choice'', and ''Add venue'' button. Clicking one of the buttons opens a modal form to define a new task. Tasks should be named in a way that helps distinguish them from each other on the dashboard. When the form is saved a task card will appear on the dashboard, but the task will not be visible yet in the block.<br /> ==== Choice ====<br /> [[File:edit choice.png|thumb|Editing Deft Choice on dashboard]]<br /> The choice task allows teachers to poll a class. The editing form defines the a question or prompt and short response that will be available for the students to choose.<br /> ==== Text ====<br /> The text tasks contains simple text that can be later be displayed in the block individually. The text area can contain multiple lines and simple html formatting, urls that may display as links, emoticons, but no media tags.<br /> ==== Comments ====<br /> The Comments task allow student to respond in the block and interact with each other. With the active updates, students can see comments in real time. This allows the block to be used for small discussions or chats. More than one Comments can be added to handle separate or group discussions. The individual task can be shown or hidden to start or moderate the discussions.<br /> The order of the tasks can be arranged. All task are initially hidden from view in the block.<br /> ==== Venue ====<br /> [[File:venue.png|thumb|Users in Venue]]<br /> The Venue task allows learners to converse with each other in a small audio chat format. Each venue is a separate place that a group of students can meet. When the teacher makes the task visible, a button is displayed on the block. When users click the button, they enter the venue and are connected with any other users already present using a peer-to-peer WebRTC audio connection.<br /> <br /> A venue can also be configured to use a bridged connection. Audio is connected through a central server to allow more participants and provide better quality. A teacher or others may also be allowed to stream video in the venue. An appropriate service agreement may be required to use the bridge server.<br /> === Deploying tasks ===<br /> [[File:task dashboard.png|thumb|Manage tasks dashboard|alt=]]<br /> A non-editing teacher, teacher, manager or any role with block/deft:manage capability will see a Manage button on the Deft response block. Clicking the button will open the manage task dashboard and change display options for the tasks. The user will not be able to create, edit or move task without the block/deft:edit capability.<br /> Display options can be changed with a form that appears on the task card. Changes will be visible only after they are submitted. <br /> == Installation and initial setup ==<br /> === Installation ===<br /> There are several options how to install the deft response block:<br /> ==== Option 1: Install from Moodle.org ====<br /> * Login as an admin and go to Site administration &gt; Plugins &gt; Install plugins. (If you can't find this location, then plugin installation is prevented on your site.)<br /> * Click the button 'Install plugins from Moodle plugins directory'.<br /> * Search for &quot;Deft response&quot;, click the Install button then click Continue.<br /> * Confirm the installation request<br /> * Check the plugin validation report<br /> ==== Option 2: Install from zip package ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Login to your Moodle site as an admin and go to Administration &gt; Site administration &gt; Plugins &gt; Install plugins.<br /> * Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if the plugin is not automatically detected.<br /> * If your target directory is not writeable, you will see a warning message.<br /> * Check the plugin validation report<br /> ==== Option 3: Install manually on server ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Upload or copy it to your Moodle server.<br /> * Unzip it in the `/blocks` directory.<br /> * In your Moodle site (as admin) go to Settings &gt; Site administration &gt; Notifications (you should, for most plugin types, get a message saying the plugin is installed).<br /> For more detailed info, visit &lt;nowiki&gt;https://docs.moodle.org/400/en/Installing_plugins&lt;/nowiki&gt;<br /> === Initial setup ===<br /> &lt;code&gt;All features of the Deft Response block will now work, but they won't be instant i.e. the page won't auto-update until the registration has been completed.&lt;/code&gt;<br /> <br /> To enable updating go the Deft response block admin settings and select the server type to use. The complete the appropriate steps from the corresponding section below that.<br /> ==== Configuring Deftly server ====<br /> ===== Automatic registration =====<br /> * [[File:Deft activaition.png|thumb|Service Activation]]After the installation, please go to Administration &gt; Site administration &gt; Plugins &gt; Blocks &gt; Deft response<br /> * On this page, tick &quot;Enable updating&quot; checkbox and save and a activation button should appear.<br /> * Press the &quot;Activation&quot; button. This should create automatically a preconfigured external tool in Activities -&gt; External tool -&gt; Register tools to deftly.<br /> * A table showing usage will then be shown in the block settings instead of the button.<br /> <br /> <br /> You should now be able to add then block to a course or module and when tasks are changed they will be updated in all browsers where they are displayed.<br /> <br /> If that's not the case (i.e. tasks don't update instantly), automatic registration has probably not worked correctly and registration needs to be completed manually (see below).<br /> <br /> ===== Manual registration =====<br /> If automatic registration has failed, please sign up (free) for the deft service agreement on this page: https://bdecent.de/product/deft-service-agreement/<br /> <br /> We will contact you (via email) and provide you with all the information that you need to complete the manual registration.<br /> ==== Jitsi configuration ====<br /> If you wish to use Jitsi Meet, you need to install and configure a Jitsi Meet server locally. The server needs to be configured to use token based authentication. The Jitsi server will require an app ID and shared secret for the Moodle instance. The app ID and secret are copied to appropriate Deft response block admin settings.<br /> <br /> <br /> [[es:Ágil]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Popup_activities_course_format&diff=153676 2025-07-14T16:59:48Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Course formats<br /> |entry = https://moodle.org/plugins/format_popups<br /> |tracker = https://github.com/dthies/moodle-format_popups/issues<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=420525<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> The Pop up activities course format displays resources and simple activities embedded in modals instead of redirecting from the course page. Otherwise it behaves as the [[ Course formats#Topics_format | Topics format]].<br /> <br /> If you are not using heavy server side assessment, but mostly resources and client side activities (SCORM, H5P), this format may help provide more interactive courses by opening the activities in popup modals instead of separate web pages. When students finish an activity or resource, they return to the course page by closing the modal without waiting for the course page to load again. The course page updates activity completion and availability when the modal is closed. <br /> <br /> This plugin uses javascript to add AJAX functionality to the standard topics format. Otherwise the format is the same as the [[ Course formats#Topics_format | Topics format]]. Currently [[Assignment]], [[Book]], [[Choice]], [https://moodle.org/plugins/mod_contentdesigner Content designer ], [https://moodle.org/plugins/mod_customcert Custom certificate ], [https://moodle.org/plugins/mod_etherpadlite Etherpad lite], [[External tool]], [[File resource]], [[Folder]], [[H5P activity]], [[Page]], [[Plenary meeting]], [https://moodle.org/plugins/mod_poster Poster], [[SCORM]], [[URL]], and [[VideoTime|Video Time]] activities are supported and can be displayed in modals. Other activities will open normally.<br /> <br /> Developers should be able to add similar functionality to other formats by copying the AMD call in format.php or section content renderer and adding this format as a dependency.<br /> == Capability ==<br /> Users will only see the popups for the supported activities if they have the capability 'format/popups:view' in the modules context. By default students have this capability. It can be given to other roles or removed at course or activity level.<br /> <br /> == Deft response integration ==<br /> This format includes an optional integration is with [[Deft response]] block that can enable the course page to be updated when something happens in the background that affects it, for example activity or completion changes.<br /> <br /> ==Configuration==<br /> When editing course settings select ''Popup activities'' under Course format. Other options are the same as Topics format. Teachers by default will not see popups, but students will. This can be changed by editing the role and changing permissions for capability format/popups:view.<br /> <br /> There are some site administration settings available to change navigation. Navigation links can added to the previous and next activities may be added to the bottom of the popups. In Moodle 4.0+ administrators can choose whether the course index will be available in this format or not.<br /> ==Demo Course==<br /> A demonstration course is available on the developer's site https://openlearner.org/popups.<br /> <br /> [[es:Formato de curso Actividades emergentes]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=150956 2025-01-29T18:35:38Z

<p>Dthies: /* Meeting forms */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=463717 Plenary meeting activity]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The '''Plenary meeting''' activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has an integration with [[Deft response]] block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for [https://jitsi.org Jitsi meet].<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until this happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available. Whether seconds are required for a type of motion can be configured by the admin for the site.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss the question before less privileged motions.<br /> <br /> ==Meeting forms==<br /> The activity can configured for use in different contexts to be selected in the activity settings. This is done with meeting form plugins. The following meeting forms are included.<br /> <br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the chair and the person who has the floor can share audio and video to speak to the pending business. When a new motion is allowed on the floor, the previous speaker is dropped and the person offering the new motion is automatically given the capability to share a camera and microphone.<br /> ===Jitsi meet===<br /> If a [https://jitsi.org Jitsi Meet] server is available, the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. Some actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. This form is useful for small groups that are familiar with using traditional web conferencing rooms.<br /> ===Managed Jitsi meet===<br /> The behavior of this meeting form is similar to the Deft meeting integration above, but is able to work with self hosted Jitsi meet servers as a back end.<br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> === Moodle App support ===<br /> The Moodle Mobile App is supported by the activity. Participants can use the app to create, view and modify motions. The Deft meeting form allows watching other speakers, but not speaking.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> = Additional configuration =<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> == Configuring Deft integration ==<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> == Jitsi Meet ==<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from the developer at [https://deftly.us deftly.us] if you are unable to install locally. There are some additional features that are also available. You can create a free account there and a sample course from the user dashboard, and then submit a site support request for LTI Access.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Course_copy&diff=150863 2025-01-14T02:18:04Z

<p>Dthies: /* Course copy settings */</p> <hr /> <div>{{Backup}}<br /> ==About course copy==<br /> Administrators, managers and those with the relevant capabilities can quickly copy courses from a course category or within a course.<br /> <br /> ==Course copy from Course and category management screen==<br /> # From ''Site administration / Courses / Manage courses and categories'', click to select a category.<br /> # Find the course you want to copy, and click the duplicate icon to copy the course.<br /> <br /> [[File:CategoryCopyCourse.png|center|Copying courses from a category]]<br /> <br /> ==Course copy from within a course==<br /> # Access the course you want to copy.<br /> # From Course navigation &gt; More &gt; Course reuse, select 'Course copy'.<br /> <br /> ==Course copy settings==<br /> As well as setting the course name, category, visibility and dates, you can make the following selections:<br /> * Include user data - Similar to in a course backup, you can decide whether or not to include the data of any users with the roles in your course who will be included in the next setting.<br /> * Include role enrolments - If you select a role here then users with that role will be enrolled into the copied course, either with or without their user data, depending on the previous setting.<br /> <br /> ==Import via CLI==<br /> An administrator can copy a course or and individual modules from a command line script. For example from the installation directory<br /> sudo -u www-data /usr/bin/php admin/cli/import.php --srccmid=21 --dstcourseid=1<br /> will copy a copy a module with id 21 into the course with id 1, and<br /> sudo -u www-data /usr/bin/php admin/cli/import.php --srccourseid=12 --dstcourseid=13<br /> will copy the entire contents of course with id 12 into course with id 13.<br /> <br /> ==Allow teachers to copy courses==<br /> To allow a course teacher (or any role other than an admin or manager) to copy courses, the role needs the following capabilities:<br /> <br /> * [[Capabilities/moodle/backup:backupcourse]]<br /> * [[Capabilities/moodle/restore:restorecourse]]<br /> * [[Capabilities/moodle/course:create]]<br /> <br /> When an editing teacher copies a course, they will become an editing teacher in the copied course.<br /> <br /> Besides, if you want they can include user data (i.e. keep role enrolments), the role will need the following capabilities too:<br /> <br /> * [[Capabilities/moodle/restore:createuser]]<br /> * [[Capabilities/moodle/backup:userinfo]]<br /> * [[Capabilities/moodle/restore:userinfo]]<br /> <br /> ==Troubleshooting==<br /> <br /> If course copying fails to complete, please check [[Cron]] is running every minute<br /> <br /> If there is a quiz in the course and you are a teacher or manager this feature does not currently work. For more information see MDL-69941<br /> <br /> [[es:Copia del curso]]<br /> [[de:Kurs kopieren]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Administration_via_command_line&diff=150862 2025-01-14T02:02:40Z

<p>Dthies: /* Backup and restore of large courses */</p> <hr /> <div>{{Installing Moodle}}<br /> {{Update}}<br /> ==Running CLI scripts==<br /> If you have shell access to your web server, you may find various CLI (command line interface) scripts useful during Moodle administration. Core admin CLI tools are located in the &lt;code&gt;admin/cli/*&lt;/code&gt; folder. Other plugins may provide CLI functionality via scripts in their own &lt;code&gt;cli&lt;/code&gt; folder.<br /> <br /> To avoid problems with access control, you should run them as the owner of the web server process. It is especially important for CLI installation and upgrade as they create new files in moodledata directory and the web server has to have write access to them. In Linux distributions, the user that runs the web server is usually apache or www-data or httpd or something similar. As a root, you will probably want to execute Moodle CLI scripts like this:<br /> $ cd /path/to/your/moodle/dir<br /> $ sudo -u apache /usr/bin/php admin/cli/somescript.php --params<br /> Most of the scripts accept common --help (or -h) parameter to display the full usage information, for example:<br /> $ sudo -u apache /usr/bin/php admin/cli/install.php --help<br /> {{Note|These scripts are supposed to be run under the identity of the web server user. Examples on this page use the &lt;tt&gt;apache&lt;/tt&gt; user for illustration. The particular value depends on your OS distribution and local set-up. Typical values may be &lt;tt&gt;apache&lt;/tt&gt;, &lt;tt&gt;www-data&lt;/tt&gt; or &lt;tt&gt;httpd&lt;/tt&gt;.}}<br /> == Upgrading ==<br /> Moodle can be upgraded from the command line. As with the installation script, there is either interactive or non-interactive mode of the upgrade. The script itself does not put the site into the maintenance mode, you have to do it on your own. Also, the script does not backup any data.<br /> {{Note| As mentioned above, the upgrade php script does not perform a backup of the Moodle site data. Before running this script, make sure you have taken a proper site backup including the software, data directory, and database before you perform the upgrade.}}<br /> To run the interactive upgrade, execute the following command:<br /> $ sudo -u apache /usr/bin/php admin/cli/upgrade.php<br /> Upgrading via command line is a very comfortable way of Moodle upgrade if you use Git checkout of the Moodle source code (see [[Git for Administrators]]). See the following procedure how to upgrade your site within several seconds to the most recent version while preserving your eventual local customizations tracked in git repository:<br /> $ cd /var/www/sites/moodle/htdocs/<br /> $ sudo -u apache /usr/bin/php admin/cli/maintenance.php --enable<br /> $ git pull<br /> $ sudo -u apache /usr/bin/php admin/cli/upgrade.php<br /> $ sudo -u apache /usr/bin/php admin/cli/maintenance.php --disable<br /> Alternatively, instead of using git, the updated Moodle package can be downloaded from the Moodle site using the wget command, and then extracted with the tar command.<br /> $ wget &lt;nowiki&gt;https://download.moodle.org/download.php/direct/stable405/moodle-4.5.1.tgz&lt;/nowiki&gt;<br /> $ tar -xvzf moodle-4.5.1.tgz<br /> Note that the path must contain &quot;/direct/&quot;, or else wget will not work.<br /> ====PHP Extra Memory====<br /> Depending on your environment setup, to perform a CLI upgrade you *may* need to run PHP explicitly with more memory.&lt;br /&gt;<br /> This is only required if PHP is failing due to out of memory conditions.<br /> <br /> For example:<br /> $ sudo -u apache /usr/bin/php --memory_limit=16G admin/cli/upgrade.php<br /> <br /> The amount of memory will vary between Moodle LMS versions and your specific environment.<br /> <br /> ==Installation==<br /> There are two modes of installing Moodle from the command line. In interactive mode, the install script asks you for all data needed to properly set up new Moodle site. In non-interactive mode, you must provide all required data as the script parameters and then the new site is installed silently. The parameters can be passed in the interactive mode, too. The provided values are then used as the default values during the interactive session.<br /> $ sudo -u apache /usr/bin/php admin/cli/install.php --lang=cs<br /> If your arguments contain some specials characters for Linux-based systems, don't forget to ''escape'' them with a backslash. For example, if you want to create an admin with ''pa$sword'' as password you should wrote ''pa\$sword'' instead!<br /> <br /> If required, the database install may be skipped, with just config.php populated.<br /> $ sudo -u apache /usr/bin/php admin/cli/install.php --skip-database<br /> ==Maintenance mode==<br /> To switch your site into the maintenance mode via CLI, you can use<br /> $ sudo -u apache /usr/bin/php admin/cli/maintenance.php --enable<br /> To turn maintenance mode off, execute the same script with the --disable parameter:<br /> $ sudo -u apache /usr/bin/php admin/cli/maintenance.php --disable<br /> If you don't want to enable maintenance mode immediately, but show a countdown to your users, execute the same script with the --enablelater parameter and the number of minutes which the countdown should run:<br /> $ sudo -u apache /usr/bin/php admin/cli/maintenance.php --enablelater=10<br /> This script will also create and remove the climaintenance.html file for &quot;Offline&quot; mode.<br /> ==Offline mode==<br /> In some situations, you may want to switch your Moodle site into offline mode so that it is not accessible via the web but you can not stop the web server completely (typically because there are other web pages and applications running there). If a file called &lt;code&gt;climaintenance.html&lt;/code&gt; exists in the root folder of moodledata directory, Moodle will automatically display the contents of that file instead of any other page.<br /> $ cd /var/www/sites/moodle/moodledata/<br /> $ echo '&amp;lt;h1&amp;gt;Sorry, maintenance in progress&amp;lt;/h1&amp;gt;' &amp;gt; climaintenance.html<br /> You can prepare a nice formatted HTML page to inform your users about the server being down and keep in the moodledata directory under a name like &lt;code&gt;climaintenance.off&lt;/code&gt; and rename it to the &lt;code&gt;climaintenance.html&lt;/code&gt; if needed.<br /> ==Custom site defaults==<br /> During the install and upgrade via CLI, Moodle sets the administration variables to the default values. You can use different defaults. See MDL-17850 for details. Shortly, all you need to do is to add a file &lt;code&gt;local/defaults.php&lt;/code&gt; into your Moodle installation. The format of the file is like<br /> &lt;syntaxhighlight lang=&quot;php&quot;&gt;<br /> &lt;?php<br /> $defaults['pluginname']['settingname'] = 'settingvalue'; // for plugins<br /> $defaults['moodle']['settingname'] = 'settingvalue'; // for core settings<br /> &lt;/syntaxhighlight&gt;<br /> These defaults are used during install, upgrade and are also displayed as defaults on Site administration pages.<br /> ==Reset user password==<br /> If you happen to forget your admin password (or you want to set a password for any other user on the site), you can use reset_password.php script. The script sets the correctly salted password for the given user.<br /> $ sudo -u apache /usr/bin/php admin/cli/reset_password.php<br /> <br /> ==Display manual login form==<br /> If you hide the manual login form then find that you can no longer log in, you can display it again using the command line<br /> php admin/cli/cfg.php --name=showloginform --set=1<br /> <br /> ==Converting InnoDB to Barracuda==<br /> Newer versions of MySQL and MariaDB have an improved file format called Barracuda. To take advantage of this:<br /> #Ensure your version of MySQL/MariaDB is using Barracuda with the large index key prefix (innodb_large_prefix). See below for details.<br /> #Change to the compressed row format (see [[#Changing_tables_to_compressed_row_format|Changing tables to compressed row format]])<br /> #Change the character set and collation for full Unicode support (see [[#Converting_character_set_and_collation|Converting character set and collation]]).<br /> <br /> <br /> If you have MySQL 8.0.0 or later, or MariaDB 10.3.0 or later, then these versions only support Barracuda with the large index key prefix. For earlier versions to check if MySQL/MariaDB is using Barracuda run the following statement in the MySQL/MariaDB client or phpMyAdmin SQL tab:<br /> SHOW GLOBAL VARIABLES WHERE variable_name IN ('innodb_file_format', 'innodb_large_prefix', 'innodb_file_per_table');<br /> If your settings do not match any of the tables below, see [[MySQL#Configure_full_UTF-8_support|Configure full UTF-8 support]] for how to change these settings:<br /> <br /> [[File:phpMyAdmin1.png|alt=innodb_file_format=Barracuda;innodb_file_per_table=ON;innodb_large_prefix=ON]] or [[File:phpMyAdmin2.png|alt=innodb_file_format=(blank);innodb_file_per_table=ON;innodb_large_prefix=(blank)]] or [[File:phpMyAdmin3.png|alt=innodb_file_per_table=ON]]<br /> <br /> If your settings match one of these tables then MySQL/MariaDB is using Barracuda with the large index key prefix.<br /> ===Changing tables to compressed row format===<br /> This script changes tables with many text columns to use ROW_FORMAT=COMPRESSED. This change isn’t required but is recommended. If the database error ''Row size too large (&gt; 8126)'' occurs when using Moodle then run this script to fix this.<br /> <br /> '''Note:''' If you have MariaDB version 10.6.0 to 10.6.6 or version 10.7.0 to 10.7.2 you must upgrade to a later version before running this script. See MDL-72131 for details.<br /> <br /> To view tables requiring conversion, use the --list option:<br /> $ php admin/cli/mysql_compressed_rows.php --list<br /> Here is an example output:<br /> mdl_data Compact (needs fixing) <br /> mdl_data_fields Compact (needs fixing)<br /> mdl_enrol_paypal Compact (needs fixing)<br /> To proceed with the conversion, run the command using the fix option:<br /> $ php admin/cli/mysql_compressed_rows.php --fix<br /> Successful table conversion will be reported in the output, for example:<br /> mdl_data ... Compressed<br /> mdl_data_fields ... Compressed<br /> mdl_enrol_paypal ... Compressed<br /> If you get errors due to having insufficient privileges to run these commands use --showsql to generate the required SQL commands:<br /> $ php admin/cli/mysql_compressed_rows.php --showsql<br /> You can then copy the generated SQL into your MySQL/MariaDB client running as the 'root' user.<br /> ===Converting character set and collation===<br /> This script changes the Moodle database tables to enable full Unicode support.<br /> $ php admin/cli/mysql_collation.php --collation=utf8mb4_unicode_ci<br /> After making this change edit config.php and change the 'dbcollation' to 'utf8mb4_unicode_ci' in the $CFG-&gt;dboptions array.<br /> <br /> For further details see: [[MySQL full unicode support]]<br /> ==Running cron via command line==<br /> In versions 1.x, you could execute admin/cron.php either from command line or via the web. Since Moodle 2.0, only admin/cli/cron.php script can be run via command line.<br /> ==Scheduled tasks ==<br /> Scheduled tasks are automatically run by the cron script, but the specific tasks which run on each cron iteration are determined by the scheduled tasks configuration. It is possible to override the scheduled tasks configuration and run a single scheduled task immediately using the admin/cli/scheduled_task.php script. <br /> <br /> This script accepts the following arguments:<br /> --list - list all the known scheduled tasks. The tasks are listed by the class name used to run the task. This class name is required as the argument to the next option in order to run a specific task immediately.<br /> <br /> --execute=&lt;task&gt; - Runs a single scheduled task immediately - regardless of scheduling settings. This will even run disabled tasks. Tasks will still use locking to prevent concurrent execution of the same task - even on clusters. The format of the &lt;task&gt; argument must be the same as returned by the --list option above.<br /> <br /> --disable=&lt;task&gt; - Disables a single scheduled task. The format of the &lt;task&gt; argument must be the same as returned by the --list option above.<br /> <br /> --enable=&lt;task&gt; - Enables a single scheduled task. The format of the &lt;task&gt; argument must be the same as returned by the --list option above.<br /> <br /> --showsql - Shows sql queries before they are execute<br /> <br /> --showdebugging - Shows developer debugging info<br /> '''Note:''' You must escape the &quot;\&quot; with an extra \ when using the --execute command. Take the following for example:<br /> &lt;pre&gt;php admin/cli/scheduled_task.php --list&lt;/pre&gt;<br /> will return something like:<br /> &lt;pre&gt;<br /> == List of scheduled tasks (http://yourserver.com/moodle) ==<br /> \enrol_imsenterprise\task\cron_task 10 * * * * * ASAP<br /> \logstore_legacy\task\cleanup_task * 5 * * * * ASAP<br /> \logstore_standard\task\cleanup_task * 4 * * * * Wednesday, November 12, 2014, 4:35 AM<br /> \mod_forum\task\cron_task * * * * * * ASAP<br /> \core\task\automated_backup_task 50 * * * * * ASAP<br /> <br /> ...<br /> &lt;/pre&gt;<br /> To run the first task in that list, you would execute<br /> php admin/cli/scheduled_task.php --execute='\enrol_imsenterprise\task\cron_task'<br /> Be aware of the single quotes. Without them, you would need to use double backlashes to avoid escaping by the shell.<br /> ===Ad hoc tasks===<br /> [[Cron#Low_latency_adhoc_tasks|Ad hoc tasks]] are low-latency tasks that are normally run by the cron. You can run just the queued ad hoc tasks with admin/cli/adhoc_task.php.<br /> <br /> This script accepts the following options and arguments:<br /> &lt;pre&gt;<br /> -h, --help Print out this help<br /> --showsql Show sql queries before they are executed<br /> --showdebugging Show developer level debugging information<br /> -e, --execute Run all queued adhoc tasks<br /> -k, --keep-alive=N Keep this script alive for N seconds and poll for new adhoc tasks<br /> -i --ignorelimits Ignore task_adhoc_concurrency_limit and task_adhoc_max_runtime limits<br /> -f, --force Run even if cron is disabled<br /> &lt;/pre&gt;<br /> For example to run the currently queued ad hoc tasks:<br /> sudo -u apache php admin/cli/adhoc_task.php -e<br /> <br /> See also the improvements to ad hoc tasks in [[Scheduled_tasks#Ad_hoc_tasks]]<br /> <br /> ==Database transfer==<br /> A command line script for [[Database transfer]] may be found in ''admin/tool/dbtransfer/cli/migrate.php''.<br /> ==Purge caches ==<br /> You can purge caches using this script:<br /> php admin/cli/purge_caches.php<br /> ==Kill all sessions==<br /> If needed for administrative reasons, you can kill all user sessions using this script:<br /> php admin/cli/kill_all_sessions.php<br /> As a result, all users will be logged out from Moodle.<br /> ==Backup, restore and import of courses or modules==<br /> See Backup via CLI in [[Course backup]] and Restore via CLI in [[Course restore]] (new in 3.10 onwards). Courses or individual modules can be copied directly on the command line with import.php (in 4.4 onwards). See Import via CLI in [[Course copy]].<br /> <br /> ==Deleting courses==<br /> Courses can be deleted via CLI if you know the course id:<br /> sudo -u www-data /usr/bin/php admin/cli/delete_course.php --courseid=123456<br /> <br /> ==Fix course / module sequences==<br /> In rare cases (such as after upgrading from a very old version of Moodle), the course / section / module sequence data can be out of sync. This can cause various problems for affected courses, such as sections not appearing, backups failing, pages not displaying etc. There is a specific check to check for errors caused by this problem, and to fix the data in the database if they are found. To run this script please use the command below:<br /> php admin/cli/fix_course_sequence.php -c=* --fix<br /> This will check every course in Moodle and report which ones had errors and were fixed.<br /> ==Fix orphaned question categories==<br /> When a quiz is created, a new question category for the quiz is automatically created. In versions of Moodle prior to 2.9.1, if the quiz is deleted, the question category and any questions in the category remain in database. These orphaned question categories may be fixed by running the admin/cli/fix_orphaned_question_categories.php script with the --fix option.<br /> == Search and replace text==<br /> This script can be used to search and replace text throughout the whole database. Use carefully and backup first always. More info in [[Search and replace tool]].<br /> php admin/tool/replace/cli/replace.php --search=//oldsitehost --replace=//newsitehost<br /> ==Build theme CSS cache==<br /> If Moodle is not running in theme designer mode it will keep a copy of the compiled CSS on local disk and serve that to the browser when it requests a page. If there isn't a copy on local disk then a copy will be built the first time a page within Moodle is requested. <br /> <br /> With this script you can pre-compile the cached CSS files for themes within Moodle to avoid having a user wait for the theme to compile during the first page request.<br /> php admin/cli/build_theme_css.php --themes=boost<br /> ==Get and set configuration values==<br /> Displays the current value of the given setting, or set the given setting to the specified value.<br /> $ php admin/cli/cfg.php [--component=&lt;componentname&gt;] [--json] [--shell-arg]<br /> $ php admin/cli/cfg.php --name=&lt;configname&gt; [--component=&lt;componentname&gt;] [--shell-arg] [--no-eol]<br /> $ php admin/cli/cfg.php --name=&lt;configname&gt; [--component=&lt;componentname&gt;] --set=&lt;value&gt;<br /> $ php admin/cli/cfg.php --name=&lt;configname&gt; [--component=&lt;componentname&gt;] --unset<br /> $ php admin/cli/cfg.php [--help|-h]<br /> Examples:<br /> $ php admin/cli/cfg.php --name=langmenu<br /> will display the value of ''Display language menu'' in ''Site administration &gt; Language &gt; Language settings'' (0 for ''No'' or 1 for ''Yes'').<br /> $ php cfg.php --name=maxsizetodownload --component=folder<br /> will display the value of ''Maximum folder download size (MB)'' accessible from ''Site administration &gt; Plugins &gt; Activity modules &gt; Folder''.<br /> $ php admin/cli/cfg.php --name=langmenu --set=0<br /> will disable the ''Language menu''.<br /> ==E-mail flag for users== <br /> '''New in 4.2''' <br /> The CLI script to change the email flag for one or many users at a time can be found on the page [[E-Mail flag for users]]<br /> <br /> ==Dashboard reset==<br /> If you make changes to the dashboard and want all users to have their dashboard reset to reflect the changes this can be done on the cli:<br /> php admin/cli/dashboard_reset.php -e<br /> <br /> ==Managing plugins via command line ==<br /> ===List and uninstall Moodle plugins===<br /> Moodle includes a handy command-line tool to display a list of plugins and remove plugins.<br /> $ php admin/cli/uninstall_plugins.php<br /> This command line tool accepts the following arguments.<br /> <br /> Options:<br />     -h --help                   Print this help.<br />     --show-all                  Displays a list of all installed plugins.<br />     --show-contrib              Displays a list of all third-party installed plugins.<br />     --show-missing              Displays a list of plugins missing from disk.<br />     --purge-missing             Uninstall all missing from disk plugins.<br />     --plugins=&lt;plugin name&gt;     A comma separated list of plugins to be uninstalled. E.g. mod_assign,mod_forum<br />     --run                       Execute uninstall. If this option is not set, then the script will be run in a dry mode.<br />     --showsql                   Show sql queries before they are executed.<br />     --showdebugging             Show developer level debugging information.<br /> Dry Mode does everything the script would normally do except for actually making any changes. This is useful when you want to test the validity of your command.<br /> <br /> Run this command from the Moodle wwwroot directory. Here are some examples:<br />     # php admin/cli/uninstall_plugins.php  --show-all<br />         Prints tab-separated list of all installed plugins.<br />     # php admin/cli/uninstall_plugins.php  --show-contrib<br />         Prints tab-separated list of all third-party installed plugins.<br />     # php admin/cli/uninstall_plugins.php  --show-missing<br /> &lt;blockquote&gt;        Prints tab-separated list of all missing from disk plugins.&lt;/blockquote&gt;<br />     # php admin/cli/uninstall_plugins.php  --purge-missing<br />         A dry run of uninstalling all missing plugins. This will NOT uninstall the plugin. To actually uninstall, you need to add the '--run' arguments.<br />     # php admin/cli/uninstall_plugins.php  --purge-missing --run<br />         Run uninstall of all missing plugins.<br />     # php admin/cli/uninstall_plugins.php  --plugins=mod_assign,mod_forum<br />         A dry run of uninstalling mod_assign and mod_forum plugins. This will NOT uninstall the plugin. To actually uninstall, you need to add the '--run' arguments.<br />     # php admin/cli/uninstall_plugins.php  --plugins=mod_assign,mod_forum --run<br />         Run uninstall for mod_assign and mod_forum plugins.<br /> <br /> This tool does not perform all of the steps needed to fully uninstall a plugin. You must then:<br /> *Remove the files belonging to the plugin manually;<br /> *[[Administration via command line#Upgrading|Update the Moodle database]] as previously described.<br /> If you skip one or both of these steps, you will be prompted to update the Moodle database or re-install the plugin the next time you log in as a site administrator and access the Site Administration &gt; Notifications page.<br /> <br /> ==See also==<br /> *MDL-35736 - Manage plugins via command-line<br /> *MDL-36237 - Resort course list via CLI<br /> *[http://moosh-online.com/ MOOSH] - MOOdle SHell. It is a command-line tool that will allow you to perform many of the most common Moodle tasks.<br /> [[fr:Administration en ligne de commande]]<br /> [[de:Administration über Kommandozeile]]<br /> [[es:Administración por línea de comando]]<br /> [[it:Amministrazione via linea di comando]]<br /> [[ja:コマンドライン経由の管理]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=150847 2025-01-09T04:16:41Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=463717 Plenary meeting activity]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The '''Plenary meeting''' activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has an integration with [[Deft response]] block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for [https://jitsi.org Jitsi meet].<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until this happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available. Whether seconds are required for a type of motion can be configured by the admin for the site.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss the question before less privileged motions.<br /> <br /> ==Meeting forms==<br /> The activity can configured for use in different contexts to be selected in the activity settings. This is done with meeting form plugins. The following meeting forms are included.<br /> <br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a [https://jitsi.org Jitsi Meet] server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> A newer integration is being developed to Jitsi Meet that provides better integration with the activity. The behavior will be similarto the Deft integration, but able to work with self hosted Jitsi meet servers.<br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> === Moodle App support ===<br /> The Moodle Mobile App is supported by the activity. Participants can use the app to create, view and modify motions. The Deft meeting form allows watching other speakers, but not speaking.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> = Additional configuration =<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> == Configuring Deft integration ==<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> == Jitsi Meet ==<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from the developer at [https://deftly.us deftly.us] if you are unable to install locally. There are some additional features that are also available. You can create a free account there and a sample course from the user dashboard, and then submit a site support request for LTI Access.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Deft&diff=150846 2025-01-09T04:11:45Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Block<br /> |entry = https://moodle.org/plugins/block_deft<br /> |tracker = https://github.com/dthies/moodle-block_deft/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=436763 Deft response block]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]], [[Stefan Scholz]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The ''Deft response'' block allows a Manager or Editing teacher to create multiple tasks consisting of short texts, discussions, polls, audio conferences and control remotely which ones are displayed and how students may interact with them.<br /> There is a external service that is available to push notifications to clients to update content. This can be configured easily from the plugin and is free for limited usage. Larger sites may need a service agreement in the future. More information and demos are available at [https://deftly.us Deftly.us].<br /> == Managing tasks ==<br /> The block can be added the usual way to a block or course by a user with the Add instance capability. If the user has block/deft:edit or block/deft:manage capability on the block, a Manage button will appear in the block. Clicking the button opens a Manage Tasks dashboard for the block instance. Teachers can make the tasks visible and adjust other parameters on the dashboard and changes will by visible in learners' browsers.<br /> === Defining Tasks ===<br /> If a user has block/deft:edit capability, the dashboard should also have an ''Add text'', ''Add comments'', ''Add choice'', and ''Add venue'' button. Clicking one of the buttons opens a modal form to define a new task. Tasks should be named in a way that helps distinguish them from each other on the dashboard. When the form is saved a task card will appear on the dashboard, but the task will not be visible yet in the block.<br /> ==== Choice ====<br /> [[File:edit choice.png|thumb|Editing Deft Choice on dashboard]]<br /> The choice task allows teachers to poll a class. The editing form defines the a question or prompt and short response that will be available for the students to choose.<br /> ==== Text ====<br /> The text tasks contains simple text that can be later be displayed in the block individually. The text area can contain multiple lines and simple html formatting, urls that may display as links, emoticons, but no media tags.<br /> ==== Comments ====<br /> The Comments task allow student to respond in the block and interact with each other. With the active updates, students can see comments in real time. This allows the block to be used for small discussions or chats. More than one Comments can be added to handle separate or group discussions. The individual task can be shown or hidden to start or moderate the discussions.<br /> The order of the tasks can be arranged. All task are initially hidden from view in the block.<br /> ==== Venue ====<br /> [[File:venue.png|thumb|Users in Venue]]<br /> The Venue task allows learners to converse with each other in a small audio chat format. Each venue is a separate place that a group of students can meet. When the teacher makes the task visible, a button is displayed on the block. When users click the button, they enter the venue and are connected with any other users already present using a peer-to-peer WebRTC audio connection.<br /> <br /> A venue can also be configured to use a bridged connection. Audio is connected through a central server to allow more participants and provide better quality. A teacher or others may also be allowed to stream video in the venue. An appropriate service agreement may be required to use the bridge server.<br /> === Deploying tasks ===<br /> [[File:task dashboard.png|thumb|Manage tasks dashboard|alt=]]<br /> A non-editing teacher, teacher, manager or any role with block/deft:manage capability will see a Manage button on the Deft response block. Clicking the button will open the manage task dashboard and change display options for the tasks. The user will not be able to create, edit or move task without the block/deft:edit capability.<br /> Display options can be changed with a form that appears on the task card. Changes will be visible only after they are submitted. <br /> == Installation and initial setup ==<br /> === Installation ===<br /> There are several options how to install the deft response block:<br /> ==== Option 1: Install from Moodle.org ====<br /> * Login as an admin and go to Site administration &gt; Plugins &gt; Install plugins. (If you can't find this location, then plugin installation is prevented on your site.)<br /> * Click the button 'Install plugins from Moodle plugins directory'.<br /> * Search for &quot;Deft response&quot;, click the Install button then click Continue.<br /> * Confirm the installation request<br /> * Check the plugin validation report<br /> ==== Option 2: Install from zip package ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Login to your Moodle site as an admin and go to Administration &gt; Site administration &gt; Plugins &gt; Install plugins.<br /> * Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if the plugin is not automatically detected.<br /> * If your target directory is not writeable, you will see a warning message.<br /> * Check the plugin validation report<br /> ==== Option 3: Install manually on server ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Upload or copy it to your Moodle server.<br /> * Unzip it in the `/blocks` directory.<br /> * In your Moodle site (as admin) go to Settings &gt; Site administration &gt; Notifications (you should, for most plugin types, get a message saying the plugin is installed).<br /> For more detailed info, visit &lt;nowiki&gt;https://docs.moodle.org/400/en/Installing_plugins&lt;/nowiki&gt;<br /> === Initial setup ===<br /> &lt;code&gt;All features of the Deft Response block will now work, but they won't be instant i.e. the page won't auto-update until the registration has been completed.&lt;/code&gt;<br /> ==== Automatic registration ====<br /> * [[File:Deft activaition.png|thumb|Service Activation]]After the installation, please go to Administration &gt; Site administration &gt; Plugins &gt; Blocks &gt; Deft response<br /> * On this page, tick &quot;Enable updating&quot; checkbox and save and a activation button should appear.<br /> * Press the &quot;Activation&quot; button. This should create automatically a preconfigured external tool in Activities -&gt; External tool -&gt; Register tools to deftly.<br /> * A table showing usage will then be shown in the block settings instead of the button.<br /> <br /> <br /> You should now be able to add then block to a course or module and when tasks are changed they will be updated in all browsers where they are displayed.<br /> <br /> If that's not the case (i.e. tasks don't update instantly), automatic registration has probably not worked correctly and registration needs to be completed manually (see below).<br /> <br /> ==== Manual registration ====<br /> If automatic registration has failed, please sign up (free) for the deft service agreement on this page: https://bdecent.de/product/deft-service-agreement/<br /> <br /> We will contact you (via email) and provide you with all the information that you need to complete the manual registration.<br /> <br /> <br /> [[es:Ágil]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=150280 2024-11-27T15:04:13Z

<p>Dthies: /* Open meeting */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=463717 Plenary meeting activity]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The '''Plenary meeting''' activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has an integration with [[Deft response]] block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for [https://jitsi.org Jitsi meet].<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until this happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available. Whether seconds are required for a type of motion can be configured by the admin for the site.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss the question before less privileged motions.<br /> <br /> ==Meeting forms==<br /> The activity can configured for use in different contexts to be selected in the activity settings. This is done with meeting form plugins. The following meeting forms are included.<br /> <br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a [https://jitsi.org Jitsi Meet] server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> === Moodle App support ===<br /> The Moodle Mobile App is supported by the activity. Participants can use the app to create, view and modify motions. The Deft meeting form allows watching other speakers, but not speaking.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> = Additional configuration =<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> == Configuring Deft integration ==<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> == Jitsi Meet ==<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from the developer at [https://deftly.us deftly.us] if you are unable to install locally. There are some additional features that are also available. You can create a free account there and a sample course from the user dashboard, and then submit a site support request for LTI Access.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=150116 2024-11-13T20:33:45Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=463717 Plenary meeting activity]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The '''Plenary meeting''' activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has an integration with [[Deft response]] block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for [https://jitsi.org Jitsi meet].<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss to question.<br /> <br /> ==Meeting forms==<br /> The activity can configured for use in different contexts to be selected in the activity settings. This is done with meeting form plugins. The following meeting forms are included.<br /> <br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a [https://jitsi.org Jitsi Meet] server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> === Moodle App support ===<br /> The Moodle Mobile App is supported by the activity. Participants can use the app to create, view and modify motions. The Deft meeting form allows watching other speakers, but not speaking.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> = Additional configuration =<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> == Configuring Deft integration ==<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> == Jitsi Meet ==<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from the developer at [https://deftly.us deftly.us] if you are unable to install locally. There are some additional features that are also available. You can create a free account there and a sample course from the user dashboard, and then submit a site support request for LTI Access.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Popup_activities_course_format&diff=150093 2024-11-11T13:44:00Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Course formats<br /> |entry = https://moodle.org/plugins/format_popups<br /> |tracker = https://github.com/dthies/moodle-format_popups/issues<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=420525<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> The Pop up activities course format displays resources and simple activities embedded in modals instead of redirecting from the course page. Otherwise it behaves as the [[ Course formats#Topics_format | Topics format]].<br /> <br /> If you are not using heavy server side assessment, but mostly resources and client side activities (SCORM, H5P), this format may help provide more interactive courses by opening the activities in popup modals instead of separate web pages. When students finish an activity or resource, they return to the course page by closing the modal without waiting for the course page to load again. The course page updates activity completion and availability when the modal is closed. <br /> <br /> This plugin uses javascript to add AJAX functionality to the standard topics format. Otherwise the format is the same as the [[ Course formats#Topics_format | Topics format]]. Currently [[Book]], [[Choice]], [https://moodle.org/plugins/mod_customcert Custom certificate ], [https://moodle.org/plugins/mod_etherpadlite Etherpad lite], [[File resource]], [[Folder]], [[H5P activity]], [[Page]], [https://moodle.org/plugins/mod_poster Poster], [[SCORM]], [[URL]], and [[VideoTime|Video Time]] activities are supported and can be displayed in modals. Other activities will open normally.<br /> <br /> Developers should be able to add similar functionality to other formats by copying the AMD call in format.php and adding this format as a dependency.<br /> == Capability ==<br /> Users will only see the popups for the supported activities if they have the capability 'format/popups:view' in the modules context. By default students have this capability. It can be given to other roles or removed at course or activity level.<br /> <br /> == Deft response integration ==<br /> This format includes an optional integration is with [[Deft response]] block that can enable the course page to be updated when something happens in the background that affects it, for example activity or completion changes.<br /> <br /> ==Configuration==<br /> When editing course settings select ''Popup activities'' under Course format. Other options are the same as Topics format. Teachers by default will not see popups, but students will. This can be changed by editing the role and changing permissions for capability format/popups:view.<br /> <br /> There are some site administration settings available to change navigation. Navigation links can added to the previous and next activities may be added to the bottom of the popups. In Moodle 4.0+ administrators can choose whether the course index will be available in this format or not.<br /> ==Demo Course==<br /> A demonstration course is available on the developer's site https://openlearner.org/popups.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Popup_activities_course_format&diff=150092 2024-11-11T13:35:07Z

<p>Dthies: /* Deft response integration */</p> <hr /> <div>{{Infobox plugin<br /> |type = Course formats<br /> |entry = https://moodle.org/plugins/format_popups<br /> |tracker = https://github.com/dthies/moodle-format_popups/issues<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=420525<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> The Pop up activities course format displays resources and simple activities embedded in modals instead of redirecting from the course page. Otherwise it behaves as the [[ Course formats#Topics_format | Topics format]].<br /> <br /> If you are not using heavy server side assessment, but mostly resources and client side activities (SCORM, H5P), this format may help provide more interactive courses by opening the activities in popup modals instead of separate web pages. When students finish an activity or resource, they return to the course page by closing the modal without waiting for the course page to load again. The course page updates activity completion and availability when the modal is closed. <br /> <br /> This plugin uses javascript to add AJAX functionality to the standard topics format. Otherwise the format is the same as the [[ Course formats#Topics_format | Topics format]]. Currently [[Book]], [[Choice]], [https://moodle.org/plugins/mod_customcert Custom certificate ], [https://moodle.org/plugins/mod_etherpadlite Etherpad lite], [[File resource]], [[Folder]], [[H5P activity]], [[Page]], [https://moodle.org/plugins/mod_poster Poster], [[SCORM]], [[URL]], and [[VideoTime|Videotime]] activities are supported and can be displayed in modals. Other activities will open normally.<br /> <br /> Developers should be able to add similar functionality to other formats by copying the AMD call in format.php and adding this format as a dependency.<br /> == Capability ==<br /> Users will only see the popups for the supported activities if they have the capability 'format/popups:view' in the modules context. By default students have this capability. It can be given to other roles or removed at course or activity level.<br /> <br /> == Deft response integration ==<br /> This format includes an optional integration is with [[Deft response]] block that can enable the course page to be updated when something happens in the background that affects it, for example activity or completion changes.<br /> <br /> ==Configuration==<br /> When editing course settings select ''Popup activities'' under Course format. Other options are the same as Topics format. Teachers by default will not see popups, but students will. This can be changed by editing the role and changing permissions for capability format/popups:view.<br /> <br /> There are some site administration settings available to change navigation. Navigation links can added to the previous and next activities may be added to the bottom of the popups. In Moodle 4.0+ administrators can choose whether the course index will be available in this format or not.<br /> ==Demo Course==<br /> A demonstration course is available on the developer's site https://openlearner.org/popups.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Popup_activities_course_format&diff=150091 2024-11-11T13:33:29Z

<p>Dthies: /* Capability */</p> <hr /> <div>{{Infobox plugin<br /> |type = Course formats<br /> |entry = https://moodle.org/plugins/format_popups<br /> |tracker = https://github.com/dthies/moodle-format_popups/issues<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=420525<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> The Pop up activities course format displays resources and simple activities embedded in modals instead of redirecting from the course page. Otherwise it behaves as the [[ Course formats#Topics_format | Topics format]].<br /> <br /> If you are not using heavy server side assessment, but mostly resources and client side activities (SCORM, H5P), this format may help provide more interactive courses by opening the activities in popup modals instead of separate web pages. When students finish an activity or resource, they return to the course page by closing the modal without waiting for the course page to load again. The course page updates activity completion and availability when the modal is closed. <br /> <br /> This plugin uses javascript to add AJAX functionality to the standard topics format. Otherwise the format is the same as the [[ Course formats#Topics_format | Topics format]]. Currently [[Book]], [[Choice]], [https://moodle.org/plugins/mod_customcert Custom certificate ], [https://moodle.org/plugins/mod_etherpadlite Etherpad lite], [[File resource]], [[Folder]], [[H5P activity]], [[Page]], [https://moodle.org/plugins/mod_poster Poster], [[SCORM]], [[URL]], and [[VideoTime|Videotime]] activities are supported and can be displayed in modals. Other activities will open normally.<br /> <br /> Developers should be able to add similar functionality to other formats by copying the AMD call in format.php and adding this format as a dependency.<br /> == Capability ==<br /> Users will only see the popups for the supported activities if they have the capability 'format/popups:view' in the modules context. By default students have this capability. It can be given to other roles or removed at course or activity level.<br /> <br /> == Deft response integration ==<br /> This format in integration is with [[Deft response]] block that can enable the course page to be updated when something happens in the background that affects it, for example activity or completion changes.<br /> <br /> ==Configuration==<br /> When editing course settings select ''Popup activities'' under Course format. Other options are the same as Topics format. Teachers by default will not see popups, but students will. This can be changed by editing the role and changing permissions for capability format/popups:view.<br /> <br /> There are some site administration settings available to change navigation. Navigation links can added to the previous and next activities may be added to the bottom of the popups. In Moodle 4.0+ administrators can choose whether the course index will be available in this format or not.<br /> ==Demo Course==<br /> A demonstration course is available on the developer's site https://openlearner.org/popups.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149961 2024-11-01T11:28:26Z

<p>Dthies: /* Introduction */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The '''Plenary meeting''' activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has an integration with [[Deft response]] block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for [https://jitsi.org Jitsi meet].<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss to question.<br /> <br /> ==Meeting forms==<br /> The activity can configured for use in different contexts to be selected in the activity settings. This is done with meeting form plugins. The following meeting forms are included.<br /> <br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a [https://jitsi.org Jitsi Meet] server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> === Moodle App support ===<br /> The Moodle Mobile App is supported by the activity. Participants can use the app to create, view and modify motions. The Deft meeting form allows watching other speakers, but not speaking.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> = Additional configuration =<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> == Configuring Deft integration ==<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> == Jitsi Meet ==<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from the developer at [https://deftly.us deftly.us] if you are unable to install locally. There are some additional features that are also available. You can create a free account there and a sample course from the user dashboard, and then submit a site support request for LTI Access.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=mod/plenum/view&diff=149959 2024-11-01T04:29:59Z

<p>Dthies: Redirected page to Plenary meeting</p> <hr /> <div>#REDIRECT [[Plenary meeting]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=mod/plenum/view&diff=149958 2024-11-01T04:23:15Z

<p>Dthies: </p> <hr /> <div>|Plenary meeting</div>

Dthies https://docs.moodle.org/501/en/index.php?title=mod/plenum/view&diff=149957 2024-11-01T04:22:20Z

<p>Dthies: Created page with &quot;#Plenary meeting&quot;</p> <hr /> <div>#Plenary meeting</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149794 2024-10-25T20:45:38Z

<p>Dthies: /* Jitsi meet */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss to question.<br /> <br /> ==Meeting forms==<br /> The activity can configured for use in different contexts to be selected in the activity settings. This is done with meeting form plugins. The following meeting forms are included.<br /> <br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a [https://jitsi.org Jitsi Meet] server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> === Moodle App support ===<br /> The Moodle Mobile App is supported by the activity. Particpants can use the app to create, view and modify motions. The Deft meeting form allows watching other speakers, but not speaking.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> = Additional configuration =<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> == Configuring Deft integration ==<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> == Jitsi Meet ==<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from the developer at [https://deftly.us deftly.us] if you are unable to install locally. There are some additional features that are also available. You can create a free account there and a sample course from the user dashboard, and then submit a site support request for LTI Access.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149793 2024-10-25T19:12:53Z

<p>Dthies: /* LTI Usage */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss to question.<br /> <br /> ==Meeting forms==<br /> The activity can configured for use in different contexts to be selected in the activity settings. This is done with meeting form plugins. The following meeting forms are included.<br /> <br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> === Moodle App support ===<br /> The Moodle Mobile App is supported by the activity. Particpants can use the app to create, view and modify motions. The Deft meeting form allows watching other speakers, but not speaking.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> = Additional configuration =<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> == Configuring Deft integration ==<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> == Jitsi Meet ==<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from the developer at [https://deftly.us deftly.us] if you are unable to install locally. There are some additional features that are also available. You can create a free account there and a sample course from the user dashboard, and then submit a site support request for LTI Access.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149792 2024-10-25T19:08:12Z

<p>Dthies: /* Meeting forms */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss to question.<br /> <br /> ==Meeting forms==<br /> The activity can configured for use in different contexts to be selected in the activity settings. This is done with meeting form plugins. The following meeting forms are included.<br /> <br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> === Moodle App support ===<br /> The Moodle Mobile App is supported by the activity. Particpants can use the app to create, view and modify motions. The Deft meeting form allows watching other speakers, but not speaking.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> = Additional configuration =<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> == Configuring Deft integration ==<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> == Jitsi Meet ==<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from the developer at deftly.us if you are unable to install locally. There are some additional features that are also available. You can create a free account there and a sample course from the user dashboard, and then submit a site support request for LTI Access.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149706 2024-10-21T00:26:13Z

<p>Dthies: /* Introduction */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss to question.<br /> <br /> ==Meeting forms==<br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> === Moodle App support ===<br /> The Moodle Mobile App is supported by the activity. Particpants can use the app to create, view and modify motions. The Deft meeting form allows watching other speakers, but not speaking.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> = Additional configuration =<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> == Configuring Deft integration ==<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> == Jitsi Meet ==<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from the developer at deftly.us if you are unable to install locally. There are some additional features that are also available. You can create a free account there and a sample course from the user dashboard, and then submit a site support request for LTI Access.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149702 2024-10-20T03:58:39Z

<p>Dthies: /* Completion conditions */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss to question.<br /> <br /> ==Meeting forms==<br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> === Moodle App support ===<br /> The Moodle Mobile App is supported by the activity. Particpants can use the app to create, view and modify motions. The Deft meeting form allows watching other speakers, but not speaking.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> = Additional configuration =<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> == Configuring Deft integration ==<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> == Jitsi Meet ==<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from the developer and deftly.us if you are unable to install locally which also has some additional features. You can create a free account there and a sample course from the user dashboard, and then submit a site support request for LTI Access.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149700 2024-10-19T18:41:17Z

<p>Dthies: /* LTI Usage */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss to question.<br /> <br /> ==Meeting forms==<br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> = Additional configuration =<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> == Configuring Deft integration ==<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> == Jitsi Meet ==<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from the developer and deftly.us if you are unable to install locally which also has some additional features. You can create a free account there and a sample course from the user dashboard, and then submit a site support request for LTI Access.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149699 2024-10-19T17:27:28Z

<p>Dthies: /* Installing via uploaded ZIP file */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss to question.<br /> <br /> ==Meeting forms==<br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> = Additional configuration =<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> == Configuring Deft integration ==<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> == Jitsi Meet ==<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from deftly.us if you are unable to install locally which also has some additional features.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149698 2024-10-19T17:25:49Z

<p>Dthies: /* LTI Usage */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss to question.<br /> <br /> ==Meeting forms==<br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> == Additional configuration ==<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> ==== Configuring Deft integration ====<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> === Jitsi Meet ===<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> = LTI Usage =<br /> LTI service is available from deftly.us if you are unable to install locally which also has some additional features.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149697 2024-10-19T17:24:32Z

<p>Dthies: /* Installing via uploaded ZIP file */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss to question.<br /> <br /> ==Meeting forms==<br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> == Additional configuration ==<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> ==== Configuring Deft integration ====<br /> The Deft meeting form requires that the Deft response block is installed and configured to provide content updating and Audio and Video conferencing. The deftly.us site provides a message service and media service access to make the conferencing experience work. The admin will need to activate the service and video bridging in the Deft response block sit admin settings, and then go to the Plenary meeting -&gt; Meeting form plugins settings page and enable the Deft integration plugin. If you are wanting to us this on a production site which requires a reliable capacity contact deftly.us for a user agreement.<br /> <br /> === Jitsi Meet ===<br /> This plugin provides an optional minimal integration for Jitsi Meet. A Jitsi Meet room is embedded on the activity page and users are authenticated from Moodle to use the room. First obtain access for a secure Jitsi server. You should receive an app ID, secret, and server url. The admin should add these to the Jitsi Meet form plugin settings, and enable the plugin on the management page. The teacher will then be able to select Jitsi as the meeting form in the activity settings and set a room name to let the participants use the integration.<br /> <br /> === LTI Usage ===<br /> LTI service is available from deftly.us if you are unable to install locally which also has some additional features.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149696 2024-10-19T16:00:52Z

<p>Dthies: /* Group support */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss to question.<br /> <br /> ==Meeting forms==<br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> The Plenary meeting supports Moodle groups. When group mode is enabled for the activity motions are separated by group so that independent meetings can be run simultaneously in one activity. Users only see motions in the selected activity group. Deft and Jitsi integrations will have separate rooms assigned to each groups so users only hear and see the activity in the selected group.<br /> <br /> === Assessment ===<br /> The activity may be graded to provide feedback to the participants in the Moodle gradebook. This may be used to contribute to a course grade or simply to provide individual feedback to meeting participants. The advanced grading methods in Moodle are supported. The grading interface provides a report on individual users activity in a meeting.<br /> <br /> === Completion conditions ===<br /> Some activity completions available to track user participation when the view activity or submit motions.<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> === Additional configuration ===<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> === LTI Usage ===<br /> LTI service is available from deftly.us if you are unable to install locally which also has some additional features.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149695 2024-10-19T15:18:38Z

<p>Dthies: /* Resolutions */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> Users can raise a Point of Order to address an action of the chair at any time while other business is pending by clicking the 'Order' motion. The chair will have to recognize or dismiss to question.<br /> <br /> ==Meeting forms==<br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> == Additional features ==<br /> <br /> === Group support ===<br /> <br /> === Assessment ===<br /> <br /> === Completion conditions ===<br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> === Additional configuration ===<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> === LTI Usage ===<br /> LTI service is available from deftly.us if you are unable to install locally which also has some additional features.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149693 2024-10-19T03:23:33Z

<p>Dthies: /* Jitsi meet */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> ==Meeting forms==<br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Speakers must be moderated with the tools in the Jitsi interface. Speakers are not automatically queued. So actions in Jitsi are recorded in the Moodle logs including users joining the meeting and raising hands. <br /> <br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.<br /> <br /> === Additional configuration ===<br /> Motions may be customized in the plugin site administration settings. Motion types are subplugins that may be individually enabled or disabled in Plugins &gt; Activities &gt; Plenary meeting &gt; Motion types. Some of the motion types have additional settings which can be modified to fit local parliamentary variations.<br /> <br /> There are also different Meeting form plugins that can be managed. If more than one is enabled, teachers will be able to choose which to use in the activity settings. The Basic form is enabled by default. Before enabling Deft form, the admin should configure Deft response block and enable the updating and video service from deftly.us. If using Jitsi form is used, access to a Jitsi Meet server must be configured.<br /> <br /> LTI Usage<br /> <br /> LTI service is available from deftly.us if you are unable to install locally which also has some additional features.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149692 2024-10-19T02:14:35Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> = Features =<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> ==Meeting forms==<br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Users will have to <br /> <br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149691 2024-10-19T02:12:59Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> = Introduction =<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> = Features =<br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> ==Making motions==<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ===Open meeting===<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ===Resolutions===<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ===Amendments===<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ===Seconds===<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ===Privileged motions===<br /> ==Meeting forms==<br /> ===Basic meeting===<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ===Deft meeting===<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ===Jitsi meet===<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Users will have to <br /> <br /> <br /> =Installing via uploaded ZIP file=<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149690 2024-10-19T01:27:15Z

<p>Dthies: /* Resolutions */</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> ===Making motions===<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ====Open meeting====<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ====Resolutions====<br /> Once the meeting has been opened, participants can offer a motion to be considered by the group. A use click 'Resolve' button and completes a modal form to supply the content of the motion either as text or in an attached file. After form is saved it is either accepted or denied by the chair or queued immediately depending on the activity configured. Once on the floor, it will appear on the activity page for other users to view. If required other users will be given the opportunity to second the resolution before it is placed on the floor for debate.<br /> <br /> ====Amendments====<br /> Once a resolution or main motion is on the floor, participants will be able to offer amendments to motion to make modifications.<br /> <br /> ====Seconds====<br /> Resolutions, amendments and motions to adjourn may be configured to require a second. If a motion requires a second, a different user than the one offering the amendment must click the second button before normal users can do anything else with it. The chair can remove it if no second is available.<br /> <br /> ====Privileged motions====<br /> ===Meeting forms===<br /> ====Basic meeting====<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ====Deft meeting====<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ====Jitsi meet====<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Users will have to <br /> <br /> <br /> ===Installing via uploaded ZIP file===<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149689 2024-10-19T00:29:50Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> ===Making motions===<br /> Users participate in the meetings by offering motions. The presiding officer determines which motions are considered. <br /> <br /> The motions that are available are configured by the admin in the site settings.<br /> <br /> ====Open meeting====<br /> Before the meeting may begin, a presiding officer must open the meeting. Other users will not be able to offer any motions until the happens.<br /> <br /> ====Resolutions====<br /> ====Amendments====<br /> ====Seconds====<br /> ====Privileged motions====<br /> ===Meeting forms===<br /> ====Basic meeting====<br /> The basic meeting form is enabled by default and is appropriate for in person meetings where users are in the same run or have an external method of communication. Users can offer motions and vote using the activity so that there is a record stored of the meetings official proceedings, but audio or video is not integrated (although a Deft response block audio venue can be added).<br /> ====Deft meeting====<br /> If Deft response block is configured with video support, the Chair and the person who has the floor can share audio and video to speak to the pending business.<br /> ====Jitsi meet====<br /> If a Jitsi Meet server is available the admin can configure it to work with the plugin. The activity will authorize the users to join a room which is shared on the activity page. Users will have to <br /> <br /> <br /> ===Installing via uploaded ZIP file===<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Plenary_meeting&diff=149688 2024-10-18T19:15:25Z

<p>Dthies: Created page with &quot;{{Infobox plugin |type = Activity |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum |tracker = https://github.com/dthies/moodle-mod_plenum/issues |maintainer = Daniel Thies |float = right }} == Introduction == The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer facul...&quot;</p> <hr /> <div>{{Infobox plugin<br /> |type = Activity<br /> |entry = https://moodle.org/plugins/view.php?plugin=mod_plenum<br /> |tracker = https://github.com/dthies/moodle-mod_plenum/issues<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The Plenary meeting activity module organizes online and in person meetings following traditional rules of parliamentary procedure. It may be used as a tool to teach skills to conduct a meeting or to structure and administer faculty, staff, student or other organizational meetings.<br /> <br /> Users are granted the privileges to speak, make motions, vote or chair meetings through Moodle capabilities and roles. The activity maintains a record of motions to provide meeting minutes. User actions are logged in Moodle log system.<br /> <br /> The activity can be used with an in person event or as an online event. It has a integration with Deft response block to allow audio and video to be shared based on whether the user is recognized to speak in the activity. Other web conference or media servers also can be used as long as users can be managed by them manually. A minimal integration is provided for Jitsi meet.<br /> <br /> ===Installing via uploaded ZIP file===<br /> Log in to your Moodle site as an admin and go to Site administration &gt; Plugins &gt; Install plugins.<br /> Upload the ZIP file with the plugin code and ZIP file for block Deft response. You should only be prompted to add extra details if your plugin type is not automatically detected.<br /> Check the plugin validation report and finish the installation.<br /> Installing manually<br /> The plugin can be also installed by putting the contents of this directory to<br /> <br /> {your/moodle/dirroot}/mod/plenum<br /> <br /> and place code for block Deft response in<br /> <br /> {your/moodle/dirroot}/blocks/deft<br /> <br /> Afterwards, log in to your Moodle site as an admin and 1. go to Site administration &gt; Notifications to complete the installation. 2. Adjust subplugin settings to accommodate variations in parliamentary procedure. 3. Install Block deft response or other conferencing integration dependency for online meeting support.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Popup_activities_course_format&diff=146082 2023-05-04T23:51:30Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Course formats<br /> |entry = https://moodle.org/plugins/format_popups<br /> |tracker = https://github.com/dthies/moodle-format_popups/issues<br /> |discussion = https://moodle.org/mod/forum/discuss.php?d=420525<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]]<br /> |float = right<br /> }}<br /> The Pop up activities course format displays resources and simple activities embedded in modals instead of redirecting from the course page. Otherwise it behaves as the [[ Course formats#Topics_format | Topics format]].<br /> <br /> If you are not using heavy server side assessment, but mostly resources and client side activities (SCORM, H5P), this format may help provide more interactive courses by opening the activities in popup modals instead of separate web pages. When students finish an activity or resource, they return to the course page by closing the modal without waiting for the course page to load again. The course page updates activity completion and availability when the modal is closed. <br /> <br /> This plugin uses javascript to add AJAX functionality to the standard topics format. Otherwise the format is the same as the [[ Course formats#Topics_format | Topics format]]. Currently [[Book]], [[Choice]], [https://moodle.org/plugins/mod_customcert Custom certificate ], [https://moodle.org/plugins/mod_etherpadlite Etherpad lite], [[File resource]], [[Folder]], [[H5P activity]], [[Page]], [https://moodle.org/plugins/mod_poster Poster], [[SCORM]], [[URL]], and [[VideoTime|Videotime]] activities are supported and can be displayed in modals. Other activities will open normally.<br /> <br /> Developers should be able to add similar functionality to other formats by copying the AMD call in format.php and adding this format as a dependency.<br /> == Capability ==<br /> Users will only see the popups for the supported activities if they have the capability 'format/popups:view' in the modules context. By default students have this capability. It can be given to other roles or removed at course or activity level.<br /> ==Configuration==<br /> When editing course settings select ''Popup activities'' under Course format. Other options are the same as Topics format. Teachers by default will not see popups, but students will. This can be changed by editing the role and changing permissions for capability format/popups:view.<br /> <br /> There are some site administration settings available to change navigation. Navigation links can added to the previous and next activities may be added to the bottom of the popups. In Moodle 4.0+ administrators can choose whether the course index will be available in this format or not.<br /> ==Demo Course==<br /> A demonstration course is available on the developer's site https://openlearner.org/popups.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Deft&diff=146059 2023-05-01T23:45:45Z

<p>Dthies: </p> <hr /> <div>{{Infobox plugin<br /> |type = Block<br /> |entry = https://moodle.org/plugins/view.php?plugin=block_deft<br /> |tracker = https://github.com/dthies/moodle-block_deft/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=436763 Deft response block]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]], [[Stefan Scholz]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The ''Deft response'' block allows a Manager or Editing teacher to create multiple tasks consisting of short texts, discussions, polls, audio conferences and control remotely which ones are displayed and how students may interact with them.<br /> There is a external service that is available to push notifications to clients to update content. This can be configured easily from the plugin and is free for limited usage. Larger sites may need a service agreement in the future. More information and demos are available at [https://deftly.us Deftly.us].<br /> == Managing tasks ==<br /> The block can be added the usual way to a block or course by a user with the Add instance capability. If the user has block/deft:edit or block/deft:manage capability on the block, a Manage button will appear in the block. Clicking the button opens a Manage Tasks dashboard for the block instance. Teachers can make the tasks visible and adjust other parameters on the dashboard and changes will by visible in learners' browsers.<br /> === Defining Tasks ===<br /> If a user has block/deft:edit capability, the dashboard should also have an ''Add text'', ''Add comments'', ''Add choice'', and ''Add venue'' button. Clicking one of the buttons opens a modal form to define a new task. Tasks should be named in a way that helps distinguish them from each other on the dashboard. When the form is saved a task card will appear on the dashboard, but the task will not be visible yet in the block.<br /> ==== Choice ====<br /> [[File:edit choice.png|thumb|Editing Deft Choice on dashboard]]<br /> The choice task allows teachers to poll a class. The editing form defines the a question or prompt and short response that will be available for the students to choose.<br /> ==== Text ====<br /> The text tasks contains simple text that can be later be displayed in the block individually. The text area can contain multiple lines and simple html formatting, urls that may display as links, emoticons, but no media tags.<br /> ==== Comments ====<br /> The Comments task allow student to respond in the block and interact with each other. With the active updates, students can see comments in real time. This allows the block to be used for small discussions or chats. More than one Comments can be added to handle separate or group discussions. The individual task can be shown or hidden to start or moderate the discussions.<br /> The order of the tasks can be arranged. All task are initially hidden from view in the block.<br /> ==== Venue ====<br /> [[File:venue.png|thumb|Users in Venue]]<br /> The Venue task allows learners to converse with each other in a small audio chat format. Each venue is a separate place that a group of students can meet. When the teacher makes the task visible, a button is displayed on the block. When users click the button, they enter the venue and are connected with any other users already present using a peer-to-peer WebRTC audio connection.<br /> <br /> A venue can also be configured to use a bridged connection. Audio is connected through a central server to allow more participants and provide better quality. A teacher or others may also be allowed to stream video in the venue. An appropriate service agreement may be required to use the bridge server.<br /> === Deploying tasks ===<br /> [[File:task dashboard.png|thumb|Manage tasks dashboard|alt=]]<br /> A non-editing teacher, teacher, manager or any role with block/deft:manage capability will see a Manage button on the Deft response block. Clicking the button will open the manage task dashboard and change display options for the tasks. The user will not be able to create, edit or move task without the block/deft:edit capability.<br /> Display options can be changed with a form that appears on the task card. Changes will be visible only after they are submitted. <br /> == Installation and initial setup ==<br /> === Installation ===<br /> There are several options how to install the deft response block:<br /> ==== Option 1: Install from Moodle.org ====<br /> * Login as an admin and go to Site administration &gt; Plugins &gt; Install plugins. (If you can't find this location, then plugin installation is prevented on your site.)<br /> * Click the button 'Install plugins from Moodle plugins directory'.<br /> * Search for &quot;Deft response&quot;, click the Install button then click Continue.<br /> * Confirm the installation request<br /> * Check the plugin validation report<br /> ==== Option 2: Install from zip package ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Login to your Moodle site as an admin and go to Administration &gt; Site administration &gt; Plugins &gt; Install plugins.<br /> * Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if the plugin is not automatically detected.<br /> * If your target directory is not writeable, you will see a warning message.<br /> * Check the plugin validation report<br /> ==== Option 3: Install manually on server ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Upload or copy it to your Moodle server.<br /> * Unzip it in the `/blocks` directory.<br /> * In your Moodle site (as admin) go to Settings &gt; Site administration &gt; Notifications (you should, for most plugin types, get a message saying the plugin is installed).<br /> For more detailed info, visit &lt;nowiki&gt;https://docs.moodle.org/400/en/Installing_plugins&lt;/nowiki&gt;<br /> === Initial setup ===<br /> &lt;code&gt;All features of the Deft Response block will now work, but they won't be instant i.e. the page won't auto-update until the registration has been completed.&lt;/code&gt;<br /> ==== Automatic registration ====<br /> * [[File:Deft activaition.png|thumb|Service Activation]]After the installation, please go to Administration &gt; Site administration &gt; Plugins &gt; Blocks &gt; Deft response<br /> * On this page, tick &quot;Enable updating&quot; checkbox and save and a activation button should appear.<br /> * Press the &quot;Activation&quot; button. This should create automatically a preconfigured external tool in Activities -&gt; External tool -&gt; Register tools to deftly.<br /> * A table showing usage will then be shown in the block settings instead of the button.<br /> <br /> <br /> You should now be able to add then block to a course or module and when tasks are changed they will be updated in all browsers where they are displayed.<br /> <br /> If that's not the case (i.e. tasks don't update instantly), automatic registration has probably not worked correctly and registration needs to be completed manually (see below).<br /> <br /> ==== Manual registration ====<br /> If automatic registration has failed, please sign up (free) for the deft service agreement on this page: https://bdecent.de/product/deft-service-agreement/<br /> <br /> We will contact you (via email) and provide you with all the information that you need to complete the manual registration.<br /> <br /> <br /> [[es:Ágil]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Deft&diff=146058 2023-05-01T23:43:41Z

<p>Dthies: /* Automatic registration */</p> <hr /> <div>{{Infobox plugin<br /> |type = Block<br /> |entry = https://moodle.org/plugins/view.php?plugin=block_deft<br /> |tracker = https://github.com/dthies/moodle-block_deft/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=436763 Deft response block]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]], [[Stefan Scholz]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The ''Deft response'' block allows a Manager or Editing teacher to create multiple tasks consisting of short texts, discussions, polls, audio conferences and control remotely which ones are displayed and how students may interact with them.<br /> There is a external service that is available to push notifications to clients to update content. This can be configured easily from the plugin and is free for limited usage. Larger sites may need a service agreement in the future. More information and demos are available at [https://deftly.us Deftly.us].<br /> == Managing tasks ==<br /> The block can be added the usual way to a block or course by a user with the Add instance capability. If the user has block/deft:edit or block/deft:manage capability on the block, a Manage button will appear in the block. Clicking the button opens a Manage Tasks dashboard for the block instance. Teachers can make the tasks visible and adjust other parameters on the dashboard and changes will by visible in learners' browsers.<br /> === Defining Tasks ===<br /> If a user has block/deft:edit capability, the dashboard should also have an ''Add text'', ''Add comments'', ''Add choice'', and ''Add venue'' button. Clicking one of the buttons opens a modal form to define a new task. Tasks should be named in a way that helps distinguish them from each other on the dashboard. When the form is saved a task card will appear on the dashboard, but the task will not be visible yet in the block.<br /> ==== Choice ====<br /> [[File:edit choice.png|thumb|Editing Deft Choice on dashboard]]<br /> The choice task allows teachers to poll a class. The editing form defines the a question or prompt and short response that will be available for the students to choose.<br /> ==== Text ====<br /> The text tasks contains simple text that can be later be displayed in the block individually. The text area can contain multiple lines and simple html formatting, urls that may display as links, emoticons, but no media tags.<br /> ==== Comments ====<br /> The Comments task allow student to respond in the block and interact with each other. With the active updates, students can see comments in real time. This allows the block to be used for small discussions or chats. More than one Comments can be added to handle separate or group discussions. The individual task can be shown or hidden to start or moderate the discussions.<br /> The order of the tasks can be arranged. All task are initially hidden from view in the block.<br /> ==== Venue ====<br /> [[File:venue.png|thumb|Users in Venue]]<br /> The Venue task allows learners to converse with each other in a small audio chat format. Each venue is a separate place that a group of students can meet. When the teacher makes the task visible, a button is displayed on the block. When users click the button, they enter the venue and are connected with any other users already present using a peer-to-peer WebRTC audio connection.<br /> <br /> A venue can also be configured to use a bridged connection. Audio is connected through a central server to allow more participants and provide better quality. A teacher or others may also be allowed to stream video in the venue. An appropriate service agreement may be required to use the bridge server.<br /> == Deploying tasks ==<br /> [[File:task dashboard.png|thumb|Manage tasks dashboard|alt=]]<br /> A non-editing teacher, teacher, manager or any role with block/deft:manage capability will see a Manage button on the Deft response block. Clicking the button will open the manage task dashboard and change display options for the tasks. The user will not be able to create, edit or move task without the block/deft:edit capability.<br /> Display options can be changed with a form that appears on the task card. Changes will be visible only after they are submitted. <br /> == Installation and initial setup ==<br /> === Installation ===<br /> There are several options how to install the deft response block:<br /> ==== Option 1: Install from Moodle.org (recommended) ====<br /> * Login as an admin and go to Site administration &gt; Plugins &gt; Install plugins. (If you can't find this location, then plugin installation is prevented on your site.)<br /> * Click the button 'Install plugins from Moodle plugins directory'.<br /> * Search for &quot;Deft response&quot;, click the Install button then click Continue.<br /> * Confirm the installation request<br /> * Check the plugin validation report<br /> ==== Option 2: Install from zip package ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Login to your Moodle site as an admin and go to Administration &gt; Site administration &gt; Plugins &gt; Install plugins.<br /> * Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if the plugin is not automatically detected.<br /> * If your target directory is not writeable, you will see a warning message.<br /> * Check the plugin validation report<br /> ==== Option 3: Install manually on server ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Upload or copy it to your Moodle server.<br /> * Unzip it in the `/blocks` directory.<br /> * In your Moodle site (as admin) go to Settings &gt; Site administration &gt; Notifications (you should, for most plugin types, get a message saying the plugin is installed).<br /> For more detailed info, visit &lt;nowiki&gt;https://docs.moodle.org/400/en/Installing_plugins&lt;/nowiki&gt;<br /> === Initial setup ===<br /> &lt;code&gt;All features of the Deft Response block will now work, but they won't be instant i.e. the page won't auto-update until the registration has been completed.&lt;/code&gt;<br /> ==== Automatic registration ====<br /> * [[File:Deft activaition.png|thumb|Service Activation]]After the installation, please go to Administration &gt; Site administration &gt; Plugins &gt; Blocks &gt; Deft response<br /> * On this page, tick &quot;Enable updating&quot; checkbox and save and a activation button should appear.<br /> * Press the &quot;Activation&quot; button. This should create automatically a preconfigured external tool in Activities -&gt; External tool -&gt; Register tools to deftly.<br /> * A table showing usage will then be shown in the block settings instead of the button.<br /> <br /> <br /> You should now be able to add then block to a course or module and when tasks are changed they will be updated in all browsers where they are displayed.<br /> <br /> If that's not the case (i.e. tasks don't update instantly), automatic registration has probably not worked correctly and registration needs to be completed manually (see below).<br /> <br /> ==== Manual registration ====<br /> If automatic registration has failed, please sign up (free) for the deft service agreement on this page: https://bdecent.de/product/deft-service-agreement/<br /> <br /> We will contact you (via email) and provide you with all the information that you need to complete the manual registration.<br /> <br /> <br /> [[es:Ágil]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Video&diff=146048 2023-04-30T17:56:51Z

<p>Dthies: /* See also */</p> <hr /> <div>{{Working with media}}<br /> '''Video''' is a very powerful tool to use in a Moodle course. Teachers and students can use video actively, by recording short messages directly into the Atto editor. Teachers can also display video so students, for example, catch up on lectures they missed, learn from a &quot;how-to&quot; screencast, or improve their language skills by watching native speakers interact.<br /> ==Recording short video messages==<br /> [[File:recordrtcatto.png]]<br /> Moodle's [[Atto editor]] allows teachers and students to record short video messages by clicking the relevant icon.( If you don't see this setting in the Atto editor, ask your administrator to check the [[RecordRTC]] settings.) This feature is also available for the [[TinyMCE editor]].<br /> <br /> Example uses are:<br /> * Introductions in Forum posts<br /> *Spoken assignments instead of typed<br /> *Courses where teachers and students interact by signing instead of speaking or typing.<br /> ==Where to host the videos==<br /> If you upload your videos to your Moodle site, storing them on your own server, then you retain ultimate control. If you are worried about multiple copies of the same video taking up lots of space, then that is not a problem; the Moodle file system is clever enough to only store a single copy of a file, no matter how many times you upload it to your server.<br /> <br /> When server space or upload limits are restricted, or if you are seeking some video player features not available within Moodle, it is convenient to upload videos to an online site like [https://api.video/ api.video], [http://www.youtube.com YouTube] or [http://vimeo.com Vimeo]. They can easily be embedded inside Moodle from such sites and privacy can still be maintained if you choose their private video sharing option.<br /> ==Ways of displaying video==<br /> ===Linking to a video online elsewhere===<br /> *If your video is hosted elsewhere online (such as YouTube, Vimeo or api.video) you can simply link to the relevant page by choosing [[URL]] from 'Add an activity or resource' and pasting in the relevant link.<br /> *Note that, in an establishment where certain video sharing sites might be banned, your students might not be able to access your video through Moodle.<br /> ===Uploading a video===<br /> *If your browser allows resources to be dragged and dropped, then you can turn on the editing and drag the video directly onto the course page.<br /> *A box will then appear for you to decide whether you want the video embedded in a label, or added as a clickable file resource.<br /> *Alternatively, you can upload the video by turning the editing on and choosing ''Add an activity or resource &gt; [[File]]''<br /> ===Embedding a video in its own player===<br /> Moodle uses [[VideoJS player]] as its default player as it is responsive and displays video well across devices and browsers. With the [[Multimedia plugins filter]] enabled, videos may be embedded as follows:<br /> ====Using the Moodle media icon====<br /> ''(Note that these instructions are for the [[Atto editor]])''<br /> *With your editing turned on, click into the Atto editor text box where you wish to embed your video. <br /> *Click the Moodle media icon as in the following screenshot:<br /> [[File:AddMediaAtto.png]]<br /> *If your video is online, paste its URL into the Source URL box.<br /> *If your video is one you want to upload, click the Video tab.<br /> [[File:DocsVideoInsertMedia.png]]<br /> *Click the Browse repositories button to locate and upload your video from the repository where it is stored. (What you see depends on what the admin has enabled.) If you have it in more than one file type (such as .mov and .mp4) then you can upload an alternative video by clicking 'Add alternative source'.<br /> *'''Display options''' allows you to specify a height and width for the video<br /> *'''Advanced settings''' allows you to decide how the video will play<br /> *'''Subtitles and captions''' allows you to add subtitle files (VTT) in different languages and/or caption files, with descriptions, chapters, and metadata. Subtitles, captions, chapters, and descriptions can be added to videos and audios using the [https://w3c.github.io/webvtt/ WebVTT file format]. These files can be created using caption making software or just a plain text editor. If the video is on YouTube, subtitles can be generated automatically then corrected. Software such as Camtasia enables subtitles to be easily added. '''NOTE:''' ''The files must be uploaded to Moodle; they will not display if they are linked from elsewhere.''<br /> *Click the Insert media button when you are ready.<br /> *Your video will appear as a blue link until you save the changes.<br /> [[File:Videoplayback.png]]<br /> <br /> Note the playback rate (speed) of the video can be changed.<br /> ====Using a hyperlink====<br /> ''(Note: this method has no advantage over using the media icon.)''<br /> *With your editing turned on, click into the Atto editor where you wish to embed your video.<br /> *Type some blank spaces (or some text) and select them.<br /> *Click the hyperlink icon. (The icon will only be clickable if you have selected text or spaces.)<br /> *Click 'Browse repositories'<br /> *This takes you to the file picker. Follow the instructions for uploading/selecting your video as for using the Moodle media icon.<br /> *When your video is chosen, it will appear in the link URL box as below. Click ''Insert:''<br /> *'''''Don't panic!''''' You will now only get a blue line (if you selected blank spaces) or the actual text underlined in the Atto editor:<br /> *When you click ''save changes'' to return to the main course page, your video will display.<br /> ====Using embed code to display external videos====<br /> *Go to your chosen video sharing site and find the embed code of the video you wish to display. Copy this code.<br /> *With your editing turned on, click into the Atto editor where you wish to embed your video.<br /> *Click the HTML code icon as in the following screenshot:<br /> [[File:hyperlinkicon.png]]<br /> *Paste your embed code into the box:<br /> *Save your changes<br /> *Your video will display embedded in a player. YouTube videos by default play via the [[VideoJS player]].<br /> [[File:VideoJSOfficialMusicVideo.png]]<br /> ==See also==<br /> * [[Media FAQ]]<br /> * [[Multimedia plugins filter]]<br /> * [https://moodle.org/plugins/mod_jitsi Jitsi] - This module allows creating jitsi-meet videoconference sessions<br /> * [https://moodle.org/plugins/mod_bigbluebuttonbn Big Blue Button] - Integrate BigBlueButton within Moodle - including record and playback of sessions<br /> * [[Deft response]] block - Allows teacher streaming video to learners as pat of other activities<br /> <br /> <br /> Forum discussions:<br /> *[http://moodle.org/mod/forum/discuss.php?d=143478 Best video format]<br /> *[https://moodle.org/mod/forum/discuss.php?d=344662 download h5p interactive video in moodle]<br /> *[https://moodle.org/mod/forum/discuss.php?d=386059#p1556113 Workshop Module enhances American Sign Language classroom with Video Recordings]<br /> [[Category:Language teaching]]<br /> [[de:Video]]<br /> [[es:Video]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Deft_response&diff=146047 2023-04-30T17:53:48Z

<p>Dthies: Redirected page to Deft</p> <hr /> <div>#REDIRECT [[Deft]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Deft&diff=146046 2023-04-30T00:09:23Z

<p>Dthies: /* Introduction */</p> <hr /> <div>{{Infobox plugin<br /> |type = Block<br /> |entry = https://moodle.org/plugins/view.php?plugin=block_deft<br /> |tracker = https://github.com/dthies/moodle-block_deft/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=436763 Deft response block]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]], [[Stefan Scholz]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The ''Deft response'' block allows a Manager or Editing teacher to create multiple tasks consisting of short texts, discussions, polls, audio conferences and control remotely which ones are displayed and how students may interact with them.<br /> There is a external service that is available to push notifications to clients to update content. This can be configured easily from the plugin and is free for limited usage. Larger sites may need a service agreement in the future. More information and demos are available at [https://deftly.us Deftly.us].<br /> == Managing tasks ==<br /> The block can be added the usual way to a block or course by a user with the Add instance capability. If the user has block/deft:edit or block/deft:manage capability on the block, a Manage button will appear in the block. Clicking the button opens a Manage Tasks dashboard for the block instance. Teachers can make the tasks visible and adjust other parameters on the dashboard and changes will by visible in learners' browsers.<br /> === Defining Tasks ===<br /> If a user has block/deft:edit capability, the dashboard should also have an ''Add text'', ''Add comments'', ''Add choice'', and ''Add venue'' button. Clicking one of the buttons opens a modal form to define a new task. Tasks should be named in a way that helps distinguish them from each other on the dashboard. When the form is saved a task card will appear on the dashboard, but the task will not be visible yet in the block.<br /> ==== Choice ====<br /> [[File:edit choice.png|thumb|Editing Deft Choice on dashboard]]<br /> The choice task allows teachers to poll a class. The editing form defines the a question or prompt and short response that will be available for the students to choose.<br /> ==== Text ====<br /> The text tasks contains simple text that can be later be displayed in the block individually. The text area can contain multiple lines and simple html formatting, urls that may display as links, emoticons, but no media tags.<br /> ==== Comments ====<br /> The Comments task allow student to respond in the block and interact with each other. With the active updates, students can see comments in real time. This allows the block to be used for small discussions or chats. More than one Comments can be added to handle separate or group discussions. The individual task can be shown or hidden to start or moderate the discussions.<br /> The order of the tasks can be arranged. All task are initially hidden from view in the block.<br /> ==== Venue ====<br /> [[File:venue.png|thumb|Users in Venue]]<br /> The Venue task allows learners to converse with each other in a small audio chat format. Each venue is a separate place that a group of students can meet. When the teacher makes the task visible, a button is displayed on the block. When users click the button, they enter the venue and are connected with any other users already present using a peer-to-peer WebRTC audio connection.<br /> <br /> A venue can also be configured to use a bridged connection. Audio is connected through a central server to allow more participants and provide better quality. A teacher or others may also be allowed to stream video in the venue. An appropriate service agreement may be required to use the bridge server.<br /> == Deploying tasks ==<br /> [[File:task dashboard.png|thumb|Manage tasks dashboard|alt=]]<br /> A non-editing teacher, teacher, manager or any role with block/deft:manage capability will see a Manage button on the Deft response block. Clicking the button will open the manage task dashboard and change display options for the tasks. The user will not be able to create, edit or move task without the block/deft:edit capability.<br /> Display options can be changed with a form that appears on the task card. Changes will be visible only after they are submitted. <br /> == Installation and initial setup ==<br /> === Installation ===<br /> There are several options how to install the deft response block:<br /> ==== Option 1: Install from Moodle.org (recommended) ====<br /> * Login as an admin and go to Site administration &gt; Plugins &gt; Install plugins. (If you can't find this location, then plugin installation is prevented on your site.)<br /> * Click the button 'Install plugins from Moodle plugins directory'.<br /> * Search for &quot;Deft response&quot;, click the Install button then click Continue.<br /> * Confirm the installation request<br /> * Check the plugin validation report<br /> ==== Option 2: Install from zip package ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Login to your Moodle site as an admin and go to Administration &gt; Site administration &gt; Plugins &gt; Install plugins.<br /> * Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if the plugin is not automatically detected.<br /> * If your target directory is not writeable, you will see a warning message.<br /> * Check the plugin validation report<br /> ==== Option 3: Install manually on server ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Upload or copy it to your Moodle server.<br /> * Unzip it in the `/blocks` directory.<br /> * In your Moodle site (as admin) go to Settings &gt; Site administration &gt; Notifications (you should, for most plugin types, get a message saying the plugin is installed).<br /> For more detailed info, visit &lt;nowiki&gt;https://docs.moodle.org/400/en/Installing_plugins&lt;/nowiki&gt;<br /> === Initial setup ===<br /> &lt;code&gt;All features of the Deft Response block will now work, but they won't be instant i.e. the page won't auto-update until the registration has been completed.&lt;/code&gt;<br /> ==== Automatic registration ====<br /> * [[File:Deft activaition.png|thumb|Service Activation]]After the installation, please go to Administration &gt; Site administration &gt; Plugins &gt; Blocks &gt; Deft response<br /> * On this page, tick &quot;Enable updating&quot; checkbox and save and a activation button should appear.<br /> * Press the &quot;Activation&quot; button. This should create automatically a preconfigured external tool in Activities -&gt; External tool -&gt; Register tools to deftly.<br /> * A table showing usage will then be shown in the block settings instead of the button.<br /> <br /> <br /> You should now be able to add then block to a course or module and when tasks are changed they will be updated in all browsers where they are displayed.<br /> <br /> If that's not the case (i.e. tasks don't update instantly), automatic registration probably has probably not worked correctly and registration needs to be completed manually (see below).<br /> ==== Manual registration ====<br /> If automatic registration has failed, please sign up (free) for the deft service agreement on this page: https://bdecent.de/product/deft-service-agreement/<br /> <br /> We will contact you (via email) and provide you with all the information that you need to complete the manual registration.<br /> <br /> <br /> [[es:Ágil]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Deft&diff=146045 2023-04-30T00:04:47Z

<p>Dthies: /* Installation */</p> <hr /> <div>{{Infobox plugin<br /> |type = Block<br /> |entry = https://moodle.org/plugins/view.php?plugin=block_deft<br /> |tracker = https://github.com/dthies/moodle-block_deft/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=436763 Deft response block]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]], [[Stefan Scholz]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The ''Deft response'' block allows a Manager or Editing teacher to create multiple tasks consisting of short texts, discussions, polls, audio conferences and control remotely which ones are displayed and how students may interact with them.<br /> There is a external service that is available to push notifications to clients to update content. This can be usually be configured easily from the plugin and is free for limited usage. Larger sites may need a service agreement in the future. More information and demos are available at [https://deftly.us Deftly.us].<br /> == Managing tasks ==<br /> The block can be added the usual way to a block or course by a user with the Add instance capability. If the user has block/deft:edit or block/deft:manage capability on the block, a Manage button will appear in the block. Clicking the button opens a Manage Tasks dashboard for the block instance.<br /> === Defining Tasks ===<br /> If a user has block/deft:edit capability, the dashboard should also have an ''Add text'', ''Add comments'', ''Add choice'', and ''Add venue'' button. Clicking one of the buttons opens a modal form to define a new task. Tasks should be named in a way that helps distinguish them from each other on the dashboard. When the form is saved a task card will appear on the dashboard, but the task will not be visible yet in the block.<br /> ==== Choice ====<br /> [[File:edit choice.png|thumb|Editing Deft Choice on dashboard]]<br /> The choice task allows teachers to poll a class. The editing form defines the a question or prompt and short response that will be available for the students to choose.<br /> ==== Text ====<br /> The text tasks contains simple text that can be later be displayed in the block individually. The text area can contain multiple lines and simple html formatting, urls that may display as links, emoticons, but no media tags.<br /> ==== Comments ====<br /> The Comments task allow student to respond in the block and interact with each other. With the active updates, students can see comments in real time. This allows the block to be used for small discussions or chats. More than one Comments can be added to handle separate or group discussions. The individual task can be shown or hidden to start or moderate the discussions.<br /> The order of the tasks can be arranged. All task are initially hidden from view in the block.<br /> ==== Venue ====<br /> [[File:venue.png|thumb|Users in Venue]]<br /> The Venue task allows learners to converse with each other in a small audio chat format. Each venue is a separate place that a group of students can meet. When the teacher makes the task visible, a button is displayed on the block. When users click the button, they enter the venue and are connected with any other users already present using a peer-to-peer WebRTC audio connection.<br /> <br /> A venue can also be configured to use a bridged connection. Audio is connected through a central server to allow more participants and provide better quality. A teacher or others may also be allowed to stream video in the venue. An appropriate service agreement may be required to use the bridge server.<br /> == Deploying tasks ==<br /> [[File:task dashboard.png|thumb|Manage tasks dashboard|alt=]]<br /> A non-editing teacher, teacher, manager or any role with block/deft:manage capability will see a Manage button on the Deft response block. Clicking the button will open the manage task dashboard and change display options for the tasks. The user will not be able to create, edit or move task without the block/deft:edit capability.<br /> Display options can be changed with a form that appears on the task card. Changes will be visible only after they are submitted. <br /> == Installation and initial setup ==<br /> === Installation ===<br /> There are several options how to install the deft response block:<br /> ==== Option 1: Install from Moodle.org (recommended) ====<br /> * Login as an admin and go to Site administration &gt; Plugins &gt; Install plugins. (If you can't find this location, then plugin installation is prevented on your site.)<br /> * Click the button 'Install plugins from Moodle plugins directory'.<br /> * Search for &quot;Deft response&quot;, click the Install button then click Continue.<br /> * Confirm the installation request<br /> * Check the plugin validation report<br /> ==== Option 2: Install from zip package ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Login to your Moodle site as an admin and go to Administration &gt; Site administration &gt; Plugins &gt; Install plugins.<br /> * Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if the plugin is not automatically detected.<br /> * If your target directory is not writeable, you will see a warning message.<br /> * Check the plugin validation report<br /> ==== Option 3: Install manually on server ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Upload or copy it to your Moodle server.<br /> * Unzip it in the `/blocks` directory.<br /> * In your Moodle site (as admin) go to Settings &gt; Site administration &gt; Notifications (you should, for most plugin types, get a message saying the plugin is installed).<br /> For more detailed info, visit &lt;nowiki&gt;https://docs.moodle.org/400/en/Installing_plugins&lt;/nowiki&gt;<br /> <br /> === Initial setup ===<br /> &lt;code&gt;All features of the Deft Response block will now work, but they won't be instant i.e. the page won't auto-update until the registration has been completed.&lt;/code&gt;<br /> ==== Automatic registration ====<br /> * [[File:Deft activaition.png|thumb|Service Activation]]After the installation, please go to Administration &gt; Site administration &gt; Plugins &gt; Blocks &gt; Deft response<br /> * On this page, tick &quot;Enable updating&quot; checkbox and save and a activation button should appear.<br /> * Press the &quot;Activation&quot; button. This should create automatically a preconfigured external tool in Activities -&gt; External tool -&gt; Register tools to deftly.<br /> * A table showing usage will then be shown in the block settings instead of the button.<br /> <br /> <br /> You should now be able to add then block to a course or module and when tasks are changed they will be updated in all browsers where they are displayed.<br /> <br /> If that's not the case (i.e. tasks don't update instantly), automatic registration probably has probably not worked correctly and registration needs to be completed manually (see below).<br /> ==== Manual registration ====<br /> If automatic registration has failed, please sign up (free) for the deft service agreement on this page: https://bdecent.de/product/deft-service-agreement/<br /> <br /> We will contact you (via email) and provide you with all the information that you need to complete the manual registration.<br /> <br /> <br /> [[es:Ágil]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Deft&diff=146044 2023-04-29T23:47:46Z

<p>Dthies: /* Venue */</p> <hr /> <div>{{Infobox plugin<br /> |type = Block<br /> |entry = https://moodle.org/plugins/view.php?plugin=block_deft<br /> |tracker = https://github.com/dthies/moodle-block_deft/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=436763 Deft response block]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]], [[Stefan Scholz]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The ''Deft response'' block allows a Manager or Editing teacher to create multiple tasks consisting of short texts, discussions, polls, audio conferences and control remotely which ones are displayed and how students may interact with them.<br /> There is a external service that is available to push notifications to clients to update content. This can be usually be configured easily from the plugin and is free for limited usage. Larger sites may need a service agreement in the future. More information and demos are available at [https://deftly.us Deftly.us].<br /> == Managing tasks ==<br /> The block can be added the usual way to a block or course by a user with the Add instance capability. If the user has block/deft:edit or block/deft:manage capability on the block, a Manage button will appear in the block. Clicking the button opens a Manage Tasks dashboard for the block instance.<br /> === Defining Tasks ===<br /> If a user has block/deft:edit capability, the dashboard should also have an ''Add text'', ''Add comments'', ''Add choice'', and ''Add venue'' button. Clicking one of the buttons opens a modal form to define a new task. Tasks should be named in a way that helps distinguish them from each other on the dashboard. When the form is saved a task card will appear on the dashboard, but the task will not be visible yet in the block.<br /> ==== Choice ====<br /> [[File:edit choice.png|thumb|Editing Deft Choice on dashboard]]<br /> The choice task allows teachers to poll a class. The editing form defines the a question or prompt and short response that will be available for the students to choose.<br /> ==== Text ====<br /> The text tasks contains simple text that can be later be displayed in the block individually. The text area can contain multiple lines and simple html formatting, urls that may display as links, emoticons, but no media tags.<br /> ==== Comments ====<br /> The Comments task allow student to respond in the block and interact with each other. With the active updates, students can see comments in real time. This allows the block to be used for small discussions or chats. More than one Comments can be added to handle separate or group discussions. The individual task can be shown or hidden to start or moderate the discussions.<br /> The order of the tasks can be arranged. All task are initially hidden from view in the block.<br /> ==== Venue ====<br /> [[File:venue.png|thumb|Users in Venue]]<br /> The Venue task allows learners to converse with each other in a small audio chat format. Each venue is a separate place that a group of students can meet. When the teacher makes the task visible, a button is displayed on the block. When users click the button, they enter the venue and are connected with any other users already present using a peer-to-peer WebRTC audio connection.<br /> <br /> A venue can also be configured to use a bridged connection. Audio is connected through a central server to allow more participants and provide better quality. A teacher or others may also be allowed to stream video in the venue. An appropriate service agreement may be required to use the bridge server.<br /> == Deploying tasks ==<br /> [[File:task dashboard.png|thumb|Manage tasks dashboard|alt=]]<br /> A non-editing teacher, teacher, manager or any role with block/deft:manage capability will see a Manage button on the Deft response block. Clicking the button will open the manage task dashboard and change display options for the tasks. The user will not be able to create, edit or move task without the block/deft:edit capability.<br /> Display options can be changed with a form that appears on the task card. Changes will be visible only after they are submitted. <br /> == Installation and initial setup ==<br /> === Installation ===<br /> There are several options how to install the deft response block:<br /> ==== Option 1: Install from Moodle.org (recommended) ====<br /> * Login as an admin and go to Site administration &gt; Plugins &gt; Install plugins. (If you can't find this location, then plugin installation is prevented on your site.)<br /> * Click the button 'Install plugins from Moodle plugins directory'.<br /> * Search for &quot;Deft response&quot;, click the Install button then click Continue.<br /> * Confirm the installation request<br /> * Check the plugin validation report<br /> ==== Option 2: Install from zip package ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Login to your Moodle site as an admin and go to Administration &gt; Site administration &gt; Plugins &gt; Install plugins.<br /> * Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if the plugin is not automatically detected.<br /> * If your target directory is not writeable, you will see a warning message.<br /> * Check the plugin validation report<br /> ===== Option 3: Install manually on server =====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Upload or copy it to your Moodle server.<br /> * Unzip it in the `/blocks` directory.<br /> * In your Moodle site (as admin) go to Settings &gt; Site administration &gt; Notifications (you should, for most plugin types, get a message saying the plugin is installed).<br /> For more detailed info, visit &lt;nowiki&gt;https://docs.moodle.org/400/en/Installing_plugins&lt;/nowiki&gt;<br /> === Initial setup ===<br /> &lt;code&gt;All features of the Deft Response block will now work, but they won't be instant i.e. the page won't auto-update until the registration has been completed.&lt;/code&gt;<br /> ==== Automatic registration ====<br /> * [[File:Deft activaition.png|thumb|Service Activation]]After the installation, please go to Administration &gt; Site administration &gt; Plugins &gt; Blocks &gt; Deft response<br /> * On this page, tick &quot;Enable updating&quot; checkbox and save and a activation button should appear.<br /> * Press the &quot;Activation&quot; button. This should create automatically a preconfigured external tool in Activities -&gt; External tool -&gt; Register tools to deftly.<br /> * A table showing usage will then be shown in the block settings instead of the button.<br /> <br /> <br /> You should now be able to add then block to a course or module and when tasks are changed they will be updated in all browsers where they are displayed.<br /> <br /> If that's not the case (i.e. tasks don't update instantly), automatic registration probably has probably not worked correctly and registration needs to be completed manually (see below).<br /> ==== Manual registration ====<br /> If automatic registration has failed, please sign up (free) for the deft service agreement on this page: https://bdecent.de/product/deft-service-agreement/<br /> <br /> We will contact you (via email) and provide you with all the information that you need to complete the manual registration.<br /> <br /> <br /> [[es:Ágil]]</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Deft&diff=145638 2023-03-12T01:22:22Z

<p>Dthies: /* Venue */</p> <hr /> <div>{{Infobox plugin<br /> |type = Block<br /> |entry = https://moodle.org/plugins/view.php?plugin=block_deft<br /> |tracker = https://github.com/dthies/moodle-block_deft/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=436763 Deft response block]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]], [[Stefan Scholz]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The ''Deft response'' block allows a Manager or Editing teacher to create multiple tasks consisting of short texts, discussions, polls, audio conferences and control remotely which ones are displayed and how students may interact with them.<br /> There is a external service that is available to push notifications to clients to update content. This can be usually be configured easily from the plugin and is free for limited usage. Larger sites may need a service agreement in the future. More information and demos are available at [https://deftly.us Deftly.us].<br /> == Managing tasks ==<br /> The block can be added the usual way to a block or course by a user with the Add instance capability. If the user has block/deft:edit or block/deft:manage capability on the block, a Manage button will appear in the block. Clicking the button opens a Manage Tasks dashboard for the block instance.<br /> === Defining Tasks ===<br /> If a user has block/deft:edit capability, the dashboard should also have an ''Add text'', ''Add comments'', ''Add choice'', and ''Add venue'' button. Clicking one of the buttons opens a modal form to define a new task. Tasks should be named in a way that helps distinguish them from each other on the dashboard. When the form is saved a task card will appear on the dashboard, but the task will not be visible yet in the block.<br /> ==== Choice ====<br /> [[File:edit choice.png|thumb|Editing Deft Choice on dashboard]]<br /> The choice task allows teachers to poll a class. The editing form defines the a question or prompt and short response that will be available for the students to choose.<br /> ==== Text ====<br /> The text tasks contains simple text that can be later be displayed in the block individually. The text area can contain multiple lines and simple html formatting, urls that may display as links, emoticons, but no media tags.<br /> ==== Comments ====<br /> The Comments task allow student to respond in the block and interact with each other. With the active updates, students can see comments in real time. This allows the block to be used for small discussions or chats. More than one Comments can be added to handle separate or group discussions. The individual task can be shown or hidden to start or moderate the discussions.<br /> The order of the tasks can be arranged. All task are initially hidden from view in the block.<br /> ==== Venue ====<br /> [[File:venue.png|thumb|Users in Venue]]<br /> The Venue task allows learners to converse with each other in a small audio chat format. Each venue is a separate place that a group of students can meet. When the teacher makes the task visible, a button is displayed on the block. When users click the button, they enter the venue and are connected with any other users already present using a peer-to-peer WebRTC audio connection.<br /> == Deploying tasks ==<br /> [[File:task dashboard.png|thumb|Manage tasks dashboard|alt=]]<br /> A non-editing teacher, teacher, manager or any role with block/deft:manage capability will see a Manage button on the Deft response block. Clicking the button will open the manage task dashboard and change display options for the tasks. The user will not be able to create, edit or move task without the block/deft:edit capability.<br /> Display options can be changed with a form that appears on the task card. Changes will be visible only after they are submitted. <br /> == Installation and initial setup ==<br /> === Installation ===<br /> There are several options how to install the deft response block:<br /> ==== Option 1: Install from Moodle.org (recommended) ====<br /> * Login as an admin and go to Site administration &gt; Plugins &gt; Install plugins. (If you can't find this location, then plugin installation is prevented on your site.)<br /> * Click the button 'Install plugins from Moodle plugins directory'.<br /> * Search for &quot;Deft response&quot;, click the Install button then click Continue.<br /> * Confirm the installation request<br /> * Check the plugin validation report<br /> ==== Option 2: Install from zip package ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Login to your Moodle site as an admin and go to Administration &gt; Site administration &gt; Plugins &gt; Install plugins.<br /> * Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if the plugin is not automatically detected.<br /> * If your target directory is not writeable, you will see a warning message.<br /> * Check the plugin validation report<br /> ===== Option 3: Install manually on server =====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Upload or copy it to your Moodle server.<br /> * Unzip it in the `/blocks` directory.<br /> * In your Moodle site (as admin) go to Settings &gt; Site administration &gt; Notifications (you should, for most plugin types, get a message saying the plugin is installed).<br /> For more detailed info, visit &lt;nowiki&gt;https://docs.moodle.org/400/en/Installing_plugins&lt;/nowiki&gt;<br /> === Initial setup ===<br /> &lt;code&gt;All features of the Deft Response block will now work, but they won't be instant i.e. the page won't auto-update until the registration has been completed.&lt;/code&gt;<br /> ==== Automatic registration ====<br /> * [[File:Deft activaition.png|thumb|Service Activation]]After the installation, please go to Administration &gt; Site administration &gt; Plugins &gt; Blocks &gt; Deft response<br /> * On this page, tick &quot;Enable updating&quot; checkbox and save and a activation button should appear.<br /> * Press the &quot;Activation&quot; button. This should create automatically a preconfigured external tool in Activities -&gt; External tool -&gt; Register tools to deftly.<br /> * A table showing usage will then be shown in the block settings instead of the button.<br /> <br /> <br /> You should now be able to add then block to a course or module and when tasks are changed they will be updated in all browsers where they are displayed.<br /> <br /> If that's not the case (i.e. tasks don't update instantly), automatic registration probably has probably not worked correctly and registration needs to be completed manually (see below).<br /> ==== Manual registration ====<br /> If automatic registration has failed, please sign up (free) for the deft service agreement on this page: https://bdecent.de/product/deft-service-agreement/<br /> <br /> We will contact you (via email) and provide you with all the information that you need to complete the manual registration.</div>

Dthies https://docs.moodle.org/501/en/index.php?title=Deft&diff=145594 2023-03-01T16:14:15Z

<p>Dthies: /* Automatic registration */</p> <hr /> <div>{{Infobox plugin<br /> |type = Block<br /> |entry = https://moodle.org/plugins/view.php?plugin=block_deft<br /> |tracker = https://github.com/dthies/moodle-block_deft/issues<br /> |discussion = [https://moodle.org/mod/forum/discuss.php?d=436763 Deft response block]<br /> |maintainer = [[User:Daniel Thies|Daniel Thies]], [[Stefan Scholz]]<br /> |float = right<br /> }}<br /> == Introduction ==<br /> The ''Deft response'' block allows a Manager or Editing teacher to create multiple tasks consisting of short texts, discussions, polls, audio conferences and control remotely which ones are displayed and how students may interact with them.<br /> There is a external service that is available to push notifications to clients to update content. This can be usually be configured easily from the plugin and is free for limited usage. Larger sites may need a service agreement in the future. More information and demos are available at [https://deftly.us Deftly.us].<br /> == Managing tasks ==<br /> The block can be added the usual way to a block or course by a user with the Add instance capability. If the user has block/deft:edit or block/deft:manage capability on the block, a Manage button will appear in the block. Clicking the button opens a Manage Tasks dashboard for the block instance.<br /> === Defining Tasks ===<br /> If a user has block/deft:edit capability, the dashboard should also have an ''Add text'', ''Add comments'', ''Add choice'', and ''Add venue'' button. Clicking one of the buttons opens a modal form to define a new task. Tasks should be named in a way that helps distinguish them from each other on the dashboard. When the form is saved a task card will appear on the dashboard, but the task will not be visible yet in the block.<br /> ==== Choice ====<br /> [[File:edit choice.png|thumb|Editing Deft Choice on dashboard]]<br /> The choice task allows teachers to poll a class. The editing form defines the a question or prompt and short response that will be available for the students to choose.<br /> ==== Text ====<br /> The text tasks contains simple text that can be later be displayed in the block individually. The text area can contain multiple lines and simple html formatting, urls that may display as links, emoticons, but no media tags.<br /> ==== Comments ====<br /> The Comments task allow student to respond in the block and interact with each other. With the active updates, students can see comments in real time. This allows the block to be used for small discussions or chats. More than one Comments can be added to handle separate or group discussions. The individual task can be shown or hidden to start or moderate the discussions.<br /> The order of the tasks can be arranged. All task are initially hidden from view in the block.<br /> ==== Venue ====<br /> [[File:venue.png|thumb|Users in Venue]]<br /> The Venue task allows learners to converse with each other in a small audio chat format. Each venue is a separate place that a group of students can meet. When the teacher makes the task visible, a button is displayed on the block. When users click the button, they enter the venue an are connected with any other users already using a peer-to-peer WebRTC audio connection.<br /> == Deploying tasks ==<br /> [[File:task dashboard.png|thumb|Manage tasks dashboard|alt=]]<br /> A non-editing teacher, teacher, manager or any role with block/deft:manage capability will see a Manage button on the Deft response block. Clicking the button will open the manage task dashboard and change display options for the tasks. The user will not be able to create, edit or move task without the block/deft:edit capability.<br /> Display options can be changed with a form that appears on the task card. Changes will be visible only after they are submitted. <br /> == Installation and initial setup ==<br /> === Installation ===<br /> There are several options how to install the deft response block:<br /> ==== Option 1: Install from Moodle.org (recommended) ====<br /> * Login as an admin and go to Site administration &gt; Plugins &gt; Install plugins. (If you can't find this location, then plugin installation is prevented on your site.)<br /> * Click the button 'Install plugins from Moodle plugins directory'.<br /> * Search for &quot;Deft response&quot;, click the Install button then click Continue.<br /> * Confirm the installation request<br /> * Check the plugin validation report<br /> ==== Option 2: Install from zip package ====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Login to your Moodle site as an admin and go to Administration &gt; Site administration &gt; Plugins &gt; Install plugins.<br /> * Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if the plugin is not automatically detected.<br /> * If your target directory is not writeable, you will see a warning message.<br /> * Check the plugin validation report<br /> ===== Option 3: Install manually on server =====<br /> * Download Deft from https://moodle.org/plugins/block_deft or https://github.com/dthies/moodle-block_deft.<br /> * Upload or copy it to your Moodle server.<br /> * Unzip it in the `/blocks` directory.<br /> * In your Moodle site (as admin) go to Settings &gt; Site administration &gt; Notifications (you should, for most plugin types, get a message saying the plugin is installed).<br /> For more detailed info, visit &lt;nowiki&gt;https://docs.moodle.org/400/en/Installing_plugins&lt;/nowiki&gt;<br /> === Initial setup ===<br /> &lt;code&gt;All features of the Deft Response block will now work, but they won't be instant i.e. the page won't auto-update until the registration has been completed.&lt;/code&gt;<br /> ==== Automatic registration ====<br /> * [[File:Deft activaition.png|thumb|Service Activation]]After the installation, please go to Administration &gt; Site administration &gt; Plugins &gt; Blocks &gt; Deft response<br /> * On this page, tick &quot;Enable updating&quot; checkbox and save and a activation button should appear.<br /> * Press the &quot;Activation&quot; button. This should create automatically a preconfigured external tool in Activities -&gt; External tool -&gt; Register tools to deftly.<br /> * A table showing usage will then be shown in the block settings instead of the button.<br /> <br /> <br /> You should now be able to add then block to a course or module and when tasks are changed they will be updated in all browsers where they are displayed.<br /> <br /> If that's not the case (i.e. tasks don't update instantly), automatic registration probably has probably not worked correctly and registration needs to be completed manually (see below).<br /> ==== Manual registration ====<br /> If automatic registration has failed, please sign up (free) for the deft service agreement on this page: https://bdecent.de/product/deft-service-agreement/<br /> <br /> We will contact you (via email) and provide you with all the information that you need to complete the manual registration.</div>

Dthies