In 1.6, is it possible to embargo existing items by altering the
database directly?
I know that I can embargo an item by adding items to the metadatavalue
table, providing data for metadata_field_id's 10 and 53, as with the
following SQL:
INSERT INTO metadatavalue (metadata_value_id, item_id,
metadata_field_id, text_value, place) VALUES ("$metadata_value_id",
"$item_id", '10', "$embargo_lift_date", '1');
INSERT INTO metadatavalue (metadata_value_id, item_id,
metadata_field_id, text_value, place) VALUES ("$metadata_value_id",
"$item_id", '53', "$embargo_reason", '1');
But I'm still left with the problem of the bitstreams having anonymous
access granted to them, as reported by the embargo-lifter utility.
Is it possible to modify the database directly to modify the access
rights? I can't seem to find the correct table.
(Or is this all a very bad idea?)
Sean
--
Sean Carte
esAL Library Systems Manager
+27 72 898 8775
+27 31 373 2490
fax: 0866741254
http://esal.dut.ac.za/
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
