Re: [dspace-tech] DSpace installation problem

[Creel, James Silas]

Hi Prakash,

Make sure that your institution’s network allows traffic to oss.sonatype.org 
and repo.maven.apache.org.  I’ve had trouble in the past with installations at 
some institutions for this reason.

James

From:  on behalf of prakash das 

Date: Thursday, July 7, 2016 at 1:19 AM
To: DSpace Technical Support 
Subject: [dspace-tech] DSpace installation problem

when in run "mvn package" in dspace it shows errors.



C:\dspace-5.5-src-release\dspace>mvn package
[INFO] Scanning for projects...
Downloading: 
https://oss.sonatype.org/content/repositories/releases/org/sonatype/oss/oss-parent/9/oss-parent-9.pom
Downloading: 
http://maven.restlet.org/org/sonatype/oss/oss-parent/9/oss-parent-9.pom
Downloading: 
https://repo.maven.apache.org/maven2/org/sonatype/oss/oss-parent/9/oss-parent-9.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.dspace:dspace-parent:5.5: Could not 
transfer artifact org.sonatype.oss:oss-parent:pom:9 from/to sonatype-releases 
(https://oss.sonatype.org/content/repositories/releases/): oss.sonatype.org and 
'parent.relativePath' points at no local POM @ org.dspace:dspace-parent:5.5, 
C:\dspace-5.5-src-release\pom.xml, line 20, column 13
 @
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.dspace:dspace:[unknown-version] 
(C:\dspace-5.5-src-release\dspace\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for org.dspace:dspace-parent:5.5: Could 
not transfer artifact org.sonatype.oss:oss-parent:pom:9 from/to 
sonatype-releases (https://oss.sonatype.org/content/repositories/releases/): 
oss.sonatype.org and 'parent.relativePath' points at no local POM @ 
org.dspace:dspace-parent:5.5, C:\dspace-5.5-src-release\pom.xml, line 20, 
column 13: Unknown host oss.sonatype.org -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] 
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
--
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-tech@googlegroups.com.
Visit this group at 
https://groups.google.com/group/dspace-tech.
For more options, visit 
https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] exclude display of values from certain metadata fields

[Monika Mevenkamp]

Is it possible in JSPUI to define a no-show list  of metadata fields (used on 
items), such 
that values for those fields will be shown only to users that are specially 
authorized. 

I plan to build a custom feature that keeps track of status in metadata values; 
but I don’t 
want regular users to be able to see those values. Along with this we’ll have 
employee 
ids on items. While the ids are not a big secret we don’t want to advertise 
them broadly either, 

Monika


—
Monika Mevenkamp
Digital Repository Infrastructure Developer
Princeton University
Phone: 609-258-4161
Skype: mo-meven



-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Collection admin cannot assign DEFAULT_READ access when editing a collection

[strujill]

I am the system administrator for my institution's install of DSpace 
(version 5.3, XMLUI) and am working with a researcher whom I've given 
collection admin privileges. I want to allow this researcher full (or most) 
admin privileges over their collection, however we discovered that although 
the collection admin can assign other admins and submitters to the 
collection, they *cannot assign anyone read access to the collection, or 
even view to the DEFAULT_READ group list for their collection*. 

When you go to the Edit Collection page as a collection admin (i.e. not a 
super admin) you will see that the option to delete the DEFAULT_READ group 
is greyed out with a note that reads "system administrators only", and if 
you click on the link to the READ group you are denied access based on 
insufficient privileges. I've attached screenshots here. 

Does anyone now of a configuration or a patch that will allow collection 
admins the ability to assign (or at least view) the DEFAULT_READ group 
members for their collection? This seems like a real oversight in 
delegating admin responsibilities to collection owners and I'd be curious 
to know more about the reasoning behind it. 

Any information would be greatly appreciated as this may be a deal breaker 
for using DSpace as the repository for this particular researcher's work. 

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: DB Migration when adding new metadata field

[Pantelis Karamolegkos]

Ηi Claudia,

so, if I undestand correctly, adding a new metadata field to an existing 
schema (say dc for example) is a 3 step process?

1. Addition of the field in the following admin form



2. Addition in the input-forms.xml

3. Addition in the registries, i.e. in our case dublin-core-types.xml?

Is that correct?

(In my case I carried out the first 2 steps, and the field was indeed 
added...I just wanted to know how the db migration will take place so 
someone who checks out my code has the new field in his db instance)

Thanks,

P.K.

On Friday, July 8, 2016 at 5:07:17 PM UTC+3, Pantelis Karamolegkos wrote:
>
> When adding a new metadata field through the respective admin form (in an 
> existing schema. e.g. dc), do we also have to manually add the respective 
> flyway migration script under org.dspace.storage.sqlmigration. ?
> Otherwise how will the new field be added to the database of someone who 
> checks out our code from the branch we are working on?
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] DB Migration when adding new metadata field

[Claudia Jürgen]

Hi Pantelis,

you can add metadata fields, bitstream formats to the respective
registries in:
https://github.com/DSpace/DSpace/tree/master/dspace/config/registries
Thus on a fresh install the entries added to the instance via the UI
will also be availble for a fresh install from your source code.

Hope this helps

Claudia Jürgen


Am 08.07.2016 um 16:07 schrieb Pantelis Karamolegkos:

When adding a new metadata field through the respective admin form (in an
existing schema. e.g. dc), do we also have to manually add the respective
flyway migration script under org.dspace.storage.sqlmigration. ?
Otherwise how will the new field be added to the database of someone who
checks out our code from the branch we are working on?



--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia.juer...@tu-dortmund.de
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist 
ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese 
E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und 
vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform 
(mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen 
Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is 
solely intended for the recipient. If you are not the intended recipient of 
this e-mail please contact the sender and delete this message. Thank you. 
Without prejudice of e-mail correspondence, our statements are only legally 
binding when they are made in the conventional written form (with personal 
signature) or when such documents are sent by fax.

--
You received this message because you are subscribed to the Google Groups "DSpace 
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] DB Migration when adding new metadata field

[Pantelis Karamolegkos]

When adding a new metadata field through the respective admin form (in an 
existing schema. e.g. dc), do we also have to manually add the respective 
flyway migration script under org.dspace.storage.sqlmigration. ?
Otherwise how will the new field be added to the database of someone who 
checks out our code from the branch we are working on?

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: [Dspace-tech] XMLUI Controlled vocabularies attribute closed not working

[Franziska Ackermann]

Hi,

We have the same experience. We are using DSpace 5.5, Mirage2. An 
alternative would be to offer a dropdown list instead via input-forms.xml.
However, this isn't very elegant for longer lists. Could you solve the 
problem?


Best regards,
Franziska Ackermann


Am 08.06.2016 um 14:06 schrieb Alan Orth:

Hi, Jacob. We have the SAME experience as you! We are using DSpace 5.1.

Does anyone know how to prevent the user from adding free-text
vocabulary terms when using controlled vocabularies?

Thank you,

On Thu, Sep 11, 2014 at 11:34 AM, Jacob Andersson
 wrote:

Hi,

The DSpace 4 documentation on "How to invoke a controlled vocabulary from 
input-forms.xml" states that

"The vocabulary element has an optional boolean attribute closed that can be used to force 
input only with the Javascript of controlled-vocabulary add-on. The default behaviour (i.e. without 
this attribute) is as set closed="false". This allow the user also to enter values as 
free text, not selecting them from the controlled vocabulary."

When I set closed="true" I see no effect in XMLUI (works fine in JSPUI though, 
stopping manual input).

Does anyone have any advice or similar experience?

Thanks,

---
Jacob Andersson
Librarian
Library & IT
Malmö University
205 06 Malmö
Sweden
+46-(0)40-66 58387
jacob.anders...@mah.se


--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
___
DSpace-tech mailing list
dspace-t...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


--
You received this message because you are subscribed to the Google Groups "DSpace 
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.