<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.talis.com/tdn" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Talis Developer Network - Deleted works - Comments</title>
 <link>http://www.talis.com/tdn/node/1680</link>
 <description>Comments for &quot;Deleted works&quot;</description>
 <language>en</language>
<item>
 <title>Thank you!</title>
 <link>http://www.talis.com/tdn/node/1680#comment-407</link>
 <description>&lt;p&gt;Thank you Brian that is really helpful.&lt;/p&gt;
&lt;p&gt;Perhaps I&#039;d better go down the Alto route after all...!&lt;/p&gt;
</description>
 <pubDate>Mon, 13 Nov 2006 10:11:19 +0000</pubDate>
 <dc:creator>Wes</dc:creator>
 <guid isPermaLink="false">comment 407 at http://www.talis.com/tdn</guid>
</item>
<item>
 <title>deleted works</title>
 <link>http://www.talis.com/tdn/node/1680#comment-406</link>
 <description>&lt;p&gt;If you have a look at the work_logdelete.pl script it is not only the WORKS table that is changed.&lt;/p&gt;
&lt;p&gt;The CONTROL_NUMBER table contains a list on control numbers and the script physically deletes any rows related to the WORK_ID in question.  The CONTROL_NUMBER table also has a unique id attribute called NUMBER_ID that takes values from the CONTROL_NUMBER_RID table. Everytime a new row is inserted in the CONTROL_NUMBER table the value in the RID table is updated and then the new value used in the CONTROL_NUMBER table.&lt;/p&gt;
&lt;p&gt;The full attributes in the table are&lt;br /&gt;
                  NUMBER_ID,&lt;br /&gt;
                  NUMBER,&lt;br /&gt;
                  MAIN,&lt;br /&gt;
                  WORK_ID,&lt;br /&gt;
                  SUBFIELD_OCC,&lt;br /&gt;
                  COLLECTION_ID,&lt;br /&gt;
                  PRIOR_ID &lt;/p&gt;
&lt;p&gt;The rows in this table would also have to be rebuilt.  The main issue would be to make sure the NUMBER_ID values were unique and that the CONTROL_NUMBER_RID table was updated to avoid conflicts e.g. duplicate CONTROL_ID values trying to be inserted by the on-line.  The MAIN attribute would be &quot;T&quot; and the last three can have the value of 0.&lt;/p&gt;
&lt;p&gt;It is also possible that rows in WORK_WORK_LINK were also deleted if they existed.&lt;/p&gt;
&lt;p&gt;The safest option is to recreate the works through Alto but if you do update the database it would be important that you test any changes on the MIS server and that you are happy  before making any changes on the live system.&lt;/p&gt;
&lt;p&gt;Brian Crampton&lt;br /&gt;
Developer, Talis&lt;/p&gt;
</description>
 <pubDate>Mon, 13 Nov 2006 09:05:56 +0000</pubDate>
 <dc:creator>Brian Crampton</dc:creator>
 <guid isPermaLink="false">comment 406 at http://www.talis.com/tdn</guid>
</item>
<item>
 <title>Deleted works</title>
 <link>http://www.talis.com/tdn/node/1680</link>
 <description>&lt;p&gt;Due to my (over zealous!) use of work_logdelete, we have about a dozen newly catalogued records which have been deleted as they had not yet had any items attached. &lt;/p&gt;
&lt;p&gt;I have changed their status from 9 (deleted) to 0 (catalogued) in the WORKS table and pushed them into the WORK_UPDATE table but we still just get &quot;No records found&quot; when we search for them in Alto. &lt;/p&gt;
&lt;p&gt;Am I missing a small but vital piece of sql to make them magically reappear or do I really have to input all of that data by hand...&lt;/p&gt;
&lt;p&gt;Many grateful thanks to anyone who can help!&lt;/p&gt;
&lt;p&gt;Wes&lt;br /&gt;
University of Northampton&lt;/p&gt;
</description>
 <comments>http://www.talis.com/tdn/node/1680#comments</comments>
 <category domain="http://www.talis.com/tdn/taxonomy/term/60">Talis Library System</category>
 <pubDate>Fri, 10 Nov 2006 15:51:40 +0000</pubDate>
 <dc:creator>Wes</dc:creator>
 <guid isPermaLink="false">1680 at http://www.talis.com/tdn</guid>
</item>
</channel>
</rss>
