Development Backlog

From Salish Sea Wiki

Technical Pages[edit]

Click this book to return to the Development Log Page

See Introduction Pages

See also Development Log and Development Roadmap

The backlog includes all potential tasks that have not been designated as part of an active contract or specific scope of work.

Proposed SOW#2[edit]

WikiWorks[edit]

  1. Develop Page Forms/Templates for 4 Remaining Page Types - Using the existing Form:Product and Template:Product, create similar pages for Workgroup, Effort, Place, and Topic page types. For Workgroups this will include functions that enable the use of acronyms that redirect to workgroup pages, and the ability to associate workgroups with products, efforts and topics.
    • Effort and Product Attribution - develop mechanism for workgroups to be associated with efforts and products in a systematic way and resolve the Category:Acronym and {{credit}} functions.
    • Page Edit Forms - See Form:Workgroup, Form:Effort, Form:Place, and Form:Topic for drafts.
    • Update Product Data - Simplify Product Data Structure, but having the same title field, and with the same Author and Year fields "appear on select" for each subtype (Documents, Graphics, and Datasets). Simplify Temlate data call to match.
    • Establish Cargo Table Relationships And Test Queries- Currently the overall native category structure as described by the single category hierarchy is not reflected in the structure of the Cargo tables created by the structured data now in various page types. We'd like to be able to efficiently use cargo queries to query across and among page types.
    • Establish Edit With Form - use "edit with form" and "create with form" links as the primary mechanism for page editing and creation for users following links (bureaucrats and admin will have source options provided). Remove "view source" for visitors.
  2. Minor Improvements -
    • Bulk email members - extension to allow communication with active users.
    • Update Site Icons - for browser links (moderator will provide)
    • Troubleshoot Popup Problem - troubleshoot "unable to show preview" error... moderator will flag examples.
    • Inline Comments - add inline comment extension or recommended equivalent. https://www.mediawiki.org/wiki/Extension:InlineComments
    • QR Codes - add an extension light QR light that creates a QR code for each page that can be easily cut and pasted into products that take you back to that page. Can this have a custom central graphic?
    • Bulk Page Creation - We will develop and deploy the ability to load a set of documents, and then autogenerate a set of pages from a CVS spreadsheet.
    • Define a new category protocol - Define the sequence of steps necessary to add an category/attribute while maintaining the relationships among attributes, correcting any use of deprecated attributes in existing pages, and maintaining cargo-to-category parity. Potential Categories provides a stopgap reservoir of future changes. The primary challenge here is changing categories in cargo data structure, presumably using ReplaceText and some sophisticated RegEx (?).
  3. Initial Map Scope or Prototype - A system for displaying polygons stored on the wiki through a slide-up mapper accessible from Place pages. Spatial objects are stored on the wiki (likely as GeoJson files using Map Data Extension) and are associated with pages, and the structured data of those pages. In the mapper, spatial objects (linked to wiki pages) can be filtered based on category/attribute data on the pages structured data (using Cargo?). The map is accessable from all place pages. When map view is activated, the mapper reads the Cargo data of the current page, checks if there is an associated polygon associated with that place, and generates a map centering that place at an appropriate scale and showing other similar scale pages in the neighborhood. A master mapper allows for review and filtering of all spatial data using page-polygon-cargo-associated data and a set of controls.

Moderator Team[edit]

  • Social Component - Replace talk pages with a pathway into a dynamic social media context (perhaps Hylo). This must be designed and promoted.
  • Update Page Type Info Boxes - Update the Salish Sea References and create DPLs appropriate for each Page Type Info Box.
  • Finish Architecture Page Framework -
  • Polygon Set
  • Promotional Video
    • Personal Call To Action--appeal to shared purpose
    • Appeal to Professionals--value proposition of wiki use
    • How to archive your Product
  • Platform for Faculty/Platform for Grad Student fliers

Backlog[edit]

The following tasks are in a parking lot.

Site Architecture Improvement[edit]

  • Template Picture - Build out Template:Picture
  • Category Pages or Redirects? - existing category pages Category:Categories have useful information, and a template which shows all categories... however if you click on a category on a page footer it takes you into the Category namespace. An alternative would be to have category pages redirect to the related Category:Architecture Page and thereby provide information in a mainpage format and style, using customized Content Templates suited to Page Type instead of the native category page lists.
  • Onboard OCR - https://www.mediawiki.org/wiki/Extension:TikaAllTheFiles allow OCR of uploaded PDF files (historical artifacts) and then becomes part of hte search.
  • ?? - How does CirrusSearch look at PDF content.

Site Detailing Tasks[edit]

  • Font Review - We need a review and revision of fonts and font sizes... many pages use H2 subheadings because in general the headings are both too large, and not distinct in style from text. I'd propose a distinct and stylized page title font (similar to the logo), and then subtle but distinct heading fonts that are not so large and spaced out.
  • Support Domain Registration Transfer (FROM #1) - Work with Roger Fuller and Herold at SER and the SER webmaster with domain transfer from Roger to SER to transfer SalishSeaRestoration.org to SER. Create a domain email, and transition SMTP to the new domain.
  • Add Color To Nav Menu - add small pagetype icons to the nav menu to identify the five key page types?
  • Fancy Tree Menus - https://www.mediawiki.org/wiki/Extension:TreeAndMenu allows for construction of tree-form menus based on DPL queries, and may be useful for Infobox links
  • Social Media Share Image Selection - set social media share settings so that an image other than the page type icon shows during social media share

Content Improvement Tasks[edit]

Information Architecture Refinements[edit]

  • Education Categories - we have education as a Social Change Topic, and we have Academic as a type of Workgroup, and a proposal to subdivide by Youth/College. This seems like a poor description of all the institutions and approaches encompassed by education, both as a kind of Workgroup (could all educational institutions just be State/Special District/NGO/Private?) and the purposes of education, which bleed into advocacy depending on your perspectives. This is the one place where a workgroup type category is divided by a effort purpose category, and is an inconsistency.

Community Development Tasks[edit]

Ultimately the platform is strong because it has a community of devoted users. We need a clear program that provides an easy way for users to become involved in the the development of the platform.

  • Value and Roles of Membership - Describe participation in the platform as membership and describe the value that a member gains by participating in the platform. All participation levels are "free" but additional benefits are gained by additional contributions. A guild and hub model can be used to describe place-based vs. topic-based knowledge.
  • Promotional Videos - We'd benefit from a set of video presentations selling the philosophy and value of the platform, and how it can serve your professional practice. This should start with a script.
    • Page Type Architecture -
    • Category Architecture - as elaboration of page type
  • Topic Editor Cultivation - conduct special events where we gather experts on a topic, and complete updates of Master Topic pages and additions to the wiki to represent current best knowledge.
  • Place Mapping - conduct special events where we train people to use the platform to describe the workgroups, efforts and products that are important to a place.

facts or skills acquired by a person through experience or education.

Retrieved from "https://salishsearestoration.org/w/index.php?title=Development_Backlog&oldid=26484"
This page was last edited on 12 December 2024, at 18:47.
The Salish Sea Restoration Platform at salishsearestoration.org is project of The Society for Ecological Restoration, with content offered under a Creative Commons Attribution-ShareAlike 3.0 Unported License. All content is based on private professional contributions, and no content reflects the policies or opinions of agencies or other workgroups. Content may be outdated.
Privacy policy
Disclaimers