#97: Summary field should be used for description meta tag
-----------------------------------+----------------------------------------
Reporter: earle | Owner: earle
Type: enhancement | Status: new
Priority: normal | Milestone: 0.53
Component: london.openguides.org | Version: svn
Severity: trivial | Keywords: metadata
-----------------------------------+----------------------------------------
The content of the "summary" metadata field should be used to generate an
HTML <meta name="description" content="..."> tag if it has been filled.
--
Ticket URL: <http://dev.openguides.org/ticket/97>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#106: RDF versions of pages should list all contributors
------------------------+---------------------------------------------------
Reporter: earle | Owner: earle
Type: defect | Status: new
Priority: low | Milestone:
Component: openguides | Version: svn
Severity: minor | Keywords: rdf
------------------------+---------------------------------------------------
At present the RDF version of a node only lists the most recent editor as
a <dc:contributor>; it should be all of them (including Anonymous).
--
Ticket URL: <http://dev.openguides.org/ticket/106>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#104: redirect=0 does not stop #REDIRECTs
------------------------+---------------------------------------------------
Reporter: grimoire | Owner: dom
Type: defect | Status: new
Priority: normal | Milestone:
Component: openguides | Version: 0.52
Severity: normal | Keywords:
------------------------+---------------------------------------------------
Example URL:
http://manchester.openguides.org/?Locale_Great_Northern_Centre
When a user attempts to access a node which is a #REDIRECT, they are
automatically redirected. The new page they are viewing tells them which
page they were redirected from, and there is a link to this node with a
"redirect=0" parameter. It's reasonable to assume that this link will
allow you to see or edit the #REDIRECT but in fact it just redirects the
user back to the target of the #REDIRECT.
--
Ticket URL: <http://dev.openguides.org/ticket/104>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#96: Add version numbers to wiki:openguides.org
-------------------------+--------------------------------------------------
Reporter: earle | Owner: earle
Type: enhancement | Status: new
Priority: lowest | Milestone:
Component: trac | Version:
Severity: trivial | Keywords:
-------------------------+--------------------------------------------------
Add another column to wiki:openguides.org for the version of the
OpenGuides software being used by each guide..
--
Ticket URL: <http://dev.openguides.org/ticket/96>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#101: Add Metadata to search indexing
-------------------------------------+--------------------------------------
Reporter: crschmidt(a)crschmidt.net | Owner: dom
Type: defect | Status: new
Priority: normal | Milestone:
Component: openguides | Version:
Severity: normal | Keywords:
-------------------------------------+--------------------------------------
The way I found to do this involves double-indexing all search results,
which is obviously not ideal, but 'works'. Milton Keynes and Boston are
using this. The indexer uses a CGI::Wiki plugin to reindex after the node
is committed -- code for plugin to be attached.
--
Ticket URL: <http://dev.openguides.org/ticket/101>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#100: Merge Boston Macros where relevant
-------------------------------------+--------------------------------------
Reporter: crschmidt(a)crschmidt.net | Owner: dom
Type: defect | Status: new
Priority: normal | Milestone:
Component: openguides | Version:
Severity: normal | Keywords:
-------------------------------------+--------------------------------------
@INCLUDE_NODE and @MAP_LINK macros are probably relevant for more than
just Boston guide. Merge with main tree.
--
Ticket URL: <http://dev.openguides.org/ticket/100>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#42: "About" output
------------------------+---------------------------------------------------
Reporter: earle | Owner: earle
Type: enhancement | Status: new
Priority: low | Component: openguides
Version: | Severity: minor
Keywords: rdf |
------------------------+---------------------------------------------------
There should be an "action=about" method in wiki.cgi that produces an
"About this guide" page, with information about the OpenGuides install
(version number, logo, link to website, etc). I figure a link to this
could replace the standard OpenGuides link at the bottom of every page.
There should also be a link on that page to "action=about;format=rdf"
which would produce [http://usefulinc.com/doap/ DOAP] output about the
software.
--
Ticket URL: <http://dev.openguides.org/ticket/42>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#14: test failure with no plucene
------------------------+---------------------------------------------------
Reporter: dom | Owner:
Type: defect | Status: new
Priority: low | Milestone:
Component: openguides | Version: 0.47
Severity: normal | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Comment (by crschmidt(a)crschmidt.net):
Do we want to support non-plucene code anymore? Search::II was more of a
PITA than it was worth, and I'm pretty sure most guides use Plucene these
days.
--
Ticket URL: <http://dev.openguides.org/ticket/14>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project