Two different ways of write/view credits.

[Jazz_North]

I highlighted this problem some time ago. I have copied my original post for reference.

When you enter the composers from the Record Properties/Tracks/Composer Field, the Record Properties/General/Composer Field is not updated. It appears that these are two completly different fields. I think that this should work in the same way as the artists fields work.

Also when you enter the composer from the Record Properties/Tracks/Composer Field, the composer statistics do not work.

Joe

There are two other relevant differences.

1) If do a query on Composer (Query > Advanced Search), OCD will only find those entered via the Tracks field; if you search on Credits: Authors and Performance, it will on find only those entered via the Album Properties > Credits page.

2) If you want Browse by composer in the left panel, it will only use the entries from the Tracks field.

As both of these are of much more importance to me than statistics, I only use the Tracks field.

It should be noted that composers entered in the composer field on the General tab of Record Properties (in Classical Display) functions the same as those entered on the Track Properties form. But this is useful if there is only one composer or one major composer for an album.

[Joebugs]

As both of these are of much more importance to me than statistics, I only use the Tracks field.

I also only use the Tracks field to enter my composers.

[Balok]

The 'Composer' field to which you refer is an artifact of early versions of OrangeCD which lacked the grid. Yes, I've been using it that long. The problem with simply eliminating it is the obvious: how does one access the data stored in that field? The problem with migrating it is, how does Orange know how to break it up? You used hyphens; I used commas and sometimes semicolons. I am gradually moving the data in my DB, and I don't use the Composer field for new entries, but I'd hate to see the field (and its associated data) just... vanish... until I was done.

The ideal solution would be some kind of prompt driven migration tool (i.e. allows you to view data, specify how to migrate it, and so on). The trouble is that this is an expensive sort of thing to implement and debug for a relatively small return.