Download Firefox: WindowsMac OS X
logo       
Google Custom Search
    AddThis Social Bookmark Button

Re: ID customizations: msg#00027

Subject: Re: ID customizations
Sounds good.  I would be glad to have this come after 1.2, since I am
eager for 1.2 to become stable.

And I would also like the ability to later change a barcode if
needed.

Thanks!

On Mon, Jul 12, 2004 at 09:55:01PM +0300, Christoffer Landtman wrote:
> Hello all,
> 
> Following the discussions lately concerning the customization of both 
> user and book ID:s from the currently specified e.g. "0000000001P" 
> (didn't bother to count the zeros :-)) my thoughts have been confirmed; 
> such an approach needs to be implemented. If this can still be done by 
> Emilda 1.2 stable, I cannot say, but it certainly is high priority.
> 
> However as this seems to be an issue where each and every one has 
> his/her own oppinion the system needs to be really 
> customizeable/portable. Thus I'm asking You for thoughts on what would 
> be the type of approach/solution that You would like to see. I realize 
> that we probably will not all be of entirely the same oppinion, but lets 
> see what we can get cooking :-)
> 
> Here are some of my thoughts, which are entirely on the thought-basis of 
> my bus-trip home today ;-)
> 
> 1. The current style of [numbers][letter] could be replaced with a 
> config field that would be a regexp-syntax that would be used to verify 
> the validity of a code. This would allow virtually any type of book ID, 
> but there is of course a need to have all items using the same 
> "type/syntax" of ID.
> 
> 2. Point 1. could also apply to user ID:s
> 
> 3. When adding an item it would be possible to choose between an 
> automatically generated ID, or e.g. an entirely manually added ID (which 
> would be checked against the supplied regexp) or system generate an ID 
> with a supplied offset (e.g. 200000). The given ID would then be stored, 
> and when once passing e.g. 200000 the next item would have an system 
> generated ID of 200001
> 
> 4. Similar logics could apply to user ID:s.
> 
> 5. Possibility to use some sort of checdigit function, that could either 
> be shipped with Emilda, or alternatively uploaded by an ADMIN.
> 
> Disrigard my ideas totally or comment these, both are more than welcome. 
> I hope I will find the time to implement this issue still into 1.2 as it 
> has gotten more attention than I anticipated.
> 
> Regards,
> 
> -- 
> Christoffer Landtman
> Oy Realnode Ab
> Partner, Sales
> +358 (0)41 510 1073
> landtman@xxxxxxxxxxx
> www.realnode.fi
> _______________________________________________
> Emilda mailing list
> Emilda@xxxxxxxxxxxxxxxxxx
> http://lists.realnode.com/mailman/listinfo/emilda
> 

-- 
Encrypted Mail Preferred:
    Key ID:  8527B9AF
    Key Fingerprint:  E1B6 40B6 B73F 695E 0D3B  644E 6427 DD74 8527 B9AF
    Information:  http://www.gnupg.org/
                                                                                
ASCII ribbon campaign:
()  against HTML email
/\  against Microsoft attachments
    Information:  http://www.expita.com/nomime.html

Attachment: signature.asc
Description: Digital signature

<Prev in Thread] Current Thread [Next in Thread>