[Dspace-general] ADD metadata
Rodrigo Castro Artigas
following error:
[root@SDSPACE config]# /P9i/dspace/bin/./dsrun
org.dspace.app.itemimport.ItemImport -a -e dsp...@alerta.cl -c "7" -s
"/alerta/dspace/discurso1" -m "1"
Destination collections:
Owning Collection: Ex Rector Juan de Dios Vial Correa
Adding items from directory: /alerta/dspace/discurso1
Generating mapfile: 1
Adding item from directory 1
Loading dublin core from /alerta/dspace/discurso1/1/dublin_core.xml
Schema: dc Element: contributor Qualifier: author Value: Vial, Juan
de Dios
Schema: dc Element: date Qualifier: available Value: 18-07-2008
11:05:58
Schema: dc Element: date Qualifier: issued Value: 1995
Schema: dc Element: title Qualifier: none Value: A treinta años del
Concilio Vaticano II
Schema: dc Element: language Qualifier: none Value: sp
Schema: dc Element: type Qualifier: none Value: Article
Processing contents file: /alerta/dspace/discurso1/1/contents
Bitstream: 1.pdf
Processing handle file: handle
It appears there is no handle file -- generating one
java.sql.SQLException: Collection 7 has no default item READ policies
at
org.dspace.content.Item.inheritCollectionDefaultPolicies(Item.java:1911)
at org.dspace.content.InstallItem.installItem(InstallItem.java:156)
at org.dspace.app.itemimport.ItemImport.addItem(ItemImport.java:663)
at
org.dspace.app.itemimport.ItemImport.addItems(ItemImport.java:506)
at org.dspace.app.itemimport.ItemImport.main(ItemImport.java:415)
java.sql.SQLException: Collection 7 has no default item READ policies
please, help me
Rodrigo
Claudia Jürgen
seems as if your collection does not have the policy DEFAULT_ITEM_READ
set. During ingest the rights of an item are created based upon these
rights of a collection:
- DEFAULT_ITEM_READ
- DEFAULT_BITSTREAM_READ
Go to your DSpace installation. Log in as Admin. Go to collection 7 and
click on edit. On the bottom you got "Collection's Authorizations" there
you can check whether the above mentioned authorizations are set.
hope that helps
Claudia
Rodrigo Castro Artigas schrieb:
> Dspace-general mailing list
> Dspace-...@mit.edu
> http://mailman.mit.edu/mailman/listinfo/dspace-general
Rodrigo Castro Artigas
Thanks You!!!!!!!!!!!
Atte.,
Rodrigo
-----Mensaje original-----
De: Claudia Jürgen [mailto:Claudia...@ub.uni-dortmund.de]
Enviado el: Jueves, 24 de Julio de 2008 3:34
Para: Rodrigo Castro Artigas
CC: dspace-...@mit.edu
Asunto: Re: [Dspace-general] ADD metadata
gonzalo....@gmail.com
Reed, Marianne A.
Good afternoon! In DSpace 7.6, is there a way to turn off the public display of all license files for the entire repository? There used to be a configuration setting that did this, below, but it is not supported in DSpace 7.x. and I can’t find its replacement, if there is one.
WEB User Interface Configurations--from https://wiki.lyrasis.org/display/DSDOC7x/Configuration+Reference#ConfigurationReference-Thelocal.cfgConfigurationPropertiesFile
General Web User Interface Configurations
|
Property: |
webui.licence_bundle.show |
|
Example Value: |
webui.licence_bundle.show = false |
|
Informational Note: |
Sets whether to display the contents of the license bundle (often just the deposit license in the standard DSpace installation). UNSUPPORTED in DSpace 7.x |
If the solution involves limiting the access rights for the License bundles to Administrators, or for particular files in the license bundles, I’d be happy to do that. However, I’m relatively new to DSpace 7.6 and don’t know if there is a way to do this globally, and not item by item.
Any help that you can give would be greatly appreciated! Thank you!
-- Marianne Reed
Marianne Reed (she/her/hers)
Digital Publishing & Repository Manager
Watson Library, Room 470-G
University of Kansas Libraries
Matyas F. Bajger
Hello!
I have had to solve probably the same recently. In our case, we do not need license files and bitstreams at all. So I modified submission-forms where I removed confirming and adding the license (in /dspace/config/item-submission.xml comment lines: <!--step id="license"/--> ).
Then I removed all license bitstreams and bundles that has been
added before.
Might this can be suitable for you case too.
Best!
Matyas F. Bajger
University of Ostrava, University Library
https://library.osu.eu https://eduo.osu.cz
--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups "DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-communi...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dspace-community/DM8PR01MB68707B44EE4A3E6608C384F8C5FF2%40DM8PR01MB6870.prod.exchangelabs.com.
Reed, Marianne A.
Thank you for your reply, Matyas! Much appreciated.
Your solution is helpful if license files are not wanted, but we do want to keep using license files, so we need to figure out how best to hide them from the public display for both existing and future submissions.
Best regards,
Marianne
To view this discussion visit https://groups.google.com/d/msgid/dspace-community/8c919d12-6b94-46ce-b609-048ee2730a1f%40seznam.cz.
Erin Jerome
HI Marianne,
We haven’t actually implemented this change as a collection default, but we experimented with completely removing the bundle level permissions for the license bundle and that appeared to do the trick. Like you, we require the license, but don’t love that it’s visible. We’d initially tried making the bundle admin only, but that just made the lock icon appear.
Best,
Erin
--
Erin Jerome, PhD
Pronouns: she/her/hers
Library Publishing & Institutional Repository Librarian
Music & Dance Department Liaison
University of Massachusetts, Amherst
Schedule an appointment with me
https://orcid.org/0000-0002-3671-7447