Issue 2542 - Document metadata should be configurable
Summary: Document metadata should be configurable
Status: CLOSED DUPLICATE of issue 86606
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: 605
Hardware: PC Other OS
: P3 Trivial with 3 votes (vote)
Target Milestone: ---
Assignee: bettina.haberer
QA Contact: issues@sw
URL:
Keywords:
: 89672 (view as issue list)
Depends on:
Blocks:
 
Reported: 2001-12-14 16:59 UTC by lemuren
Modified: 2008-11-05 20:23 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description lemuren 2001-12-14 16:59:57 UTC
It would be sooo nice, if...

currently, there are only 4 field for user-defined metadata. For large document
collections it's desirable to add more user-defined field. Also, it would be
nice if the Dublic Core set of metadata attributes was integrated into the
default metadata set (for now, only a small subset of DC metadata if availabe
for documents).

If somebody told me where to start, I even would give it a try (seems to me only
the dialog has to be changed to contain a list widget displaying all
user-defined user-data attributes, plus two fields to define new name value
pairs (plus two buttons to add an remove listitems, ok). Very much like msoff,
but without user-defined data-types (dunno what this is really for)). I would
guess there's no internal limit to the number of user-defined meta-data fields
right now anyway. 

greets
pjotr
Comment 1 stefan.baltzer 2001-12-17 10:45:20 UTC
Reassigned to Falko.
Comment 2 falko.tesch 2002-01-02 10:39:05 UTC
This issue is re-assigned to Christian Jansen for further evaluation.
Comment 3 christian.jansen 2002-01-08 14:57:47 UTC
The Properties dialogue has to be completly renewed.This work will be
done in one of the upcomming versions of Oo.o /SO. But thanks for your
feature wish it will be taken into consideration.
Comment 4 ooo 2003-04-11 09:36:44 UTC
How can this issue have the status "FIXED" when the only comment is
that the "Properties dialogue" will be rewritten.

If there is another issue dealing with this so it is a doublé then
please write that so you can see the status.

Issue 8256 is relevant for this issue too.
Comment 5 christian.jansen 2003-06-02 07:46:59 UTC
Reassigned to Bettina.
Comment 6 christian.jansen 2003-06-02 07:47:21 UTC
Reassigned to Bettina.
Comment 7 nkuehn 2005-02-14 16:16:14 UTC
Hello everyone, 
I vote for this issue because I am part of a team at DaimlerChrysler Research &
Technology that currently implements a document generator for technical
documentation which has OpenOffice as the main target format. To fill the
document templates with the meta information from the database we currently have
to abuse the "user field" under Fields->Variables->User Field. 
I suggest changing this functionality because:
- The OASIS Format does not place this limitation, so a valid File is not
interpreted properly by OOo
- I guess People either don't use the feature at all or they need a lot of
user-defined fields
- MS Word compatibility requires it (e.g. open a Word doc with 5 user defined
properties)
- Externally generated OOo files with more than 4 user-defined meta information
fields behave unlogical: A field referencing a user-defined meta tag >4 is not
filled with the correct value or at least let empty, but is filled with the
value of the first user-defined document property.

Nikolaus
Comment 8 jorisgillis 2005-10-30 13:50:18 UTC
I cannot possibly believe that this issue still exists after 4 years!

The limitation on user-defined data makes no sense.
OpenOffice.org should at least leave alone the additional (4+) user-defined meta 
data defined manually in the meta.xml file.
Comment 9 michael.ruess 2008-05-20 09:14:47 UTC
*** Issue 89672 has been marked as a duplicate of this issue. ***
Comment 10 mst.ooo 2008-05-21 12:58:32 UTC
there is now a new API in 3.0 beta for user-defined properties, which is much
saner than the old XDocumentInfo: css.document.XDocumentProperties

there is also a new dialog tab that can display an arbitrary number of
properties and has already been qa'd in CWS doccustomproperties2

unfortunately, that CWS will not be in 3.0 because of missing the UI/translation
freeze by a week or two; expect the dialog in 3.1

@bh:
please reassign this issue to pb

@pb:
this issue is probably a duplicate, and was fixed in your CWS. i guess you
should close it.
Comment 11 Mathias_Bauer 2008-06-04 09:28:26 UTC
This issue will be fixed in 3.1 as mentioned by mst.


*** This issue has been marked as a duplicate of 86606 ***
Comment 12 Mechtilde 2008-11-05 20:23:32 UTC
close the duplicate