Dbase & what we are meant to be doing..(IMPORTANT)

carolynwhite2 carolynwhite2 at aol.com
Fri Feb 18 12:13:53 UTC 2005


--- In HPFGU-Catalogue at yahoogroups.com, "dungrollin" 
<spotthedungbeetle at h...> wrote:
> 
>  
> Can we clarify exactly what we're doing? Are we changing codes as 
we review, or making notes? What if we have posts that were coded 
> before certain categories came into existance? I don't want to 
start adding codes and find that I'm messing up somebody else's 
section by adding posts while they're in the middle of it.
> 
> How about we remove all unnecessary codes (which won't upset anyone 
> else's categories), but make a list of posts where extra codes 
> should be added, along with clearer definitions of categories and 
> potential new categories, to be discussed, and then have a sweep 
> through adding categories at the end? 
> 
> Alternatively, we could have an extra category called 'reviewed' 
> (which could be removed afterwards) that gets ticked for all posts 
> that have had codes added in this review. Then you can identify the 
> new posts that turn up in a category that you're working on, and 
you don't need to repeat somebody else's work.
> 


Carolyn:
A word of clarification here. What we are doing is as follows:

1. First consider the definitions which currently exist for the 
category you are dealing with. That's simple if it is one sub-
category, but if your review group consists of several related sub- 
categories (as most do), we need to review what the differences in 
definitions are within that sub-group before cleaning up the posts 
themselves.

In order to do this it is probably necessary to do a fast eye-ball of 
the posts in the sections to see the extent to which they fit the 
definitions or not, and whether any extra categories are needed to 
reflect the range of what you see, or whether existing ones should be 
changed.

2. Once you've done this, please first post to the group about how 
you plan to sort out a category or group of categories. This is 
important because one huge benefit of this exercise is to build 
common agreement on what different categories mean.

3. If everyone is in agreement, then go ahead and do the sort out as 
proposed. 

4. Re the problem of adding/changing codes other than those you are 
specifically dealing with, I think that having another category to 
tick in the admin section is a brilliant idea, Dot, so simple and why 
didn't I think of this!

SO: I am going to add a category -

*********5.6 Review coding*********  

under section 5, Admin Flags, and could everyone, *without fail*, 
religiously tick this if they make a change to a post that could 
affect categories other than the ones they are supposed to be dealing 
with at the time ?

Then, although it might be rather a long list, at least we have in 
one place all the ones to double check at the end of this process.

Everyone happy with this?

Large quantity of Honeydukes best to Dot..

Carolyn







More information about the HPFGU-Catalogue archive