-
Notifications
You must be signed in to change notification settings - Fork 34
make accession ID format institution-dependent #59
Comments
|
also compare with Ghini/ghini.desktop#9. the current list is not from ITF2, the field has an ITF2 description. I think you are not focusing on the
whereas you want the software to help you distinguish between you might just as well misuse the 'intended location' field! 😈 my thought would be to offer you now not just one accession id format, but several, and for the time being not to make it functionally dependent on any other fields in the accession.
this could be applied to 1.0 as well as to 1.1 |
the code for interpreting this is quickly in place. we still miss:
|
still hard coded format, but not any more hard coded logic.
next step would be to store them in the database. relates to Bauble/bauble.classic#59
I have a situation here where we have decided that the first part of the current accession number system must represent the year that the accession (physical item) entered the gardens. So if we planted the plant in late December and I am only now getting time to enter them into the database I am having to change the 2016.xxxx to 2015.xxxx This means I then have to work out the next number in the sequence. A minor nuisance but it would be nice if bauble offered the next in the sequence as a kind of auto-fill option. Also, for all older plants that I am back accessioning, to denote that we don't know exactly when they were planted we give them four capital letter x, as in XXXX, as the first section of the accession number so the accession number looks literally like this XXXX.1098 so the same issue applies here. Every accession (and this is one of the big task I am on at the moment) I enter with the XXXX accession number I have to remember what the last number was. Will what your suggesting provide a solution for this scenario? |
yes, it definitely would. it does not offer you the option "previous year", but you can edit the formats so you keep |
you can already try it out, you need install ghini-1.0 and checkout and install ghini-1.0-dev. |
I can support the format |
just to hear from users how they feel about the functionality.
…the database. still to implement, the interface to add them to the database. related to Bauble/bauble.classic#59
… one. otherwise leave it to the default value `%Y%PD####` related to Bauble/bauble.classic#59
Looks really good! |
From @mfrasca on April 29, 2015 21:5
different gardens use different ID formats for accessions.
in Mompox we just adopted the Bauble standard (year+4.digit) and it served us good,
but here at the JBQ in Quito they already have a 6.digit code for accessions.
at the BTUU in Utrecht they use still an other (much longer) format.
it would be practical if one could specify the accession code format in the institution definition.
the input should then be validated against the format. (maybe an other issue?)
Copied from original issue: mfrasca#84
The text was updated successfully, but these errors were encountered: