Plugin is not recognizing the next accession identifier in sequence for the accession year provided

[armansua]

The Next Accession plugin doesn't seem to be working properly for us. It is not recognizing the next accession identifier in sequence for the accession year provided. I have tried it several times, and even though, there were previously created accessions (for example, the last created accession number is “2022-033", I'm still getting the following accession identifier “2022.001."

Thanks,
Armando

[jackflaps]

Hello! Sorry for the delay, was on vacation and since I'm not at Denver anymore I'm not as actively maintaining this plugin. How do you enter your accession IDs? Do you put everything in the id_0 field (the first part of the four-part identifier) or are you using the second part as well? This plugin makes some assumptions about how accession IDs are entered that might not match what your practice is.

I can't replicate the behavior you're seeing but I am getting a different unexpected result, which is why I'm wondering.

[armansua]

Hi Kevin! And no worries. For our accessions, we use the first three spaces of the four-part identifier, as such: “AM” (first part) – “2020” (second part) - and “001” (third part). Thanks, and let me know if you have any questions, Armando From: Kevin Clair ***@***.***> Sent: Monday, September 20, 2021 8:47 PM To: duspeccoll/next_accession ***@***.***> Cc: Armando Suarez ***@***.***>; Author ***@***.***> Subject: Re: [duspeccoll/next_accession] Plugin is not recognizing the next accession identifier in sequence for the accession year provided (#4) Hello! Sorry for the delay, was on vacation and since I'm not at Denver anymore I'm not as actively maintaining this plugin. How do you enter your accession IDs? Do you put everything in the id_0 field (the first part of the four-part identifier) or are you using the second part as well? This plugin makes some assumptions about how accession IDs are entered that might not match what your practice is. I can't replicate the behavior you're seeing but I am getting a different unexpected result, which is why I'm wondering. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#4 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALLF2AEDKPT2AAAY32D7P6LUC7IWXANCNFSM5DVFL5EA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.