Re: [dspace-tech] Re: Hiding communities/collections from unauthenticated users.

[Paul Münch]

Hello Shaun,

it is possible for you to share a code template here or in a public git
repository?

Many thanks and kind regards,

Paul Münch

Am 12.02.19 um 12:19 schrieb Shaun donovan:
>
> Hi Diego.
>
> I have done this with JQuery. It is a simple solution and it works.
> Let me know if you would like to try it and I will send you the code.
>
> Kind Regards.
>
> Shaun.
>
> On 2019/02/12 09:00, Antti Laurila wrote:
>> Hi!
>>
>> I'll respond on behalf Ilja, we were working on the same project. And
>> the answer is unfortunately no, we did not find a solution to this.
>>
>> BR,
>> Antti
>>
>> On Friday, January 25, 2019 at 4:02:31 PM UTC+2, Diego Brice wrote:
>>
>> IIja, did you finally manage to do this? How?.
>>
>> El miércoles, 14 de septiembre de 2016, 9:40:08 (UTC-3), Ilja
>> Sidoroff escribió:
>>
>> I'm trying to hide some internal communities and collections
>> from unauthenticated users (with DSpace 5.5/XMLUI, but also
>> with upcoming 6.0). How-to in the Wiki has been outdated
>> 
>> (https://wiki.duraspace.org/display/DSPACE/Hide+Community+or+Collection+from+list
>> 
>> )
>> and some other googling turned out advise to filter specific
>> communities/collections in xsl, which I think is prone to
>> breakage in migrations and such (e.g.
>> 
>> http://stackoverflow.com/questions/37122851/hiding-collections-and-sub-collections-in-dspace
>> 
>> ).
>>
>>
>> What I'd like to do is to filter the community/collection
>> list when it is generated. This seems such common
>> requirement, that it might have been implemented already by
>> someone?
>>
>> br,
>>
>> Ilja Sidoroff
>> University of Eastern Finland
>>
>> -- 
>> 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 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.
> -- 
> 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 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.

-- 
Philipps-Universität Marburg | UB 
Digitale Dienste | Deutschhausstraße 9 | D018
Tel. +49 06421 28-24624  
--

-- 
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 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.


signature.asc
Description: OpenPGP digital signature

Re: [dspace-tech] Editing a submitted item

[Tim Donohue]

Hi Evgeni,

To be honest, I don't know whether the UI (either XMLUI or JSPUI) will even
provide the user with a link to edit the Item, regardless of whether he/she
has Item WRITE permissions.  Originally, both UIs allowed Administrators to
edit items.  As noted in my previous message this only began to change in
the DSpace 6 JSPUI.

So, that's a long way of saying, you might need to also modify/customize
the UI to get this to work.  As this is not a feature that DSpace currently
supports out-of-the-box (and I've never tried this before), I don't have
any other specific advice I can currently offer.. Hopefully if someone else
on this list has experience with this they will speak up.  Otherwise, you
could simply try adding an Item WRITE policy and see how the UI reacts to
that.

- Tim

On Tue, Feb 12, 2019 at 2:32 PM Evgeni Dimitrov 
wrote:

> Thank you Tim,
>
> I am wondering will it work if I add in the end of the submission process
> a non-interactive AuthorizationStep?
> It will add to the item a WRITE policy for the submitter.
>
> Best regards
> Evgeni
>
>
>
> On Tuesday, February 12, 2019 at 5:54:20 PM UTC+2, Tim Donohue wrote:
>
>> Hello Evgeni,
>>
>> Unfortunately, as far as I'm aware, this is only supported in DSpace 6.0
>> in the JSPUI when you have Item Versioning enabled. See the documentation
>> here:
>> https://wiki.duraspace.org/display/DSDOC6x/Item+Level+Versioning#ItemLevelVersioning-Allowingsubmitterstoversiontheiritems(JSPUIonly
>> )
>> 
>>
>> See also this answer on StackOverflow:
>> https://stackoverflow.com/questions/42564072/how-to-define-a-group-policy-that-to-allow-submitters-to-edit-only-yours-items-s
>>
>>
>> I expect this will have broader support in a future version of DSpace
>> (possibly even 7.0, but we'll have to see).
>>
>> If others have found ways around this, I'd love to hear them. It's
>> possible there's workarounds I haven't thought of.
>>
>> - Tim
>>
>>
>> On Tue, Feb 12, 2019 at 4:51 AM Evgeni Dimitrov 
>> wrote:
>>
> If a user has "Add" permission for a collection, this user can submit an
>>> item to the collection.
>>> Is there a way to allow this user to edit the metadata of "his" item but
>>> no other items in the collection?
>>> Without changing policies after the submission.
>>>
>>> --
>>> 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...@googlegroups.com.
>>> To post to this group, send email to dspac...@googlegroups.com.
>>
>>
>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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 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.
>
-- 
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 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] Mirage 2 Customisation

[Fitchett, Deborah]

You don’t *need* to create a custom theme, but it may be tidier to do so and 
it’s not hard to.

.scss files are designed to work with SASS and Compass. If you have those 
installed, then you make changes in the .scss file(s) and run the compass 
compile command to get them compiled into the final .css file (which, yes, 
overwrites the default rules).

If your changes are fairly simple and you don’t want to install SASS/Compass 
then you can just find the .css file and make the changes directly. If you’re 
wanting to work with anything responsive, though, probably you do need to work 
with the .scss. (Our own process is that we have Compass on our 
Sandbox/Development environment for developing the style using the .scss files, 
but when we’re happy with it we just copy the .css file to Production.)

You can read more Mirage2 and Compass at 
https://wiki.duraspace.org/display/DSDOC5x/Mirage+2+Configuration+and+Customization
 and https://github.com/DSpace/DSpace/tree/dspace-5_x/dspace-xmlui-mirage2

Deborah

From: dspace-tech@googlegroups.com  On Behalf Of 
Kev Evans
Sent: Wednesday, 13 February 2019 6:42 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Mirage 2 Customisation

Hi

I  need to make some basic customisation to the Mirage 2 Theme. (CSS, Logos, 
Footer links)

Am I correct in my assumptions:

I don't need to create a Custom Theme? If so do I need to follow the same 
process?

The css changes can be made in _style.scss? Will this override the Mirage 2 
theme classes if I use the same elements?

Cheers

Kev
--
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 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.



"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."

-- 
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 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] Editing a submitted item

[Evgeni Dimitrov]

Thank you Tim,

I am wondering will it work if I add in the end of the submission process a 
non-interactive AuthorizationStep?
It will add to the item a WRITE policy for the submitter.

Best regards
Evgeni


On Tuesday, February 12, 2019 at 5:54:20 PM UTC+2, Tim Donohue wrote:
>
> Hello Evgeni,
>
> Unfortunately, as far as I'm aware, this is only supported in DSpace 6.0 
> in the JSPUI when you have Item Versioning enabled. See the documentation 
> here: 
> https://wiki.duraspace.org/display/DSDOC6x/Item+Level+Versioning#ItemLevelVersioning-Allowingsubmitterstoversiontheiritems(JSPUIonly
> ) 
> 
>
> See also this answer on StackOverflow: 
> https://stackoverflow.com/questions/42564072/how-to-define-a-group-policy-that-to-allow-submitters-to-edit-only-yours-items-s
>  
>
> I expect this will have broader support in a future version of DSpace 
> (possibly even 7.0, but we'll have to see).
>
> If others have found ways around this, I'd love to hear them. It's 
> possible there's workarounds I haven't thought of.
>
> - Tim
>
>
> On Tue, Feb 12, 2019 at 4:51 AM Evgeni Dimitrov  > wrote:
>
>> If a user has "Add" permission for a collection, this user can submit an 
>> item to the collection.
>> Is there a way to allow this user to edit the metadata of "his" item but 
>> no other items in the collection?
>> Without changing policies after the submission.
>>
>> -- 
>> 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...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> 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 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: DOI DATACITE schema 4.1

[Tim Donohue]

Hello Massimiliano,

Since you are running DSpace 5.6, you'd have two options to get to DataCite
v4.1 compatibility:

   - Either you should upgrade to DSpace 6.3 (the latest version of 6.x),
   and then apply this patch https://github.com/DSpace/DSpace/pull/2321
   - Or, you would need to apply *two* patches to DSpace 5.x.  First, you'd
   have to apply the fixes to update to DataCite schema v3.1 :
   https://github.com/DSpace/DSpace/pull/1197  (This is the fix that was
   included as part of 6.0). Then you would need to apply this patch:
   https://github.com/DSpace/DSpace/pull/2321

You also may want to simply see if upgrading to DSpace 6.3 would *solve*
the issues you are having.   In your original email, it was unclear if you
absolutely *must* be running DataCite schema v4.1, or if possibly DataCite
schema v3.1 would work.  So, honestly, my recommendation would be to first
start up a test server with DSpace 6.3 on it to see if compatibility with
DataCite schema 3.1 fixes the issues you are seeing.  If so, you may not
even need to apply the patch to update to DataCite schema 4.1.  I cannot
give advice myself on whether upgrading to DSpace 6.3 will solve the issue
or not -- that's likely something you'd need to either test out yourself,
or talk to the DataCite team about.

- Tim





On Tue, Feb 12, 2019 at 12:12 PM Massimiliano CILURZO 
wrote:

> Dear Tim.
> I'm running DSpace 5.6 I could install this patch on it?
> I would like to try this patch, If you tell me that I could use it only on
> DSpace 6.0 I'll try it first on a test server with DSpace 6.0.
> If I can I'll try to help for this patch with some notes about it.
> Thanks
> Best regards
> Massimiliano
>
> Il giorno martedì 12 febbraio 2019 17:13:42 UTC+1, Tim Donohue ha scritto:
>
>> Massimiliano,
>>
>> Just a follow-up to Mark's previous note.  DSpace 6.x is using DataCite
>> Schema 3.1 (so if you are seeing Schema 2.2, I'm assuming you aren't using
>> the latest DSpace), see this update which was released in DSpace 6.0:
>> https://jira.duraspace.org/browse/DS-2924
>>
>> As Mark notes, we have a pending update to DataCite Schema 4.1, which
>> likely won't be released until 6.4 (at the earliest).  If you are already
>> running DSpace 6.x, this patch should be relatively easy to apply
>> immediately. If you are able to help test this patch, then we'd appreciate
>> it if you could add notes to the patch (in GitHub), as that will allow us
>> to more easily approve/merge the change in time for 6.4.  Again, here's
>> where this patch is: https://github.com/DSpace/DSpace/pull/2321
>>
>> If you have further questions, let us know on this list.
>>
>> Tim
>>
>> On Mon, Feb 11, 2019 at 8:00 AM Mark H. Wood  wrote:
>>
> On Monday, February 11, 2019 at 4:23:53 AM UTC-5, Massimiliano CILURZO
>>> wrote:

   The DOI Datacite schema now is arrived to 4.1, we have on DSpace
 version 2.2 and it could have some problem with the new managemant software
 of DATACITE.
 With a schema version 2.2 it cuold be impossible to do an update via
 the "DOI DataCite Fabrica" system.
 So I would like to know if it is possible to update this schema to 4.1.

>>>
>>>
>>> There is a patch to upgrade to 4.0:
>>> https://github.com/DSpace/DSpace/pull/2321 which has not yet been
>>> merged.
>>>
>>>
>>> --
>>> 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...@googlegroups.com.
>>> To post to this group, send email to dspac...@googlegroups.com.
>>
>>
>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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 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.
>
-- 
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" 

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

[Massimiliano CILURZO]

Dear Tim.
I'm running DSpace 5.6 I could install this patch on it?
I would like to try this patch, If you tell me that I could use it only on 
DSpace 6.0 I'll try it first on a test server with DSpace 6.0.
If I can I'll try to help for this patch with some notes about it.
Thanks
Best regards
Massimiliano

Il giorno martedì 12 febbraio 2019 17:13:42 UTC+1, Tim Donohue ha scritto:
>
> Massimiliano,
>
> Just a follow-up to Mark's previous note.  DSpace 6.x is using DataCite 
> Schema 3.1 (so if you are seeing Schema 2.2, I'm assuming you aren't using 
> the latest DSpace), see this update which was released in DSpace 6.0: 
> https://jira.duraspace.org/browse/DS-2924 
>
> As Mark notes, we have a pending update to DataCite Schema 4.1, which 
> likely won't be released until 6.4 (at the earliest).  If you are already 
> running DSpace 6.x, this patch should be relatively easy to apply 
> immediately. If you are able to help test this patch, then we'd appreciate 
> it if you could add notes to the patch (in GitHub), as that will allow us 
> to more easily approve/merge the change in time for 6.4.  Again, here's 
> where this patch is: https://github.com/DSpace/DSpace/pull/2321 
>
> If you have further questions, let us know on this list.
>
> Tim
>
> On Mon, Feb 11, 2019 at 8:00 AM Mark H. Wood  > wrote:
>
>> On Monday, February 11, 2019 at 4:23:53 AM UTC-5, Massimiliano CILURZO 
>> wrote:
>>>
>>>   The DOI Datacite schema now is arrived to 4.1, we have on DSpace 
>>> version 2.2 and it could have some problem with the new managemant software 
>>> of DATACITE.
>>> With a schema version 2.2 it cuold be impossible to do an update via the 
>>> "DOI DataCite Fabrica" system.
>>> So I would like to know if it is possible to update this schema to 4.1.
>>>
>>
>>
>> There is a patch to upgrade to 4.0:  
>> https://github.com/DSpace/DSpace/pull/2321 which has not yet been merged.
>>  
>>
>> -- 
>> 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...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> 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 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] Flat Community List in Mirage 2 Theme.

[Kev Evans]

Hi

How to Flat Community List in Mirage 2 Theme?

Essentially Disable the expandable list. Is this a config option or a 
customisation?

Thanks in advance for the help.

Cheers

Kev

-- 
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 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] Mirage 2 Customisation

[Kev Evans]

Hi 

I  need to make some basic customisation to the Mirage 2 Theme. (CSS, 
Logos, Footer links)

Am I correct in my assumptions:

I don't need to create a Custom Theme? If so do I need to follow the same 
process?

The css changes can be made in _style.scss?  Will this override the Mirage 
2 theme classes if I use the same elements?

Cheers

Kev

-- 
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 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] Discovery Advanced Search in Dspace 6.3

[Kev Evans]

Hi 

I want to display a link to Advance Search Options on the Home page and is 
the Discovery Page. {discover?advanced=true}

How can this be enabled as a default in Dspace 6.3
 
Cheers

Kevin

-- 
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 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] Editing a submitted item

[Tim Donohue]

Hello Evgeni,

Unfortunately, as far as I'm aware, this is only supported in DSpace 6.0 in
the JSPUI when you have Item Versioning enabled. See the documentation
here:
https://wiki.duraspace.org/display/DSDOC6x/Item+Level+Versioning#ItemLevelVersioning-Allowingsubmitterstoversiontheiritems(JSPUIonly
)


See also this answer on StackOverflow:
https://stackoverflow.com/questions/42564072/how-to-define-a-group-policy-that-to-allow-submitters-to-edit-only-yours-items-s


I expect this will have broader support in a future version of DSpace
(possibly even 7.0, but we'll have to see).

If others have found ways around this, I'd love to hear them. It's possible
there's workarounds I haven't thought of.

- Tim


On Tue, Feb 12, 2019 at 4:51 AM Evgeni Dimitrov 
wrote:

> If a user has "Add" permission for a collection, this user can submit an
> item to the collection.
> Is there a way to allow this user to edit the metadata of "his" item but
> no other items in the collection?
> Without changing policies after the submission.
>
> --
> 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 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.
>
-- 
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 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: Hiding communities/collections from unauthenticated users.

[Shaun donovan]

Hi Diego.

I have done this with JQuery. It is a simple solution and it works. Let 
me know if you would like to try it and I will send you the code.


Kind Regards.

Shaun.

On 2019/02/12 09:00, Antti Laurila wrote:

Hi!

I'll respond on behalf Ilja, we were working on the same project. And 
the answer is unfortunately no, we did not find a solution to this.


BR,
Antti

On Friday, January 25, 2019 at 4:02:31 PM UTC+2, Diego Brice wrote:

IIja, did you finally manage to do this? How?.

El miércoles, 14 de septiembre de 2016, 9:40:08 (UTC-3), Ilja
Sidoroff escribió:

I'm trying to hide some internal communities and collections
from unauthenticated users (with DSpace 5.5/XMLUI, but also
with upcoming 6.0). How-to in the Wiki has been outdated

(https://wiki.duraspace.org/display/DSPACE/Hide+Community+or+Collection+from+list

)
and some other googling turned out advise to filter specific
communities/collections in xsl, which I think is prone to
breakage in migrations and such (e.g.

http://stackoverflow.com/questions/37122851/hiding-collections-and-sub-collections-in-dspace

).


What I'd like to do is to filter the community/collection list
when it is generated. This seems such common requirement, that
it might have been implemented already by someone?

br,

Ilja Sidoroff
University of Eastern Finland

--
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 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.


--
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 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] Editing a submitted item

[Evgeni Dimitrov]

If a user has "Add" permission for a collection, this user can submit an
item to the collection.
Is there a way to allow this user to edit the metadata of "his" item but no
other items in the collection?
Without changing policies after the submission.

-- 
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 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.