Modifying entries - What are the options?
Posted: Wed May 14, 2008 7:07 pm
I've noticed a few incomplete and incorrect serial numbers, primarily from collected instruments, which can be completed thanks to the data within the register, but there is no method to do so other than contacting Gil or Peter at each occurance.
One example is a collected instruments entry from 1966, with the serial number FD?498. One of the great values of the registry, is that we now know that this serial should read FD1498. The problem is that it is a very slow process for Gil or Peter to update these one at a time, and probably not worth the effort.
Would it be worth the effort if there was a simpler way to perform the change? Possiblly a 'change entry' request webform, or similar with just the pertinant information and a quick justification? Perhaps scanning serial numbers to identify those that don't fit the pattern? (Using FD as an example, we can see that the highest FC so far is FC944 and the lowest FE so far is FE1562, so all FDs must fall somewhere between 945 and 1561. Can this knowledge be used to create a rule for logging entries, whereby the database looks at entries each side of the relevent entry and dictates the conditions that must be met?
As far a incorrect entires go, I've seen a few '7's which should be '1's, though this is only evident when you look at the serial numbers surrounding particular instances.). Once again a database rule might identify these errors.
I'm not trying to create more work for anyone, but just wondering if there are easy ways to correct obvious anomalies using the technology available to us?
One example is a collected instruments entry from 1966, with the serial number FD?498. One of the great values of the registry, is that we now know that this serial should read FD1498. The problem is that it is a very slow process for Gil or Peter to update these one at a time, and probably not worth the effort.
Would it be worth the effort if there was a simpler way to perform the change? Possiblly a 'change entry' request webform, or similar with just the pertinant information and a quick justification? Perhaps scanning serial numbers to identify those that don't fit the pattern? (Using FD as an example, we can see that the highest FC so far is FC944 and the lowest FE so far is FE1562, so all FDs must fall somewhere between 945 and 1561. Can this knowledge be used to create a rule for logging entries, whereby the database looks at entries each side of the relevent entry and dictates the conditions that must be met?
As far a incorrect entires go, I've seen a few '7's which should be '1's, though this is only evident when you look at the serial numbers surrounding particular instances.). Once again a database rule might identify these errors.
I'm not trying to create more work for anyone, but just wondering if there are easy ways to correct obvious anomalies using the technology available to us?