{"id":201,"date":"2010-03-30T16:09:52","date_gmt":"2010-03-30T20:09:52","guid":{"rendered":"http:\/\/blogs.middlebury.edu\/segue\/?page_id=201"},"modified":"2012-07-29T15:03:48","modified_gmt":"2012-07-29T15:03:48","slug":"curricular-technologies-functional-requirements","status":"publish","type":"page","link":"https:\/\/segueproject.org\/segue-migration\/curricular-technology-functional-requirements\/curricular-technologies-functional-requirements\/","title":{"rendered":"Functional Requirements for Segue Replacements"},"content":{"rendered":"<p>Below is a list of the kinds of functionality we think we would need to have in place before Segue can be completely phased out. Given that we&#8217;ll likely have many tools for curricular use, not all platforms\/applications need to have all the functionality listed here.\u00a0 If there are features or functionality in Segue that we have left out in this list, please let us know.<\/p>\n<h3>Access Control<\/h3>\n<ul>\n<li>Can be implemented to use Midd authentication<\/li>\n<li>Access to content\/resources can be granted to any group defined in Active Directory (AD) including class groups<\/li>\n<li>Access can be defined for &#8220;portions&#8221; of a site (i.e. sub-sections or sub-pages) such that different groups can have different roles in any given portion of site\/resource<\/li>\n<li>Access control UI needs to be able to:\n<ul>\n<li>search all users\/groups<\/li>\n<li>assign roles to any found user\/group<\/li>\n<li>add users\/groups to a &#8220;meta&#8221; group for that site\/resource (i.e. group of &#8220;site members&#8221;)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3>Blogging<\/h3>\n<ul>\n<li>Support for blogging (multiple posts on a page sorted recent first)<\/li>\n<li>Support for online discussion with following features:\n<ul>\n<li>threading<\/li>\n<li>HTML editor<\/li>\n<li>File attachments<\/li>\n<li>Discussion post sorting (recent first, recent last, threaded, flat&#8230;)<\/li>\n<\/ul>\n<\/li>\n<li>RSS<\/li>\n<\/ul>\n<h3>Languages<\/h3>\n<ul>\n<li>Support for diacritics and non-Roman fonts<\/li>\n<\/ul>\n<h3>File Management<\/h3>\n<ul>\n<li>Web-based file upload (ideally with support for uploading multiple files at the same time)<\/li>\n<li>Support for large file management and distribution<\/li>\n<\/ul>\n<h3>Content Management<\/h3>\n<ul>\n<li>Hierarchical organization of content into sections, pages, sub-pages etc..<\/li>\n<li>Organization by tagging and aggregation by tags<\/li>\n<li>Sorting of content<\/li>\n<li>Content versioning<\/li>\n<li>Reorganization of content<\/li>\n<li>reordering of content blocks<\/li>\n<li>move\/copy content hierarchies (i.e. move\/copy sections with multiple pages or pages with multiple content nodes\/blocks) from one site\/location to another<\/li>\n<li>Copy sites (i.e. copy a course site from a previous semester and reuse in current or future semester):<\/li>\n<li>copy site roles and content attribution<\/li>\n<li>copy site layout<\/li>\n<li>options for removing roles and discussion posts when copying<\/li>\n<\/ul>\n<h3 style=\"font-size: 1.17em\">Content Migration<\/h3>\n<ul>\n<li>Export of content to well-defined XML format or static HTML<\/li>\n<li>Import of content from comparable platforms<\/li>\n<\/ul>\n<h3>Course, Site and Namespace Management<\/h3>\n<ul>\n<li>Listing of past, current and future courses for students and faculty with links to course sites (if available)<\/li>\n<li>Course\/site self service creation for current and future courses<\/li>\n<li>Course site namespace management<\/li>\n<li>course sites with course code in site url<\/li>\n<li>multiple course site urls resolving to specified url (i.e. mechanism for ensuring that one course site can be used for multiple course sections)<\/li>\n<li>Track participation in course site (i.e. aggregation all contributions from a given user across a site in a single sortable list)<span><br \/>\n<\/span><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Below is a list of the kinds of functionality we think we would need to have in place before Segue can be completely phased out. Given that we&#8217;ll likely have many tools for curricular use, not all platforms\/applications need to &hellip; <a href=\"https:\/\/segueproject.org\/segue-migration\/curricular-technology-functional-requirements\/curricular-technologies-functional-requirements\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":29,"featured_media":0,"parent":827,"menu_order":2,"comment_status":"open","ping_status":"open","template":"page-right01-sidebar.php","meta":{"footnotes":""},"class_list":["post-201","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/segueproject.org\/segue-migration\/wp-json\/wp\/v2\/pages\/201","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/segueproject.org\/segue-migration\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/segueproject.org\/segue-migration\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/segueproject.org\/segue-migration\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/segueproject.org\/segue-migration\/wp-json\/wp\/v2\/comments?post=201"}],"version-history":[{"count":1,"href":"https:\/\/segueproject.org\/segue-migration\/wp-json\/wp\/v2\/pages\/201\/revisions"}],"predecessor-version":[{"id":1354,"href":"https:\/\/segueproject.org\/segue-migration\/wp-json\/wp\/v2\/pages\/201\/revisions\/1354"}],"up":[{"embeddable":true,"href":"https:\/\/segueproject.org\/segue-migration\/wp-json\/wp\/v2\/pages\/827"}],"wp:attachment":[{"href":"https:\/\/segueproject.org\/segue-migration\/wp-json\/wp\/v2\/media?parent=201"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}