[dspace-tech] Bug or Feature in Rest API ?

[Monika Mevenkamp]

I have been looking at the demo.dspace.org/rest api

https://demo.dspace.org/rest/hierarchy
gives a tree for communities and collections – looking for ‘Sample Community’ 
is listed there

  10673/1
  ff19bb02-4b01-4150-a7ff-997a9a9f89c2
  Sample Community


https://demo.dspace.org/rest/communities/top-communities
lists the top level communities
I expected to find ‘Sample Community’ listed – but can’t find it

Is this a bug or am I abusing the rest API ?

Monika

--
Monika Mevenkamp
OIT Princeton University
701 Carnegie Center – 331C
Phone: 609-258-4161
Skype: mo-meven

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/BL0PR06MB49931C643160BE63FD9EFCEDADE50%40BL0PR06MB4993.namprd06.prod.outlook.com.

Re: [dspace-tech] DSpace 7 accessibility (WCAG / section 508 / etc)

[Tim Donohue]

Hi Jeremy,

Yes, the Demo site of DSpace 7 ( https://dspace7-demo.atmire.com/ )  is a
very early prototype.  That said, the DSpace 7 team does not yet have an
accessibility expert or group working with us (we've attempted to find one
several times on lists, but no volunteers have stepped forward as of yet).
If this is an area of interest to you or others on this list, we would love
to find a way to work with you on reporting and resolving such issues.  The
end goal is to ensure DSpace 7 aligns with these accessibility requirements
once released. However, as you've seeing, this has proven to be challenging
so far without volunteers willing to help contribute to an accessibility
analysis. Our development team is doing our best, but we admittedly haven't
yet run our own accessibility analysis (as development is still very
active).

In any case, we welcome anyone to report accessibility issues as *bugs* in
DSpace 7.  Since these are at the UI level, the easiest way to report them
quickly would be to submit them to GitHub Issues for the "dspace-angular"
project (the new UI): https://github.com/DSpace/dspace-angular/issues   I
can then work to ensure they are categorized & assigned to a developer to
resolve the issues prior to our 7.0 Beta Release.  At the time of our Beta
release, we plan to also run a formal Community Testathon and ask for
institutions to perform a formal accessibility audit.  However, the more
issues we can find *before* Beta, the better off we'll be.  While some
issues may be rather trivial to resolve (especially if they are just
missing HTML tags or attributes), the earlier we get started the better off
we'll all be.

If you have any questions about how to report these issues as bugs, let me
know.  If you or others on this list would like to contribute on a more
regular basis around accessibility, I'd also be interested in talking
further about whether there's enough interest in forming a Working Group or
similar to help the DSpace 7 development team on an ongoing basis.

Thanks for reaching out, and for any bugs you are able to submit.  This is
a much appreciated contribution to the upcoming release!

Tim

On Mon, Jun 17, 2019 at 2:35 AM Jeremy Echols  wrote:

> Hi, I'm working with DSpace 6 and finding that remediation of
> accessibility failures is a huge chore just for our theme alone (requiring
> changes to core Java code and XSL files just to do things like add labels
> to form fields).  As we saw posts about accessibility in the past, we had
> been hoping the situation would have improved for DSpace 7, but looking
> over the demo site hosted by Atmire, it actually appears to have gotten
> significantly worse.
>
> Is there a group dedicated to accessibility for DSpace 7?  Should I be
> filing tickets as I run into problems, or is the demo a very early
> prototype?  Are the core developers aware of the issues and simply haven't
> yet dealt with them?  Some issues are so trivial that it seems unlikely
> that there's widespread awareness, but I know nothing of Angular or how the
> core team operates, so maybe I'm jumping the gun here.
>
> Detailed problems are listed below.  I found these in about fifteen
> minutes, so this is far from an in-depth audit.  Note that many of these
> are WCAG level A -- which means, essentially, that they are critical
> priority and block a large number of users from accessing the site.  It
> also means that under most jurisdictions, a university could be in legal
> trouble if they stood up the site as it exists today.
>
> - The pages have no defined language, e.g., 
> - Over a dozen fields have no labels, particularly within the search
> filter area
> - There are images used as links which have no alt attribute (or other
> alternative text)
> - The search page's filters are tab-accessible, despite being visually
> hidden, so keyboard focus just gets lost for several links
> - There's no way I can figure out to open up the search filters with just
> a keyboard without actually clicking one of the hidden links
> - There's at least one misuse of aria, where an  tag is given a role of
> "button", but its behavior isn't actually button behavior (spacebar doesn't
> activate it, for instance)
> - Some links have a title but no text.  Depending on browser and screen
> reader combination, a user may have no idea what's being presented.
> - I can't figure out how to use the date slider with just a keyboard.
> - There are dozens of instances of low-contrast text
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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 view this discussion on the web visit
> 

Re: [dspace-tech] specify the size or number of downloads

[Tim Donohue]

Hello,

No, DSpace doesn't support this out-of-the-box.   You can however access
restrict files within DSpace to only allow downloads if you are logged in,
or are a member of a specific Group in DSpace.  If you are running your
DSpace behind an Apache Web Server, you also may be able to use Apache
modules/plugins to limit access via IP ranges, etc.  But, in that scenario,
you'd be configuring Apache to restrict access rather than doing anything
in DSpace itself.

If others on this list have suggestions or have done this before locally,
hopefully they'll respond with further hints or tips.

Tim

On Mon, Jun 17, 2019 at 5:26 AM muaz awed  wrote:

> Urgent : can we  specify the size or number of downloads  either for
> groups or individuals to prevent the download of content at random by any
> way.
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/be9c7162-b0d5-438f-84e2-25a4a450046e%40googlegroups.com
> 
> .
>


-- 

Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CACKSJ9PF1%2B0inbLYFGo_8tRzi0-gK1LwRPx9n16LO2uDHRvQmw%40mail.gmail.com.

Re: [dspace-tech] HIJACKED SESSIONs Protection

[Tim Donohue]

Hello,

That ticket you referenced is still open
https://jira.duraspace.org/browse/DS-2030   This means that it's not yet
finished or completed, and therefore it is not in any DSpace release (as of
yet).

So, at this point in time, that referenced code still exists in DSpace 6.3
and has not yet been made configurable.  If you or your team are interested
in helping us complete this ticket, we do accept code contributions (from
anyone) via GitHub.  We have some general code contribution guidelines at
https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines

- Tim

On Mon, Jun 17, 2019 at 1:47 PM Federico Yemurenko <
federico.yemure...@gmail.com> wrote:

> Hi,
>
> Has the IP address based session hijacking protection already been removed
> or made configurable in DSpace 6.3 ?
> (Ref. DS-2030 ).
>
> Please advise and provide more information.
>
> Regards
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/66c7c43c-2602-45d3-83d2-1743452a5941%40googlegroups.com
> 
> .
>


-- 

Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CACKSJ9OnY9EbDo%3Do%3DEObVvDNmiPmOjrZm7nkS60rbGogjegfDg%40mail.gmail.com.

Re: [dspace-tech] DSpace7

[Tim Donohue]

Hi Monika (and all),

While user feedback/testing is welcome at any time, the current plan is to
run a formal "Community Testathon" around the 7.0 Beta release (as that
release will include all features and be more stable).  So, if you are
wanting to follow more formal testing procedures, it'd be best to wait for
Beta.  However, if you are more of a "do it yourself" or "early adopter"
tester, honestly anyone can start testing & reporting bugs
immediatelyyou would just need to report those bugs via JIRA (
https://jira.duraspace.org/), or (if they are specific to the new UI) they
could be submitted via GitHub Issues (
https://github.com/DSpace/dspace-angular/issues).  Keep in mind that
currently there are quite a few missing features (e.g. all statistics, and
a large number of Administrative features), so early testers should try to
concentrate more on giving feedback on features that already exist.

In summary, testing is always welcome, and you and others are welcome to
begin reporting bugs / usability issues immediately.  However, our formal
Testathon won't be held until 7.0 Beta is released (exact timeline TBA, but
it's at least a few months off at a minimum). That said, obviously, any
early testing will help us catch bugs/issues even before the Community
Testathon, and it is a way to contribute in a less technical fashion.

If you have other questions, please let us know on this list.

Tim

On Tue, Jun 18, 2019 at 9:48 AM Monika Mevenkamp  wrote:

> I finally took the time to have a look at the demo site. Looks like a lot
> of good progress.
>
> Congrats and thank you to all of you who have put in the effort !
>
>
>
> What is the interest level on getting users/tester feedback at this point
> ?
>
> Maybe I (or others) can help out on that end. Since testing is not quite
> as time intensive as actual coding  there is possibly a bigger pool of
> volunteers.
>
>
>
> Monika
>
>
>
> --
>
> Monika Mevenkamp
> OIT Princeton University
>
> 701 Carnegie Center – 331C
> Phone: 609-258-4161
> Skype: mo-meven
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/BL0PR06MB4993D5735A46A6DEF5C2E035ADEA0%40BL0PR06MB4993.namprd06.prod.outlook.com
> 
> .
>


-- 

Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CACKSJ9OxhWHF_BdU%2B7SeTvcEw0%2BSVUxaBOUTxKoyrNRHQaLVVQ%40mail.gmail.com.

Re: [dspace-tech] SolrCore Initialization Failures

[Tecnico UnComa]

Well I fix it this way:

Following this guide I install Tomcat9 under dspace user:

https://linuxize.com/post/how-to-install-tomcat-9-on-ubuntu-18-04/

I test this way because it seems to be a permission problem. I tried 
changing permissions and owner before but nothing changes. I don't know 
why. Anyway... It works now.

El martes, 18 de junio de 2019, 17:58:43 (UTC-3), Tecnico UnComa escribió:
>
> Hi ppl. I had the same problem.
> I was running Dspace 6.3 into Ubuntu 18.11 with Tomcat 8. Las week I 
> do-release-upgrade (18.11 -> 19.04). Then, because Ubuntu 19.04 don't use 
> Tomcat 8, I need to install Tomcat 9. Everything works fine except Solr. 
> The problems seems to be permissions, but I already changed and nothing 
> happens. The error is always the same:
>
> https://pastebin.com/tPA7r7BF
>
> I tried adding dspace to tomcat group and tomcat to dspace.
> I chown tomcat:tomcat to /dspace/solr
> I assign -just to test- chmod 777 to solr.
>
> Nothing different happend.
>
> Thanks
>
> El martes, 18 de junio de 2019, 10:45:03 (UTC-3), Mark H. Wood escribió:
>>
>> On Fri, Jun 14, 2019 at 11:03:57AM -0700, Dyego Cavalieri wrote: 
>> > I have the following in the Solr after installing dspace 6.3 
>> > 
>> >- *search:* 
>> >   
>>  org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
>> >Cannot create directory: /dspace/solr/search/data/index 
>> >- *oai:* 
>> >   
>>  org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
>> >Cannot create directory: /dspace/solr/oai/data/index 
>> >- *authority:* 
>> >   
>>  org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
>> >Cannot create directory: /dspace/solr/authority/data/index 
>> >- *statistics:* 
>> >   
>>  org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
>> >Cannot create directory: /dspace/solr/statistics/data/index 
>> > 
>> > How do i fix this ? 
>>
>> The first thing I would do is to check the ownership and permission 
>> masks of the /dspace/solr directory and everything below it.  The 
>> Servlet container (Tomcat, typically) must be able to read and write 
>> these directories.  The simplest way to ensure that is for them to be 
>> owned by the account which runs the container. 
>>
>> -- 
>> Mark H. Wood 
>> Lead Technology Analyst 
>>
>> University Library 
>> Indiana University - Purdue University Indianapolis 
>> 755 W. Michigan Street 
>> Indianapolis, IN 46202 
>> 317-274-0749 
>> www.ulib.iupui.edu 
>>
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/7e63b9d1-0ea5-4a55-8fea-a8e6b49250b1%40googlegroups.com.

Re: [dspace-tech] Best practice to modify existing classes

[Wenz, Armin]

Hi Claudia,

I want to change the filename for uploaded files to a name composed of
author-title-timestamp.extension. Therefore I modfified
org.dspace.submit.step.UploadStep.processUploadFile() and
org.dspace.app.webui.servlet.admin.EditItemServlet.processUploadBitstre
am().

BTW: We are using DSpace 6.3 and your suggestion worked. 

Thanks


Am Montag, den 17.06.2019, 15:35 +0200 schrieb Claudia Jürgen:
> Hello Armin,
> 
> with which version of DSpace are you working and what are you trying
> to
> overlay?
> 
> Depending on what you want to oververlay, you might be missing a
> dependency in
> [dspace-src]/dspace/modules/jspui/pom.xml
> Most likely
>  
>  javax.servlet
>  jsp-api
>  2.0
>  provided
>  
> as this is used in org.dspace.app.webui.jsptag and customizing the
> ItemTag.java is a common use case.
> 
> Hope this helps
> 
> Claudia Jürgen
> 
> 
> Am 17.06.2019 um 15:08 schrieb Wenz, Armin:
> > Hi all,
> > 
> > I want to modify existing class files in the dspace-api and dspace-
> > jspui tree, but keep the original files (the original source tree)
> > intact, so that I can still update Dspace without loosing my
> > changes
> > with the next update. Therefore I copied the files I want to modify
> > to
> > dspace/modules/additions (the api) and dspace/modules/jspui.
> > 
> > The problem (as you probably guess) is now, that I cannot compile
> > my
> > classes due to missing import files.
> > 
> > Either my approach is wrong or I missed something. Searched the
> > tech
> > group and the wiki but haven't found anything appropriate.
> > 
> > So, is there a HOWTO or Best Practice doc describing how to modify
> > existing files?
> > 
> > Thanks
> > 
> 
> --
> 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.
> 

-- 

Armin Wenz
Universitätsbibliothek Mainz
Leitung Bibliotheksanwendungen
Jakob-Welder-Weg 12
55128 Mainz
Tel.: +49 6131 39-29830
http://www.ub.uni-mainz.de

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/1560919518.7252.20.camel%40ub.uni-mainz.de.