[mb-users] Adding releases not yet released

[Kuno Woudt]

On Tue, Sep 04, 2007 at 11:33:59PM +0200, Philipp Wolfer wrote:
> I wanted to raise a topic I run into regularly. Often "releases" are
> added before they are actually released. Some times such edits get
> accepted, sometimes they are voted down - the result is pretty random
> and depends completely on who is voting for the edits.

I'm in favour of adding these, but with a few rules.  Which you already
have written down on the wiki, but i thought I'd mention them anyway :)

1)  Add an annotation stating the 'release' hasn't been released yet
and any data will need to be verified when it has.

2) Set data quality low.

3) Enter expected date in the release event.


Some people seem to be against 3), entering future dates.  Which seems a
bit odd to me, for the following reasons:

    - you can't enter label/catalog # info without a date.

    - having a machine readable date will allow searching for future
    release dates, which can be useful for all sorts of things.
    (for example, it shouldn't be that much work to write a cronjob
     which would notify the original editor on the release day that 
     he/she shouldn't forget to verify the data he/she entered).

--kuno.