Re: CapitalizationStandardEnglish

On Tue, Apr 21, 2009 at 2:23 PM, Pavan Chander <pchander@...> wrote:

 

 

On Tue, Apr 21, 2009 at 11:31 AM, Brian Schweitzer <brian.brianschweitzer@...> wrote:

 

1) We have artist and release level data quality, maybe something similar could be used to deal with track(/any entity) capitalization?

Track data quality?  Sounds like it could get messy.  If anything, perhaps a "Track is correct as is" flag, where ArtistIntent is identified to be overriding standard guidelines for capitalization (or whatever else)?

 

 Well, as I said, something similar to track level data quality; so any sort of "capitalization flag".

2) This may be hackish, (and add to server/ws load?), but what if GC checked the folksonomy tags that were attached to whatever entity was being edited? Certain tags could be treated as "error codes"; so GC would check for any tag with a "gc_" prefix, and then lookup an internal(/external) list of tags and their definitions. 

Yes, this sounds pretty messy to me, at least, and it definitely would increase ws load.  I'm not clear how adding a tag though would really be less work than just manually correcting the capitalization for "On".

  

The idea being that you only have to enter a tag once on a track, instead of having to come around and revert edits every month or two. 

Much less work for the editor(/would-be reverter), especially since adding a tag is so easy to do.

 

 

 

I think a "track caps correct as is" DQ-type of flag would be enough preventative solution for this (or other GC or manual changes to AI titled tracks); a tag-flag for GC would still need someone else to run GC on it to fix the changes, unless I'm missing something in what you're suggesting here...