Opened 16 years ago

Closed 9 years ago

#9 closed enhancement (duplicate)

Custom metadata fields

Reported by: Earle Martin Owned by:
Priority: high Milestone:
Component: openguides Version:
Severity: trivial Keywords: migrated
Cc:

Description

Mon Jan 3 19:19:15 2005 EMARTIN - Ticket created [Reply] [Comment]

Subject: Custom metadata fields

At present, many pages on OGL have pseudo-metadata like "nearest tube station" which has to be entered into the main text box. It would be advantageous to be able to define arbitrary extra metadata fields with unique names to which user-visible labels would be assigned, and which would subsequently appear in the edit page.

Should an arbitrary field subsequently be removed by a site maintainer, I would suggest that any data entered into nodes using it should be retained in the database, in case the maintainer changes their mind.

Download (untitled) 534b

Mon Jan 3 19:30:51 2005 EMARTIN - Correspondence added [Reply] [Comment]

List discussion of this bug at http://openguides.org/mail/openguides-dev/2005-January/000830.html

Download (untitled) 99b

Change History (5)

comment:1 Changed 16 years ago by Dominic Hargreaves

Component: openguides

comment:2 Changed 16 years ago by Ivor Williams

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.

comment:3 Changed 16 years ago by Ivor Williams

The "Address" part of this ticket is #18, and is work in progress

comment:4 Changed 9 years ago by bob

Priority: normalhigh
Severity: normaltrivial

comment:5 Changed 9 years ago by bob

Keywords: migrated added
Resolution: duplicate
Status: newclosed
Note: See TracTickets for help on using tickets.