Caroline,

I was once overly cavalier about changing ObjectNumbers with SQL and
regretted it. There are lots of dependencies. I'm sure it could be figured
out, but.... When I needed to change a bunch of numbers a second time, I
actually pulled all the records out into spreadsheets, deleted the original
records, then used the Batch Importer to put them back in (and other SQL
updates for info the Importer didn't include).

David


*David Lowe | The New York Public Library**Specialist II, Photography
Collection*

*Photographers' Identities Catalog <http://pic.nypl.org>*

On Thu, Aug 17, 2017 at 10:50 AM, Caroline Im <[log in to unmask]> wrote:

> Hello all,
>
> We have some object numbers entered wrongly by an intern who confused 1
> with I for about a hundred entries. I would like to just edit it directly
> in SQL Server using the Object Number column. However, I do see that there
> are other columns that use run off the Object Number. For example,
> SortNumber is an edited version of ObjectNumber, as is SearchObjectNumber.
>
> Would it be a terrible idea to edit these three fields in SQL Server
> directly, or are there are caveats and other places that use ObjectNumber
> and it would cause a distressful mess?
>
> Is there anything anyone does specially?
>
> TMS does have a "change object number" option but that is per object/
> entry and would take us ages to do one by one.
>
> To unsubscribe, send an email to [log in to unmask] with the
> following commands in the body of the email:
>
>      signoff TMSUSERS
>
>      //  eoj
>
>
> You will receive a confirmation that your subscription has been removed.
>

To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:

     signoff TMSUSERS

     //  eoj


You will receive a confirmation that your subscription has been removed.