#34: References to trac
-------------------+--------------------------------------------------------
Reporter: dom | Owner: earle
Type: task | Status: new
Priority: normal | Version:
Severity: normal | Keywords: website
-------------------+--------------------------------------------------------
http://openguides.org/page/information could do with a pointer to trac.
--
Ticket URL: <http://dev.openguides.org/ticket/34>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#9: Custom metadata fields
--------------------------+-------------------------------------------------
Reporter: earle | Owner:
Type: enhancement | Status: new
Priority: normal | Component: openguides
Version: | Severity: normal
Resolution: | Keywords:
--------------------------+-------------------------------------------------
Comment (by ivorw):
The "Address" part of this ticket is #18, and is work in progress
--
Ticket URL: <http://dev.openguides.org/ticket/9>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#9: Custom metadata fields
--------------------------+-------------------------------------------------
Reporter: earle | Owner:
Type: enhancement | Status: new
Priority: normal | Component: openguides
Version: | Severity: normal
Resolution: | Keywords:
--------------------------+-------------------------------------------------
Comment (by ivorw):
A challlenge will be: how to emit optional metadata fields as RDF. Whether
this will need us to define and manage a namespace and DTD is part of it.
Can we rely on the Semantic Web community, Dublin Core, foaf, moz, etc. to
provide a catalogue of suitable taxonomies for everything we need? I think
not.
I need to know what solution we intend for this, as otherwise there's NO
WAY of mirroring the data.
--
Ticket URL: <http://dev.openguides.org/ticket/9>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#40: Metadata for other guides/reviews
------------------------+---------------------------------------------------
Reporter: dom | Owner: dom
Type: enhancement | Status: new
Priority: normal | Component: openguides
Version: | Severity: normal
Keywords: |
------------------------+---------------------------------------------------
From http://oxford.openguides.org/wiki/?Comments
Dom: Perhaps we need specific metadata entries for URLs to other
guides/reviews?
* Could do, yes — I mainly worry about making the edit form overcomplex
and huge. But this is something the RDF people are interested in, so I'll
probably add it. --Kake
--
Ticket URL: <http://dev.openguides.org/ticket/40>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#41: Improvements to wanted pages
------------------------+---------------------------------------------------
Reporter: dom | Owner: dom
Type: enhancement | Status: new
Priority: normal | Component: openguides
Version: | Severity: normal
Keywords: |
------------------------+---------------------------------------------------
From http://oxford.openguides.org/wiki/?Comments
James: How about offering the wanted pages ordered by the number of times
they are wanted as well as by alphabetical ordering?
* Oh, nice idea. That'll require a patch to CGI::Wiki, so I'll have a
think about it. --Kake
* Might also be nice to replicate Wanted Nodes as a special case in
OpenGuides. --Dom
* Replicate how? --Kake
* I explained myself badly. What I mean is that Wanted Nodes should be a
"special" page in OpenGuides, such that it is a place people can submit
names of things they want to be added to the guide, and it would be
automatically included in the Wanted Pages page, and automatically deleted
from both pages when the node exists. In fact, it's probably not that
important to even have a list of the pages people have "manually"
requested; it would just be a case of having a special case for the
"backlink". I hope that makes slightly more sense. --Dom
--
Ticket URL: <http://dev.openguides.org/ticket/41>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project