alter metamanger table names to reflect the modify_xml task names

Bug #821530 reported by StaceyS
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Scribe2
New
Undecided
Unassigned

Bug Description

To avoid confusion, it would be a good idea to alter the table names in metamanger to reflect what the allowable modify_xml tasks are called (or vice versa). See this table for an example of discrepancies: https://wiki.archive.org/twiki/bin/view/BooksGroup/ModifyXMLTasks

Revision history for this message
Jude Coelho (judec) wrote : Re: [Bug 821530] [NEW] alter metamanger table names to reflect the modify_xml task names

This is a brilliant idea that I support 100%. Can't think of any reason not to do it.

StaceyS <email address hidden> wrote:

>Public bug reported:
>
>To avoid confusion, it would be a good idea to alter the table names in
>metamanger to reflect what the allowable modify_xml tasks are called (or
>vice versa). See this table for an example of discrepancies:
>https://wiki.archive.org/twiki/bin/view/BooksGroup/ModifyXMLTasks
>
>** Affects: ia-techsupport
> Importance: Undecided
> Status: New
>
>--
>You received this bug notification because you are subscribed to
>Internet Archive - Tech Support.
>https://bugs.launchpad.net/bugs/821530
>
>Title:
> alter metamanger table names to reflect the modify_xml task names
>
>Status in Internet Archive - Tech Support:
> New
>
>Bug description:
> To avoid confusion, it would be a good idea to alter the table names
> in metamanger to reflect what the allowable modify_xml tasks are
> called (or vice versa). See this table for an example of
> discrepancies:
> https://wiki.archive.org/twiki/bin/view/BooksGroup/ModifyXMLTasks
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ia-techsupport/+bug/821530/+subscriptions

Revision history for this message
Hank Bromley (hank-archive) wrote :

I believe the reason those meta.xml element names that contain hyphens are mapped to different names in the metadata table is that MySql column names aren't allowed to contain hyphens. So I'm afraid we need to use the versions with underscores in metamgr.

As for scancenter <=> scanningcenter, I have no idea why that was done, but given that we're stuck with the rest of them, there seems little reason to go through the trouble of changing this one.

Revision history for this message
Jude Coelho (judec) wrote :

We could change the way they display in metamgr without changing the field names in the database. If it would reduce bad modify_xml tasks, that's a good reason to do it.

Revision history for this message
Jude Coelho (judec) wrote :

Moved this feature request to Scribe2

affects: ia-techsupport → scribe2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.