Hi Lewatle,
What version of DSpace are you running? If you're using DSpace 1.7.0 or
later, I could help you out with a curation task I wrote to perform a very
similar task... it's much nicer and safer (and easier to reuse) than doing
it manually in SQL, and can be run via the UI on a single item, a collection
of items, a community of items, or even the entire repository!
We've added access rights curation tasks to our regular thesis and research
output workflow, and they're working well so far, because they can perform
bitstream restriction and populate dc.rights at the same time. Since it
sounds like you're going 100% Open Access, your tasks will be even easier
because they only need to populate metadata fields.
Another, more "ad-hoc" way of doing this is exporting the item metadata you
want to update as CSV, filling out the dc.rights column with "2 Publicly
Accessible", then importing the metadata back into DSpace. It's also easy to
revert since your original export could be treated as a 'backup'.
Sorry this isn't an exact answer to your question -- just providing some
non-SQL alternatives to achieving what you want... and they will guarantee
that your indexes are updated, proper errors are thrown if a problem is
encountered, etc...
Cheers!
Kim
On 5 October 2011 20:55, Lewatle Phaladi <[email protected]> wrote:
> Hi All ****
>
> ** **
>
> I want to open closed collections or items and make them available to
> public viewing, I have saw on the following link that is possible:
> http://www.ndltd.org/standards/metadata/etd-ms-v1.1.html#dc.rights I
> thought is a column in metadata * tables and I have opened tables to see if
> they have this column so I can change values to 2 = publicly accessible, any
> advice is appreciated.****
>
> ** **
>
> Regards,****
>
> Lewatle ****
>
> This communication is intended for the addressee only. It is confidential. If
> you have received this communication in error, please notify us immediately
> and destroy the original message. You may not copy or disseminate this
> communication without the permission of the University. Only authorized
> signatories are competent to enter into agreements on behalf of the
> University and recipients are thus advised that the content of this message
> may not be legally binding on the University and may contain the personal
> views and opinions of the author, which are not necessarily the views and
> opinions of The University of the Witwatersrand, Johannesburg. All agreements
> between the University and outsiders are subject to South African Law unless
> the University agrees in writing to the contrary.
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
>
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
