Re: [dspace-tech] Re: dc.identifier.uri for new communities/collections

2024-07-17 Thread 'Bill Tantzen' via DSpace Technical Support
Taking a closer look at the source code for the two choices for identifier
provider classes, I see that VersionedHandleIdentifierProvider.java will
persist an identifier for Community, Collection, or Item DSpaceObjects (it
calls dsoService.addMetadata()).

VersionedHandleIdentifierProviderWithCanonicalHandles.java on the other
hand, will only persist an identifier for Items -- Communities and
Collections are ignored (it calls itemService.addMetadata()).  This class
supports the legacy method of versioning that was used in DSpace 4/5 which
happens to be the method we prefer to use going forward.  I believe that
handles were not persisted as metadata for Communities or Collections prior
to version 6.

This looks like a bug to me --
VersionedHandleIdentifierProviderWithCanonicalHandles is ignoring
Communities and Collections when creating dc.identifier.uri metadata.  It
works similar to the class it replaced in version 5x with regard to
anything that is not an Item.

Thoughts?

On Tue, Jul 16, 2024 at 4:34 PM Bill Tantzen  wrote:

> Just out of curiosity, did *you* try toggling
> to org.dspace.identifier.VersionedHandleIdentifierProviderWithCanonicalHandles
> on your server or did you just go with the default?  Or are there any other
> installs out there that use this older, pre-version 6x strategy?
> ~~Bill
>
> On Tue, Jul 16, 2024 at 4:17 PM DSpace Technical Support <
> dspace-tech@googlegroups.com> wrote:
>
>> Hi Bill,
>>
>> I don't understand how the versioning feature could impact this...as you
>> said, it's not used by Communities & Collections.  It's also odd to me that
>> this odd behavior would *only* impact Communities & Collections, as it
>> should also impact Items if the versioning configuration was to blame.
>> Something isn't adding up here.
>>
>> I can verify the I tested on my end with the default settings of
>> "org.dspace.identifier.VersionedHandleIdentifierProvider" and everything is
>> working.   The Demo Site also has this default setting in place and it's
>> working fine as well: https://demo.dspace.org/  (Demo is running 8.0,
>> but this area of the codebase shouldn't be significantly different between
>> 7.6.2 and 8.0)
>>
>> I'm really at a loss as to what the cause could be.  My only thought is
>> to try to reinstall 7.6.2 (maybe some old config or cached JAR is causing
>> issues?), or you could try out a 100% vanilla installation (of 7.6.2) on
>> your local machine just to verify for yourself whether that works or not.
>>  My suspicion is that is likely either a configuration issue, a conflicting
>> JAR or a customization causing issues.
>>
>> Possibly the only way to determine if that suspicion is correct is to try
>> out a completely vanilla installation (with no existing data) and see if it
>> works.  If that works, you could then trying your local codebase (again
>> with no existing data) to see if that works.  If it doesn't, it's something
>> in your local codebase or configs (and you may want to diff them with
>> defaults to see what's different).  If it still does work, then maybe
>> there's some sort of issue at the data level (I think that's less likely
>> here, but I could be wrong).
>>
>> Tim
>> On Tuesday, July 16, 2024 at 2:09:42 PM UTC-5 tant...@umn.edu wrote:
>>
>>> I haven't dug into the code any deeper, but I have discovered that if I
>>> enable
>>>   org.dspace.identifier.VersionedHandleIdentifierProvider
>>> instead of
>>>
>>> org.dspace.identifier.VersionedHandleIdentifierProviderWithCanonicalHandles
>>> in dspace/config/spring/api/identifier-service.xml
>>>
>>> The metadata is created and added to the metadatavalue table as expected.
>>>
>>> Is this the intended behavior?  Off the top of my head, I would think
>>> that since versioning only applies to items, these classes should treat
>>> communities and collections the same regardless of which one is enabled.
>>> ~~Bill
>>>
>>> On Mon, Jul 15, 2024 at 4:41 PM DSpace Technical Support <
>>> dspac...@googlegroups.com> wrote:
>>>
 Hi Bill,

 I just tried this out on a DSpace 7.6.2 instance locally that I started
 using the Docker scripts (documented at
 https://wiki.lyrasis.org/display/DSPACE/Try+out+DSpace+7)

 I had no issues creating a new Community and Collection and both
 received a new "dc.identifier.uri" which is displayed on the Community /
 Collection Homepage next to the text saying "Permanent URI for this
 [community]/[collection]".   So, I don't believe this is a bug in
 out-of-the-box DSpace 7.6.2.   (That said, if others can confirm this same
 behavior, then we can dig further to see if there are specific scenarios
 where this might be happening)

 It's very odd to me that you'd see no errors when following the
 Troubleshooting Guide steps
 https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove).
 You could verify that no errors appear in any of the tabs in your Browser's
 DevTools

Re: [dspace-tech] Re: dc.identifier.uri for new communities/collections

2024-07-16 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Just out of curiosity, did *you* try toggling
to org.dspace.identifier.VersionedHandleIdentifierProviderWithCanonicalHandles
on your server or did you just go with the default?  Or are there any other
installs out there that use this older, pre-version 6x strategy?
~~Bill

On Tue, Jul 16, 2024 at 4:17 PM DSpace Technical Support <
dspace-tech@googlegroups.com> wrote:

> Hi Bill,
>
> I don't understand how the versioning feature could impact this...as you
> said, it's not used by Communities & Collections.  It's also odd to me that
> this odd behavior would *only* impact Communities & Collections, as it
> should also impact Items if the versioning configuration was to blame.
> Something isn't adding up here.
>
> I can verify the I tested on my end with the default settings of
> "org.dspace.identifier.VersionedHandleIdentifierProvider" and everything is
> working.   The Demo Site also has this default setting in place and it's
> working fine as well: https://demo.dspace.org/  (Demo is running 8.0, but
> this area of the codebase shouldn't be significantly different between
> 7.6.2 and 8.0)
>
> I'm really at a loss as to what the cause could be.  My only thought is to
> try to reinstall 7.6.2 (maybe some old config or cached JAR is causing
> issues?), or you could try out a 100% vanilla installation (of 7.6.2) on
> your local machine just to verify for yourself whether that works or not.
>  My suspicion is that is likely either a configuration issue, a conflicting
> JAR or a customization causing issues.
>
> Possibly the only way to determine if that suspicion is correct is to try
> out a completely vanilla installation (with no existing data) and see if it
> works.  If that works, you could then trying your local codebase (again
> with no existing data) to see if that works.  If it doesn't, it's something
> in your local codebase or configs (and you may want to diff them with
> defaults to see what's different).  If it still does work, then maybe
> there's some sort of issue at the data level (I think that's less likely
> here, but I could be wrong).
>
> Tim
> On Tuesday, July 16, 2024 at 2:09:42 PM UTC-5 tant...@umn.edu wrote:
>
>> I haven't dug into the code any deeper, but I have discovered that if I
>> enable
>>   org.dspace.identifier.VersionedHandleIdentifierProvider
>> instead of
>>
>> org.dspace.identifier.VersionedHandleIdentifierProviderWithCanonicalHandles
>> in dspace/config/spring/api/identifier-service.xml
>>
>> The metadata is created and added to the metadatavalue table as expected.
>>
>> Is this the intended behavior?  Off the top of my head, I would think
>> that since versioning only applies to items, these classes should treat
>> communities and collections the same regardless of which one is enabled.
>> ~~Bill
>>
>> On Mon, Jul 15, 2024 at 4:41 PM DSpace Technical Support <
>> dspac...@googlegroups.com> wrote:
>>
>>> Hi Bill,
>>>
>>> I just tried this out on a DSpace 7.6.2 instance locally that I started
>>> using the Docker scripts (documented at
>>> https://wiki.lyrasis.org/display/DSPACE/Try+out+DSpace+7)
>>>
>>> I had no issues creating a new Community and Collection and both
>>> received a new "dc.identifier.uri" which is displayed on the Community /
>>> Collection Homepage next to the text saying "Permanent URI for this
>>> [community]/[collection]".   So, I don't believe this is a bug in
>>> out-of-the-box DSpace 7.6.2.   (That said, if others can confirm this same
>>> behavior, then we can dig further to see if there are specific scenarios
>>> where this might be happening)
>>>
>>> It's very odd to me that you'd see no errors when following the
>>> Troubleshooting Guide steps
>>> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove).
>>> You could verify that no errors appear in any of the tabs in your Browser's
>>> DevTools (especially also the "Network" tab).
>>>
>>> Hopefully, if someone else runs into this they will mention it here as
>>> well.
>>>
>>> Tim
>>>
>>> On Thursday, July 11, 2024 at 9:57:41 AM UTC-5 tant...@umn.edu wrote:
>>>
 In DSpace 7.6.2, newly created collections and communities are not
 being assigned a persistent identifier (dc.identifier.uri) in the
 metadatavalue table.  I have handle.canonical.prefix and handle.prefix set
 in dspace.cfg, and the correct metadata *is* generated for new items.
 There are no errors in any of the log files (apache, tomcat, dspace), nor
 in the javascript console.  Setting the log level to DEBUG exposes other 
 "org.hibernate.SQL
 @ insert into public.metadatavalue()" statements for community title, text,
 news, etc, but nothing for dc.identifier.uri

 As I said, this metadata is generated for all new items.

 Is anybody else seeing this issue or is this behavior configurable and
 'off' by default or do I have some other isolated problem?
 Regards,
 Bill

>>> --
>>> All messages to this mailing list should adhere

Re: [dspace-tech] Re: dc.identifier.uri for new communities/collections

2024-07-16 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
I haven't dug into the code any deeper, but I have discovered that if I
enable
  org.dspace.identifier.VersionedHandleIdentifierProvider
instead of

org.dspace.identifier.VersionedHandleIdentifierProviderWithCanonicalHandles
in dspace/config/spring/api/identifier-service.xml

The metadata is created and added to the metadatavalue table as expected.

Is this the intended behavior?  Off the top of my head, I would think that
since versioning only applies to items, these classes should treat
communities and collections the same regardless of which one is enabled.
~~Bill

On Mon, Jul 15, 2024 at 4:41 PM DSpace Technical Support <
dspace-tech@googlegroups.com> wrote:

> Hi Bill,
>
> I just tried this out on a DSpace 7.6.2 instance locally that I started
> using the Docker scripts (documented at
> https://wiki.lyrasis.org/display/DSPACE/Try+out+DSpace+7)
>
> I had no issues creating a new Community and Collection and both received
> a new "dc.identifier.uri" which is displayed on the Community / Collection
> Homepage next to the text saying "Permanent URI for this
> [community]/[collection]".   So, I don't believe this is a bug in
> out-of-the-box DSpace 7.6.2.   (That said, if others can confirm this same
> behavior, then we can dig further to see if there are specific scenarios
> where this might be happening)
>
> It's very odd to me that you'd see no errors when following the
> Troubleshooting Guide steps
> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove).
> You could verify that no errors appear in any of the tabs in your Browser's
> DevTools (especially also the "Network" tab).
>
> Hopefully, if someone else runs into this they will mention it here as
> well.
>
> Tim
>
> On Thursday, July 11, 2024 at 9:57:41 AM UTC-5 tant...@umn.edu wrote:
>
>> In DSpace 7.6.2, newly created collections and communities are not being
>> assigned a persistent identifier (dc.identifier.uri) in the metadatavalue
>> table.  I have handle.canonical.prefix and handle.prefix set in dspace.cfg,
>> and the correct metadata *is* generated for new items.  There are no
>> errors in any of the log files (apache, tomcat, dspace), nor in the
>> javascript console.  Setting the log level to DEBUG exposes other 
>> "org.hibernate.SQL
>> @ insert into public.metadatavalue()" statements for community title, text,
>> news, etc, but nothing for dc.identifier.uri
>>
>> As I said, this metadata is generated for all new items.
>>
>> Is anybody else seeing this issue or is this behavior configurable and
>> 'off' by default or do I have some other isolated problem?
>> Regards,
>> Bill
>>
> --
> 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 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/74514521-fac0-4e5a-a0d4-d6461c4236a8n%40googlegroups.com
> 
> .
>


-- 
__
Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)  612-325-1777 (mobile)

-- 
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 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/CADgrb7HGerDBdrRhWxMCj3bj5OHrxQXWkHNF9czmMRpKZsF9ug%40mail.gmail.com.


Re: [dspace-tech] Re: Community/Collection logos not assigned a format.

2024-07-16 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
The browser console reports a 400 error when attempting to retrieve the
logo.  The dspace log issues a warning,

Invalid mime type "Unknown": does not contain '/' at:
org.springframework.http.MediaType.parseMediaType(MediaType.java:634))

because for some reason, the logo is assigned a bitstream_format_id = 1
(Unknown) in the bitstream table.  As I mentioned, this is the same sample
image I have used for new items, so it *should* work.

The frontend and backend are as 'plain vanilla' as they can be.  My apache
setup is identical to the one in the documentation, but I have to wonder if
there is a httpd configuration problem?
~~Bill

On Mon, Jul 15, 2024 at 4:46 PM DSpace Technical Support <
dspace-tech@googlegroups.com> wrote:

> Hi Bill,
>
> Similar to your other posting, I tried this out in vanilla DSpace 7.6.2
> using the Docker setup described at
> https://wiki.lyrasis.org/display/DSPACE/Try+out+DSpace+7.   I was able to
> upload logos into both a Community and a Collection, and had no issues
> viewing them.
>
> The fact that your issues are specific to Communities & Collections makes
> me wonder if you've somehow customized the Community & Collection forms?
> If so, my guess would be that you may have customizations that are no
> longer valid/working for DSpace 7.6.2 (and you may want to revert them, see
> if that fixes the bugs, and try them again).
>
> As always, I think the best step is to try to follow the Troubleshooting
> Guide to look for errors as well (though I'm guessing you may have already
> tried that based on your other email):
> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>
> Hopefully if someone else hits this issue, they will also report it.  But,
> right now, I cannot find a way to reproduce this in 7.6.2, so I suspect
> it's something on your end (either custom code, or some issue in your
> upgrade process).
>
> Tim
>
> On Thursday, July 11, 2024 at 11:28:42 AM UTC-5 tant...@umn.edu wrote:
>
>> In DSpace 7.6.2, site admins can successfully upload a community or a
>> collection logo.  However, the bitstream is assigned a bitstream format =
>> 1, unknown, and thus cannot be viewed.  I have tested this behavior with a
>> number of bitstreams with the same result.  I have tested with
>> known-to-work bitstreams (that is, existing community/collection logos).
>> Also, these same bitstreams can be be uploaded to items, and the format
>> will be recognized and assigned correctly.
>>
>> There are no errors or warnings in any logs; all the data in the
>> bitstream table is accurate, except for the bitstream_format_id.
>>
>> My workaround is to UPDATE the bitstream table with the correct format.
>> Is anybody else experiencing problems with this?
>> Regards,
>> ~~Bill
>>
> --
> 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 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/1b7fa2b1-1a86-4e45-bed7-0bab80cd290an%40googlegroups.com
> 
> .
>


-- 
__
Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)  612-325-1777 (mobile)

-- 
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 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/CADgrb7HkEtX2fimcdJ22QPw79P%2BUzwjRp1Zn92LjAhd3UQn9DQ%40mail.gmail.com.


Re: [dspace-tech] Re: disable browse subject tree

2024-03-27 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
I discovered this setting in config.yml, and documented here:
https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Configuration

  - filter: 'subject'
vocabulary: 'srsc'
enabled: false

Setting this to false in tandem with the setting in dspace.cfg noted above
will get rid of any 'browse by subject tree'  options.

On Wed, Mar 27, 2024 at 12:58 PM Emilia Lobo  wrote:

> Hello!
>
> I want to try to do the same or replace that search so that I can perform
> it by document type for example.
>
> What files should I modify?
> Are the changes made from DSpace and from dspace-angular?
> Thanks.
>
> El viernes, 15 de marzo de 2024 a las 17:26:49 UTC-3, tant...@umn.edu
> escribió:
>
>> In DSpace 7.6.1, we do not user Hierarchical Browse Indexes.  In
>> dspace.cfg, I have
>>
>> webui.browse.vocabularies.disabled = srsc
>>
>> so that "By Subject Category" is not an option in the global browse
>> menu.  However, when expanding the Subject filter in discovery, there is
>> still a link to "Browse subject tree"
>>
>> Can I / How do I disable this?
>> Regards,
>> Bill
>>
> --
> 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 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/ab1cdfa5-182b-4d73-b6e1-f6c480767b72n%40googlegroups.com
> 
> .
>


-- 
__
Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)  612-325-1777 (mobile)

-- 
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 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/CADgrb7Gp0R%3D%2BBD9t%2Bs_%2By%3Df4qVHYPS89qzj6K21qQ4G7bXBF8g%40mail.gmail.com.


[dspace-tech] submission status icon is never green

2023-10-13 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
dspace 7.6 backend/frontend

In my submission form, in the first describe section, the status icon is
initially the yellow '!' warning.  It never becomes the green checkmark
even if all metadata is entered correctly.

Initially, I thought the problem might be related to:
  https://github.com/DSpace/DSpace/issues/8969
so I removed all lists from my form, but the problem persists.  I even
removed all required fields from the section, but the icon stays yellow.

The item can be submitted successfully, but the warning icon remains.  On
the demo site I see the same behavior...

Any ideas on what I may be doing wrong?  Other than the one I noted, I
don't see any other issues on Github.

Regards,
~~Bill

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7F_MShEGuH3XrhD9_Hug6LAkRv_iDN108DQHn9NE_N6-A%40mail.gmail.com.


Re: [dspace-tech] Re: Possible to configure maximum embargo length?

2023-06-06 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
That's it!  Perfect, thank you.
~~Bill

On Tue, Jun 6, 2023 at 10:50 AM Mohammad S. AlMutairi 
wrote:

> Check line no. 38 in [dspace]/config/spring/api/access-conditions.xml
>
> On Tuesday, June 6, 2023 at 6:18:15 PM UTC+3 tant...@umn.edu wrote:
>
>> I would like to resurrect this question from a couple years ago.
>>
>> Is there a way to do this in DSpace 7.5?  We would like to enforce a
>> policy such that embargoes can be set for no more than two years.
>> Thanks,
>> ~~Bill
>>
>> On Tuesday, March 23, 2021 at 10:15:52 AM UTC-5 Gail Steinhart wrote:
>>
>>> Greetings,
>>>
>>>
>>> We are considering implementing embargoes in the user submission
>>> interface (simple, UploadWithEmbargoStep). I am wondering if it is possible
>>> to configure a maximum embargo length, say two years from current date? We
>>> don’t want submitters setting 100 year embargoes. I don’t see anything in
>>> the documentation that tells me this is possible, but wanted to check.
>>>
>>>
>>>
>>> Thank you,
>>>
>>> Gail
>>>
>>>
>>>
>>> Gail Steinhart
>>>
>>> Open Scholarship Services Librarian
>>>
>>> Cornell University Library Information Technology
>>>
>>> 218 Olin Library | 607.255.7251 <(607)%20255-7251>
>>>
>>> *https://orcid.org/-0002-2441-1651
>>> * | @gailst
>>> 
>>>
>>> she/her
>>>
>> --
> 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 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/f96a67f0-fdd1-4a29-8a2a-8e80b2298965n%40googlegroups.com
> 
> .
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7GmAHkc7n0ED%2BOe_PSiKdnhgHfZPW3kja5TLOrjzX%2B_QA%40mail.gmail.com.


Re: [dspace-tech] Differences in search result on items between DSpace 6.3 an DSpace 7.5

2023-03-02 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
There is a companion setting in discovery.cfg which limits the number of
characters that are actually stored in the solr index; initially, that is
also set to 10 characters.  Simply set this to a higher count, or -1
for unlimited.

Hope that helps!
~~Bill

On Thu, Mar 2, 2023 at 7:52 AM Erivelto Henrique 
wrote:

> Hello everyone!
>
> I have a DSpace 6.3 installation and am deploying a new document
> repository with version 7.5
>
> We have already installed the new version 7.5 on a new server, and we have
> imported some documents for this new installation.
> We did some search tests and noticed a very big difference in search
> results between the two versions.
> When I search for a term in version 6.3, I get 14 results found for the
> search, and when I search in version 7.5, I only get 9 returns.
> Version 6.3 search result
> [image: Screenshot_8.png]
> Version 7.5 search result
> [image: Screenshot_10.png]
>
> With some PDF documents that are very large and the Text Extractor
> settings were set to 100k characters, the file was not converting 100% to
> TXT. I changed it to textextractor.max-chars = -1, all documento is
> converted, but still the search result remains the same.
>
> Anyone can help me with this?
>
> Thanks
>
> Erivelto Alves
>
> --
> 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 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/2c07da78-ff39-4ba5-acf0-27f0144841cen%40googlegroups.com
> 
> .
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7FwqxKMJ_9QP-v0xA%2BUwBamTvvrUsMqC-ggEHArBYi%3D%2Bg%40mail.gmail.com.


[dspace-tech] DSpace 7 with apache tomcat 10

2023-02-17 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Just wondering if anybody is using apache tomcat 10x with their DSpace 7x
installation.  Any problems?
Thanks,
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7G2DSqJ%3Dt6Dw6kpve5LDNtBjX77_2hDB9VG0_rX2aMkdA%40mail.gmail.com.


[dspace-tech] Tika temp directory

2023-01-30 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
All,
Is the temp directory used by the tika text extractor configurable?  By
default it uses /tmp, but I would like to set it to somewhere that I
control, and that has more available space.
Thanks for any advice!
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7ER1d%3DaYZLbu_RnNyQdSn9FvZGpCPbUbesAQ11Dv9EhgA%40mail.gmail.com.


[dspace-tech] Error on login

2022-11-15 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
DSpace v7.3

In my DSpace log, I noticed the following error on login (in my case
Shibboleth, although I'm not sure it's related...). This is
seemingly harmless(?). That is, an eperson gets logged in and proceeds
normally, but the error is bothersome.

Indeed, the metadata field mentioned (dspace:object.owner) in the error
does not exist in my database.  A full stacktrace can be included if
anybody thinks it would be helpful.  Did something go wrong with the
database migration?

2022-11-15 09:58:03,037 ERROR unknown unknown
org.dspace.app.rest.security.EPersonRestAuthenticationProvider @ An error
occurs performing post logged in action
java.lang.IllegalArgumentException: No such metadata field: schema=dspace,
element=object, qualifier=owner
at
org.dspace.content.ItemServiceImpl.findByAuthorityValue(ItemServiceImpl.java:1355)
~[dspace-api-7.4.jar:7.4]
at
org.dspace.profile.ResearcherProfileServiceImpl.findResearcherProfileItemById(ResearcherProfileServiceImpl.java:251)
~[dspace-api-7.4.jar:7.4]
at
org.dspace.profile.ResearcherProfileServiceImpl.findById(ResearcherProfileServiceImpl.java:114)
~[dspace-api-7.4.jar:7.4]
at
org.dspace.app.rest.login.impl.ResearcherProfileAutomaticClaim.currentUserHasAlreadyResearcherProfile(ResearcherProfileAutomaticClaim.java:112)
~[classes/:7.4]
at
org.dspace.app.rest.login.impl.ResearcherProfileAutomaticClaim.claimProfile(ResearcherProfileAutomaticClaim.java:99)
~[classes/:7.4]
at
org.dspace.app.rest.login.impl.ResearcherProfileAutomaticClaim.loggedIn(ResearcherProfileAutomaticClaim.java:87)
~[classes/:7.4]
at
org.dspace.app.rest.security.EPersonRestAuthenticationProvider.authenticateNewLogin(EPersonRestAuthenticationProvider.java:140)
[classes/:7.4]
at
org.dspace.app.rest.security.EPersonRestAuthenticationProvider.authenticate(EPersonRestAuthenticationProvider.java:88)
[classes/:7.4]

etc, etc, etc

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7Gfpf%3DonRSMDqUtvRYNHSJC-0_aQt-mkM4aX54zS7KwzA%40mail.gmail.com.


[dspace-tech] Re: 'submitted by' in dc.provenance

2022-11-11 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
A little further info here -- I should add that the items are being
submitted to collections without a workflow.  This seems to be where
'Submitted by' is added to the provenance text (based on the firstStep
variable).  Do items need to go through a workflow to have this text
added?  Possibly related to https://github.com/DSpace/DSpace/issues/7667 ?
~~Bill

On Thu, Nov 10, 2022 at 2:58 PM Bill Tantzen  wrote:

> In DSpace 7.4, newly submitted items do not contain a 'Submitted by' field
> in dc.provenance.  Is there a way to configure what gets placed in
> provenance metadata?
>
> Thanks!
> ~~Bill
>
> --
> Human wheels spin round and round
> While the clock keeps the pace... -- John Mellencamp
> 
> Bill TantzenUniversity of Minnesota Libraries
> 612-626-9949 (U of M)612-325-1777 (cell)
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7G6mbxLBvjAu8PpDFjTPHBtN2HsVOrR9utymm5v_b8gLA%40mail.gmail.com.


[dspace-tech] 'submitted by' in dc.provenance

2022-11-10 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
In DSpace 7.4, newly submitted items do not contain a 'Submitted by' field
in dc.provenance.  Is there a way to configure what gets placed in
provenance metadata?

Thanks!
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7E3C26H%3DdC3MgLtaomZpvEWuN7TRhNBws7FpRPw9DE%2BQA%40mail.gmail.com.


[dspace-tech] Results per Page choices

2022-11-09 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
In DSpace 7, is it possible to adjust the choices and default values in the
"Results Per Page" dropdown on Community pages, Browse by pages, etc?

A link to the documentation would be perfect!
Thanks,
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7EzvZMD-vf_6nxp4jOtPj4ragaFHfCn%3Dg_%2BB0nNZuc%2BnQ%40mail.gmail.com.


[dspace-tech] scope search by community

2022-11-07 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
In DSpace 7.4, is it possible to search within a community/collection from
that community/collection page?  Or is the only option to go to /search
page and scope by community/collection there?

That's how it appears to me, but I want to make sure there is not a
configuration that I am overlooking.
Thanks!

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7G7uHpERW7LC3qp4-ExKfFb%3DG-3EujDxCz6RcimJ-8rOw%40mail.gmail.com.


[dspace-tech] item access conditions step configuration

2022-10-28 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
In DSpace 7.4, I would like to NOT display the Access Conditions step on my
"Edit bitstream" form.  It is not enabled in my 
definition, nor anywhere else in item-submission.xml (according to the
documentation, it is disabled by default).  However, I still see dropdowns
for

Access condition type
Grant access from
Grant access until

on my form.  Is there a way to suppress this?
Thanks,
~~Bill
-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7FG5YNgDbwg6UtwH%2Behqo0AqcxzzPsYm%3Dwrm8Lzu012rg%40mail.gmail.com.


[dspace-tech] UntypedItemComponent in version 7.4

2022-10-11 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
I was super excited to see the UntypedItemComponent among the themeable
components in the custom theme of the newly released version 7.4. However,
it does not appear to work (it does not override the component in the app
directory).

Other components in my theme are displaying properly, so my theme itself
seems to be working.

I have changed the TemplateUrl in the .ts file from
// templateUrl:
'../../../../../../../app/item-page/simple/item-types/untyped-item/untyped-item.component.html'
to
  templateUrl: './untyped-item.component.html'

but my component is not being used.

Has anybody else experimented with this component and verified that it
works?  Is there another step that I'm missing?

Thanks in advance!
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7HsyYDhwLpStoxCU0nFCcCyi%2BK1oAxwL9K%2Bpx1WOXpp6w%40mail.gmail.com.


[dspace-tech] submission metadata default values

2022-09-15 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
In DSpace 7.3 item submission, is it possible to set a default value for a
metadata field and remove it from the input form?  For instance, for a
Thesis collection, I would like to remove the Type field from the input
form, but set dc.type = "thesis" for all items submitted to this collection.

I know how to remove the field from the form, but I'm not sure how to set a
default value...
Thanks for any advice or pointers to documentation!
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7FGqr2jo9Pshy69vX%3D4wPVLkiAV_Rks%2BJ9B_MZ_ioi3VA%40mail.gmail.com.


[dspace-tech] Sort by dc.date.available

2022-08-24 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
In DSpace 7.3, I am attempting to add a sort option to the
workspaceConfiguration (to sort recent submissions) based on
dc.date.available

I have added and referenced a SortFieldConfiguration bean:






After rebuilding the search index, the sort does not work.

A look at the solr logs reveals the parameter: sort=dc.date.available_sort,
but there is no such field in the index.  I tried setting the type to
"text", but again this fails, and the solr log now shows the query
parameter is sort=dc.date.available_sort.  Same thing, there is no such
field in the index.

Not sure if this has anything to do with it, but I have a couple thousand
items with multiple dc.date.available metadatavalues (not sure how this
happens), and the dynamic fields *_dt and *_sort are NOT defined as
multivalued.

Is there a step I am missing, or are the multiple metadatavalues the
problem?

Thanks,
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7GWW3RmH5fVcVD8dL64nqU9MO2fv8Rzgd7RpCTcfYO6HA%40mail.gmail.com.


Re: [dspace-tech] Re: DSpace 7.3, multiple custom themes

2022-08-24 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Right, that much worked for me as well (with your help initially) -- adding
a second one seems to be the problem...  Only one of the
UntypedItemComponents is leveraged, regardless of the selected theme.
Which seems weird to me:  the correct ItemPageComponent is in use, but an
UntypedItemComponent from a different theme and directory is leveraged.

I will continue to experiment.
~~Bill

On Wed, Aug 24, 2022 at 8:19 AM Mark H. Wood  wrote:

> On Wed, Aug 24, 2022 at 07:38:22AM -0500, 'Bill Tantzen' via DSpace
> Technical Support wrote:
> > Thanks Mark!
> > So, just to be clear, you have two distinct themes with two different
> > UntypedItemComponents (I was able to implement and override one in my
> > default theme, it's the second one in a different theme that fails...)?
> I
> > just wanted to make sure I am not going down a dead end street!
>
> Not yet, but I do have one custom theme with its own
> UntypedItemComponent and I do get that one, not the stock one.
>
> > I thought I did give it the listableObjectComponent special treatment,
> but
> > I will check again...  I no doubt missed something if you were
> successful.
> > ~~Bill
> >
> > On Wed, Aug 24, 2022 at 6:34 AM Mark H. Wood 
> wrote:
> >
> > > On Tue, Aug 23, 2022 at 02:42:03PM -0500, 'Bill Tantzen' via DSpace
> > > Technical Support wrote:
> > > > OK, here is some further info:  The correct ItemPageComponent is
> being
> > > > selected correctly, but the UntypedItemComponent is the piece that is
> > > > incorrect.
> > > >
> > > > UntypedItemComponent is NOT in the custom theme directory, so maybe
> it is
> > > > not themeable?
> > > >
> > > > Has anybody fooled around with this?  My goal is to have differently
> > > themed
> > > > item pages depending on a per-collection or per-community basis...
> > > > Specifically, different metadata, and it looks like
> UntypedItemComponent
> > > is
> > > > where this magic happens.
> > >
> > > I ran into this as well.  One thing that is special is that
> > > UntypedItemComponent is decorated '@listableObjectComponent' so it is
> > > made theme-able in a different way.  Look for 'listableObject' in
> > > https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Customization
> > > for more information.
> > >
> > > I wish I could just tell you what worked, but I spent days floundering
> > > around in the code and the memories are blurred.
> > >
> > > > On Tue, Aug 23, 2022 at 12:07 PM Bill Tantzen 
> wrote:
> > > >
> > > > > I'm experimenting with creating custom themes for a couple of
> > > communities
> > > > > and collections.  I have a default theme with all the components in
> > > > > 'custom', along with a theme for a specific community, and one for
> a
> > > > > specific collection.  My theme config is like so:
> > > > >
> > > > > themes:
> > > > >   - name: 'community_a'
> > > > > extends: 'default'
> > > > > handle: 'x/183663'
> > > > >
> > > > >   - name: 'collection_a'
> > > > > extends: 'default'
> > > > > handle: 'x/166578'
> > > > >
> > > > >   - name: 'default'
> > > > >
> > > > > In my 'community_a' theme, I have a community-page component
> > > > > In my 'collection_a' theme, I have a collection-page component and
> an
> > > > > item-page component.  The default theme has all themeable
> components.
> > > > >
> > > > > The problem I am having is that regardless of which community or
> > > > > collection to which an item belongs, it is themed by the item-page
> > > > > component in the 'collection_a' theme (the first one it
> encounters).
> > > > >
> > > > > My understanding was that items in collection_a are themed by the
> > > > > component I override there, and that the default theme takes care
> of
> > > > > everything else.
> > > > >
> > > > > Am I misunderstanding something, have I misconfigured something,
> or is
> > > > > this a bug?  Anybody else out there experimenting with multiple
> themes?
> > > > >
> > > > > Thanks 

Re: [dspace-tech] Re: DSpace 7.3, multiple custom themes

2022-08-24 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Thanks Mark!
So, just to be clear, you have two distinct themes with two different
UntypedItemComponents (I was able to implement and override one in my
default theme, it's the second one in a different theme that fails...)?  I
just wanted to make sure I am not going down a dead end street!

I thought I did give it the listableObjectComponent special treatment, but
I will check again...  I no doubt missed something if you were successful.
~~Bill

On Wed, Aug 24, 2022 at 6:34 AM Mark H. Wood  wrote:

> On Tue, Aug 23, 2022 at 02:42:03PM -0500, 'Bill Tantzen' via DSpace
> Technical Support wrote:
> > OK, here is some further info:  The correct ItemPageComponent is being
> > selected correctly, but the UntypedItemComponent is the piece that is
> > incorrect.
> >
> > UntypedItemComponent is NOT in the custom theme directory, so maybe it is
> > not themeable?
> >
> > Has anybody fooled around with this?  My goal is to have differently
> themed
> > item pages depending on a per-collection or per-community basis...
> > Specifically, different metadata, and it looks like UntypedItemComponent
> is
> > where this magic happens.
>
> I ran into this as well.  One thing that is special is that
> UntypedItemComponent is decorated '@listableObjectComponent' so it is
> made theme-able in a different way.  Look for 'listableObject' in
> https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Customization
> for more information.
>
> I wish I could just tell you what worked, but I spent days floundering
> around in the code and the memories are blurred.
>
> > On Tue, Aug 23, 2022 at 12:07 PM Bill Tantzen  wrote:
> >
> > > I'm experimenting with creating custom themes for a couple of
> communities
> > > and collections.  I have a default theme with all the components in
> > > 'custom', along with a theme for a specific community, and one for a
> > > specific collection.  My theme config is like so:
> > >
> > > themes:
> > >   - name: 'community_a'
> > > extends: 'default'
> > > handle: 'x/183663'
> > >
> > >   - name: 'collection_a'
> > > extends: 'default'
> > > handle: 'x/166578'
> > >
> > >   - name: 'default'
> > >
> > > In my 'community_a' theme, I have a community-page component
> > > In my 'collection_a' theme, I have a collection-page component and an
> > > item-page component.  The default theme has all themeable components.
> > >
> > > The problem I am having is that regardless of which community or
> > > collection to which an item belongs, it is themed by the item-page
> > > component in the 'collection_a' theme (the first one it encounters).
> > >
> > > My understanding was that items in collection_a are themed by the
> > > component I override there, and that the default theme takes care of
> > > everything else.
> > >
> > > Am I misunderstanding something, have I misconfigured something, or is
> > > this a bug?  Anybody else out there experimenting with multiple themes?
> > >
> > > Thanks for any advice!
> > > ~~Bill
> > > --
> > > Human wheels spin round and round
> > > While the clock keeps the pace... -- John Mellencamp
> > > 
> > > Bill TantzenUniversity of Minnesota Libraries
> > > 612-626-9949 (U of M)612-325-1777 (cell)
> > >
> >
> >
> > --
> > Human wheels spin round and round
> > While the clock keeps the pace... -- John Mellencamp
> > 
> > Bill TantzenUniversity of Minnesota Libraries
> > 612-626-9949 (U of M)612-325-1777 (cell)
> >
> > --
> > 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 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/CADgrb7FjrmSz%3DjnzficmzXJUVMkkYSJ0kZP2HDFj06MZR258HQ%40mail.gmail.com
> .
>
> --
> Mark H. Wood
> Lead Technology Analyst
>
>

[dspace-tech] Re: DSpace 7.3, multiple custom themes

2022-08-23 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
OK, here is some further info:  The correct ItemPageComponent is being
selected correctly, but the UntypedItemComponent is the piece that is
incorrect.

UntypedItemComponent is NOT in the custom theme directory, so maybe it is
not themeable?

Has anybody fooled around with this?  My goal is to have differently themed
item pages depending on a per-collection or per-community basis...
Specifically, different metadata, and it looks like UntypedItemComponent is
where this magic happens.

Ideas?
~~Bill

On Tue, Aug 23, 2022 at 12:07 PM Bill Tantzen  wrote:

> I'm experimenting with creating custom themes for a couple of communities
> and collections.  I have a default theme with all the components in
> 'custom', along with a theme for a specific community, and one for a
> specific collection.  My theme config is like so:
>
> themes:
>   - name: 'community_a'
> extends: 'default'
> handle: 'x/183663'
>
>   - name: 'collection_a'
> extends: 'default'
> handle: 'x/166578'
>
>   - name: 'default'
>
> In my 'community_a' theme, I have a community-page component
> In my 'collection_a' theme, I have a collection-page component and an
> item-page component.  The default theme has all themeable components.
>
> The problem I am having is that regardless of which community or
> collection to which an item belongs, it is themed by the item-page
> component in the 'collection_a' theme (the first one it encounters).
>
> My understanding was that items in collection_a are themed by the
> component I override there, and that the default theme takes care of
> everything else.
>
> Am I misunderstanding something, have I misconfigured something, or is
> this a bug?  Anybody else out there experimenting with multiple themes?
>
> Thanks for any advice!
> ~~Bill
> --
> Human wheels spin round and round
> While the clock keeps the pace... -- John Mellencamp
> 
> Bill TantzenUniversity of Minnesota Libraries
> 612-626-9949 (U of M)612-325-1777 (cell)
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7FjrmSz%3DjnzficmzXJUVMkkYSJ0kZP2HDFj06MZR258HQ%40mail.gmail.com.


[dspace-tech] DSpace 7.3, multiple custom themes

2022-08-23 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
I'm experimenting with creating custom themes for a couple of communities
and collections.  I have a default theme with all the components in
'custom', along with a theme for a specific community, and one for a
specific collection.  My theme config is like so:

themes:
  - name: 'community_a'
extends: 'default'
handle: 'x/183663'

  - name: 'collection_a'
extends: 'default'
handle: 'x/166578'

  - name: 'default'

In my 'community_a' theme, I have a community-page component
In my 'collection_a' theme, I have a collection-page component and an
item-page component.  The default theme has all themeable components.

The problem I am having is that regardless of which community or collection
to which an item belongs, it is themed by the item-page component in the
'collection_a' theme (the first one it encounters).

My understanding was that items in collection_a are themed by the component
I override there, and that the default theme takes care of everything else.

Am I misunderstanding something, have I misconfigured something, or is this
a bug?  Anybody else out there experimenting with multiple themes?

Thanks for any advice!
~~Bill
-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7EY5sFtQKVcNjDcNZU1sr7goBSOVJBjqTOgtSG6LOCAVg%40mail.gmail.com.


[dspace-tech] solr statistics utilities

2022-08-19 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
All,

Can somebody explain the difference between:
  stats-util --export
and
  solr-export-statistics

and when and why I might choose one over the other?  I routinely use
solr-export-statistics to backup my solr stats, but stats-util --export
seems to do the same thing?
Thanks,
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7Gdyvd%3DpqZCGnxTi8FXBek0sY%2BBQn6BU6j-PH%3D2fbMMiw%40mail.gmail.com.


Re: [dspace-tech] Re: Edit bitstream page configuration

2022-08-19 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Nope, I still have only the two bundles I mentioned.  But 7.4 will be the
earliest we go public with 7.x, so I'm going to assume I'll be good then.
~~Bill

On Thu, Aug 18, 2022 at 4:07 PM 'Tim Donohue' via DSpace Technical Support <
dspace-tech@googlegroups.com> wrote:

> Hi Bill,
>
> Good find!  I completely forgot about that new configuration...and yes, it
> is what you are looking for.  It *was* added in 7.3 in this PR:
> https://github.com/DSpace/dspace-angular/pull/1605
>
> So, it *should* work in 7.3.  As you noted it works on the demo site.
>
> Tim
>
> On Thursday, August 18, 2022 at 12:39:22 PM UTC-5 tant...@umn.edu wrote:
>
>> I might add that on the demo site, the default bundles are indeed the
>> same as the array given by the standardBundles setting.  However, I note
>> that the version there is 7.4-SNAPSHOT, instead of the 7.3 that I am
>> using...  Maybe this is not fully implemented in 7.3
>> ~~Bill
>>
>> On Thursday, August 18, 2022 at 12:24:33 PM UTC-5 tant...@umn.edu wrote:
>>
>>> I just discovered this setting in config.yml:
>>>
>>> # The default bundles that should always be displayed as suggestions
>>> when you upload a new bundle
>>> bundle:
>>>   - standardBundles: [ ORIGINAL, THUMBNAIL, LICENSE ]
>>>
>>> which seemed really promising, but still, the default bundles in my
>>> dropdown are just ORIGINAL and LICENSE.  Does this setting not do what it
>>> implies, or is it a bug?
>>>
>>> On Wednesday, August 17, 2022 at 4:17:14 PM UTC-5 Tim Donohue wrote:
>>>
 Hi Bill,

 Once you create the Bundle in the Item, it will be prepopulated the
 next time you use that form.   By default that list of Bundle options is
 populated by the existing bundles...so, once a new bundle is created it
 will appear in that list.

 Tim

 On Wednesday, August 17, 2022 at 4:07:27 PM UTC-5 tant...@umn.edu
 wrote:

> Tim,
> Right, my users were hoping to have the dropdown populated with some
> common bundle names, but typing them in will work as a fallback.
> ~~Bill
>
> On Wed, Aug 17, 2022 at 4:01 PM 'Tim Donohue' via DSpace Technical
> Support  wrote:
>
>> Hi Bill,
>>
>> If you are on 7.3, on the Edit Item's "Bitstreams" tab, if you click
>> the "Upload" button, you'll see a screen that says "Select a bundle or
>> input new bundle name".  In that textbox, you can enter *any* new Bundle
>> name and click "Create Bundle".  So, it's not limited to the default 
>> bundle
>> types...you can enter any text there to create a new bundle.
>>
>>
>> On Thursday, August 11, 2022 at 10:34:04 AM UTC-5 tant...@umn.edu
>> wrote:
>>
>>> In DSpace 7, when adding a new bitstream to an existing item, I
>>> would like to populate the Bundle dropdown with a list of types, for
>>> instance, METADATA, THUMBNAIL, CC-LICENSE, TEXT, ORIGINAL, etc.  
>>> Currently,
>>> the dropdown appears to contain only the bundle types that exist in the
>>> item already (I think?).
>>>
>>> Can somebody point me to the documentation that describes how to
>>> configure this dropdown?
>>>
>>> Thanks!
>>> ~~Bill
>>>
>>> --
>>> Human wheels spin round and round
>>> While the clock keeps the pace... -- John Mellencamp
>>> 
>>> Bill TantzenUniversity of Minnesota Libraries
>>> 612-626-9949 <(612)%20626-9949> (U of M)612-325-1777
>>> <(612)%20325-1777> (cell)
>>>
>> --
>> 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 Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to dspace-tech...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/dspace-tech/d557e634-cd76-46f3-addb-2764c827967cn%40googlegroups.com
>> 
>> .
>>
>
>
> --
> Human wheels spin round and round
> While the clock keeps the pace... -- John Mellencamp
> 
> Bill TantzenUniversity of Minnesota Libraries
> 612-626-9949 <(612)%20626-9949> (U of M)612-325-1777
> <(612)%20325-1777> (cell)
>
 --
> 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 Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tec

Re: [dspace-tech] Re: Edit bitstream page configuration

2022-08-17 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Tim,
Right, my users were hoping to have the dropdown populated with some common
bundle names, but typing them in will work as a fallback.
~~Bill

On Wed, Aug 17, 2022 at 4:01 PM 'Tim Donohue' via DSpace Technical Support <
dspace-tech@googlegroups.com> wrote:

> Hi Bill,
>
> If you are on 7.3, on the Edit Item's "Bitstreams" tab, if you click the
> "Upload" button, you'll see a screen that says "Select a bundle or input
> new bundle name".  In that textbox, you can enter *any* new Bundle name and
> click "Create Bundle".  So, it's not limited to the default bundle
> types...you can enter any text there to create a new bundle.
>
>
> On Thursday, August 11, 2022 at 10:34:04 AM UTC-5 tant...@umn.edu wrote:
>
>> In DSpace 7, when adding a new bitstream to an existing item, I would
>> like to populate the Bundle dropdown with a list of types, for
>> instance, METADATA, THUMBNAIL, CC-LICENSE, TEXT, ORIGINAL, etc.  Currently,
>> the dropdown appears to contain only the bundle types that exist in the
>> item already (I think?).
>>
>> Can somebody point me to the documentation that describes how to
>> configure this dropdown?
>>
>> Thanks!
>> ~~Bill
>>
>> --
>> Human wheels spin round and round
>> While the clock keeps the pace... -- John Mellencamp
>> 
>> Bill TantzenUniversity of Minnesota Libraries
>> 612-626-9949 <(612)%20626-9949> (U of M)612-325-1777
>> <(612)%20325-1777> (cell)
>>
> --
> 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 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/d557e634-cd76-46f3-addb-2764c827967cn%40googlegroups.com
> 
> .
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7HurW2DTefpbPuuASxb%3DnZSTADv0CDcpymF2vOpu_kiQA%40mail.gmail.com.


Re: [dspace-tech] Re: Edit actions not contextualized based on admin rights

2022-08-17 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Thanks, I looked (but overlooked those).
~~Bill

On Wed, Aug 17, 2022 at 3:49 PM DSpace Technical Support <
dspace-tech@googlegroups.com> wrote:

> Hi Bill,
>
> These are known bugs which still exist in 7.3.  See these bug tickets:
>
> https://github.com/DSpace/dspace-angular/issues/1482
> https://github.com/DSpace/dspace-angular/issues/1331
>
> So, these are definitely usability bugs.  While the system does block you
> from editing anything you don't have rights to edit, it should ideally
> filter out those objects from these lists.
>
> Tim
>
> On Wednesday, August 10, 2022 at 3:36:11 PM UTC-5 tant...@umn.edu wrote:
>
>> In DSpace7, the actions that a logged in user may perform seem not be
>> contextualized according to the admin groups to which they belong, for
>> instance:
>>
>> When logged in as an eperson with any community admin capacity, that user
>> has the options Edit -> Community, Collection, or Items. The resulting
>> search option is not restricted to the community they have permissions for
>> and instead displays everything, so it appears that they have permission to
>> edit any community, collection, or item, only to receive a 403 permissions
>> error if they try to proceed.
>>
>> Similarly, an EPerson with community admin rights will see the option to
>> Create a New Item/Collection/Community/Process when logged in. The Create
>> New Collection/Community search will list all collections/communities
>> (including creating a new top-level community) and will let the EPerson
>> fill out the form for creating a new community/collection even if the
>> EPerson does not actually have permission to do so in the selected
>> community. It is not until the EPerson tries to save that new
>> community/collection that DSpace indicates that an access error has
>> occurred, and calls it a "server error" rather than a permissions error.
>>
>> Finally, users with no admin permissions see the option to Edit Item,
>> with the ability to choose seemingly any item. Selecting the item will then
>> show a 403 permissions error.
>>
>> Is this correct?  Or have I made an error in my dspace.cfg's
>> authorization system configuration? (This seems to be the behavior on the
>> demo site as well.  I would appear to be able to edit any item there, only
>> to be denied if I attempt to do so).
>>
>> Essentially I want to know if I have some mis-configuration, or if this
>> is the expected behavior.
>>
>> Thanks for any advice!
>> ~~Bill
>>
>> --
>> Human wheels spin round and round
>> While the clock keeps the pace... -- John Mellencamp
>> 
>> Bill TantzenUniversity of Minnesota Libraries
>> 612-626-9949 <(612)%20626-9949> (U of M)612-325-1777
>> <(612)%20325-1777> (cell)
>>
> --
> 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 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/064f50d2-98b5-47a9-b721-b525f054dc79n%40googlegroups.com
> 
> .
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7HnT7KN1Rk98m4b_CAQ45nAVLBkeO%3DqUiLsipJRWrLCtQ%40mail.gmail.com.


[dspace-tech] url-encoding in export

2022-08-17 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
In DSpace 5x (or 7x for that matter) when exporting to SAF:

  [dspace]/bin/dspace export --type=COLLECTION --id=collectionID_or_handle
--dest=/path/to/destination --number=seq_num
(see
https://wiki.lyrasis.org/display/DSDOC5x/Importing+and+Exporting+Items+via+Simple+Archive+Format#ImportingandExportingItemsviaSimpleArchiveFormat-OtherOptions
),

the exported dublin_core.xml files are all url(percent) encoded.  Is there
a way to turn this off, and export metadata in plain text?

Thanks for any insights here -- I've never used this export feature
before...
~~Bill
-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7E%3D7_ZaGFJPVyAG6xtfNAVD7FwsALkgDFcCC57-rmwqxQ%40mail.gmail.com.


[dspace-tech] dspace 7 bitstream display

2022-08-17 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
When viewing an item, the number of bitstreams that are displayed appears
to be limited to 5, along with a 'more' button.  Is this number
configurable, and if so, can somebody point me to the documentation on how
to change this?

Thanks,
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7FJk3aBNNHyihjSX5sdjwYdiq15%3DeO%2Bn9arNBL_O7EQRQ%40mail.gmail.com.


[dspace-tech] Edit bitstream page configuration

2022-08-11 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
In DSpace 7, when adding a new bitstream to an existing item, I would like
to populate the Bundle dropdown with a list of types, for
instance, METADATA, THUMBNAIL, CC-LICENSE, TEXT, ORIGINAL, etc.  Currently,
the dropdown appears to contain only the bundle types that exist in the
item already (I think?).

Can somebody point me to the documentation that describes how to configure
this dropdown?

Thanks!
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7EDMXEx1OLiLK8Q3_smPZv81MTMynmN5V_XKfz1Z-_08A%40mail.gmail.com.


[dspace-tech] Edit actions not contextualized based on admin rights

2022-08-10 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
In DSpace7, the actions that a logged in user may perform seem not be
contextualized according to the admin groups to which they belong, for
instance:

When logged in as an eperson with any community admin capacity, that user
has the options Edit -> Community, Collection, or Items. The resulting
search option is not restricted to the community they have permissions for
and instead displays everything, so it appears that they have permission to
edit any community, collection, or item, only to receive a 403 permissions
error if they try to proceed.

Similarly, an EPerson with community admin rights will see the option to
Create a New Item/Collection/Community/Process when logged in. The Create
New Collection/Community search will list all collections/communities
(including creating a new top-level community) and will let the EPerson
fill out the form for creating a new community/collection even if the
EPerson does not actually have permission to do so in the selected
community. It is not until the EPerson tries to save that new
community/collection that DSpace indicates that an access error has
occurred, and calls it a "server error" rather than a permissions error.

Finally, users with no admin permissions see the option to Edit Item, with
the ability to choose seemingly any item. Selecting the item will then show
a 403 permissions error.

Is this correct?  Or have I made an error in my dspace.cfg's authorization
system configuration? (This seems to be the behavior on the demo site as
well.  I would appear to be able to edit any item there, only to be denied
if I attempt to do so).

Essentially I want to know if I have some mis-configuration, or if this is
the expected behavior.

Thanks for any advice!
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7FAyai4xia8f1dFcD46nnSBehgLG%2BtXsk2nJqGqeq5%2BiA%40mail.gmail.com.


Re: [dspace-tech] dspace 7 default license

2022-08-10 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Right, and I really don't want markup in a txt file...

On Wed, Aug 10, 2022 at 7:08 AM Mark H. Wood  wrote:

> On Tue, Aug 09, 2022 at 02:20:02PM -0500, 'Bill Tantzen' via DSpace
> Technical Support wrote:
> > In DSpace 7.3, the displayed license text does not respect the line
> breaks
> > and extra whitespace in default.license (as it did in v5.10).
> >
> > Is this a theming issue?  Is there a way to reintroduce the line breaks
> for
> > readability?
>
> I sympathize.  We're going to have that same issue here.
>
> It's going to be a bit tricky, though.  To fit a variety of display
> widths, the text really should be filled.  To do this *and* permit
> arbitrary breaks, indents and the like requires some kind of embedded
> markup.
>
> And have we given sufficient thought to the accessibility of the
> license text?  If it's just a single ragged rectangle then this is
> fairly easy.  Structured text is more difficult.
>
> --
> 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 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 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/YvOfvD4WeWscFXH8%40IUPUI.Edu
> .
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7FUcEo93hr0EQ2VLekmNYpZUpgFgEPJcm9x%3D4Yp0D25WQ%40mail.gmail.com.


[dspace-tech] admin sidebar theming

2022-08-09 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
All,
Is the admin sidebar themeable (it's not in the custom theme...)?  At the
very least, I have been tasked with replacing the default logo with one
from our institution.

Thanks for any advice!
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7HbKJVh%3DN_YE5sQ3h5kL0oOE%2B0sCGtDen0evwkHoToPnw%40mail.gmail.com.


[dspace-tech] dspace 7 default license

2022-08-09 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
All,
In DSpace 7.3, the displayed license text does not respect the line breaks
and extra whitespace in default.license (as it did in v5.10).

Is this a theming issue?  Is there a way to reintroduce the line breaks for
readability?
Thanks for any advice!
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7HbRpwhjr4gs7DrexHqUqmCqm6jzZMQZSoERES681Fb3g%40mail.gmail.com.


Re: [dspace-tech] DSpace 7 item theming

2022-08-03 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Yes it does!  I was misled by the part of the docs that stated, if a
component is not in the custom theme, then it's not themeable.  Maybe this
works because it's a child of a themeable component?  You have to be
careful about adjusting the import paths in UntypedItemComponent, and to
import the component itself, but once you jump through a couple hoops, it
works.

I'm still not quite where I want to be -- it seems as if the smallest level
of refinement is , and I need a bit more than
that.  For instance, we have dc.identifier.issn, isbn, uri, and a couple
others.  I would like to group them together in the same pseudo "field" (as
I might do with field=dc.identifier.*) but still label them by type
individually.

There's a frustration level after getting pretty adept at doing these
things in xmlui, but with every new tech there's a learning curve!

Anyway, thanks for the tip!
~~Bill

On Wed, Aug 3, 2022 at 7:04 AM Mark H. Wood  wrote:

> On Tue, Aug 02, 2022 at 09:34:40AM -0500, 'Bill Tantzen' via DSpace
> Technical Support wrote:
> > Mark,
> > I'll give it a try -- my understanding was that only things from the
> custom
> > theme were themeable (and item-page/simple/item-types/untyped-item/ is
> not
> > in themes/custom/item-page).  But I'll find out!
>
> I should've said that I'm doing something similar with a custom
> untyped-item in a theme and it works.
>
> --
> 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 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 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/YupkR0oJ2YUjHTO0%40IUPUI.Edu
> .
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7Ftehs95ZseqA046g3rSDYGYf1yaB49F39nWKz_F%2BsCbw%40mail.gmail.com.


Re: [dspace-tech] DSpace 7 item theming

2022-08-02 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Mark,
I'll give it a try -- my understanding was that only things from the custom
theme were themeable (and item-page/simple/item-types/untyped-item/ is not
in themes/custom/item-page).  But I'll find out!
Thanks,
Bill

On Tue, Aug 2, 2022 at 7:50 AM Mark H. Wood  wrote:

> On Mon, Aug 01, 2022 at 12:43:46PM -0500, 'Bill Tantzen' via DSpace
> Technical Support wrote:
> > This seems like a pretty basic problem, but I have not been able to find
> a
> > solution.  If documentation exists, please point it out to me!
> >
> > I would like to add / remove / re-order the metadata on the simple item
> > view page for a custom theme.  I have discovered
> >
> src/app/item-page/simple/item-types/untyped-item/untyped-item.component.html
> > however I don't want to make global changes; I have a pair of custom
> > themes, and I would like different item views in the different themes.
> >
> > Is there a way to accomplish this?
>
> That is one of the theme-able components, so you can copy the whole
> component into your themes and reorganize the copies as needed.
>
> --
> 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 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 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/YukdmlN7wzL1%2BRH9%40IUPUI.Edu
> .
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7GA11YP-vCpO3%3DULoAY7dvpLrA6cK%2BdYcagk9oE686WEA%40mail.gmail.com.


[dspace-tech] DSpace 7 item theming

2022-08-01 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
This seems like a pretty basic problem, but I have not been able to find a
solution.  If documentation exists, please point it out to me!

I would like to add / remove / re-order the metadata on the simple item
view page for a custom theme.  I have discovered
src/app/item-page/simple/item-types/untyped-item/untyped-item.component.html
however I don't want to make global changes; I have a pair of custom
themes, and I would like different item views in the different themes.

Is there a way to accomplish this?

Thanks!
Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7GN15q%3DnHPkw4L9sburMoEixXotq4_LxQW3CRsMYEhqbQ%40mail.gmail.com.


Re: [dspace-tech] Error in frontend build

2022-06-27 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
It seems as if my gcc is out-of-date.  Unfortunately I am not able to
upgrade the compiler on this centrally managed server, so I will simply
have to hope for the best!
~~Bill

On Mon, Jun 27, 2022 at 2:00 PM Tim Donohue  wrote:

> Hi Bill,
>
> I've tried reproducing this on my end with 7.3 by running "yarn clean"
> (should remove everything from node_modules) and then a new "yarn
> install".  I cannot seem to reproduce this...a "yarn install" always
> succeeds for me with no errors.
>
> Maybe try that yourself (a yarn clean followed by a yarn install) and see
> if it happens again?  If so, we might need more details on your setup.  You
> also might want to check the messages just *above*​ the error
> message...just to see if there are any other hints as to what is going
> on...maybe a connection issue where something couldn't be downloaded?
>
> Overall, I'm not aware of this error. That said it is possible it is
> harmless (since everything else succeeds) as it's possible it's an optional
> dependency that is failing to install.
>
> Tim
> --
> *From:* 'Bill Tantzen' via DSpace Technical Support <
> dspace-tech@googlegroups.com>
> *Sent:* Monday, June 27, 2022 1:36 PM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Error in frontend build
>
> When installing the dspace 7.3 frontend, install throws an error.  This is
> seemingly harmless so far??  It does not prevent 'yarn build:prod' from
> completing normally, and the frontend appears to function normally, but I'm
> naturally suspicious of (and curious about) the error.  Anybody else
> encounter this?
>
> At the very end of 'yarn install' I get the following error:
>
> make: Entering directory
> `/usr/local/projects/current/dspace-7.3/node_modules/nice-napi/build'
>   CC(target) Release/obj.target/nothing/../node-addon-api/nothing.o
>   AR(target) Release/obj.target/../node-addon-api/nothing.a
>   COPY Release/nothing.a
>   CXX(target) Release/obj.target/nice_napi/binding.o
> g++: error: unrecognized command line option ‘-std=gnu++14’
> make: *** [Release/obj.target/nice_napi/binding.o] Error 1
> make: Leaving directory
> `/usr/local/projects/current/dspace-7.3/node_modules/nice-napi/build'
> gyp ERR! build error
> gyp ERR! stack Error: `make` failed with exit code: 2
> gyp ERR! stack at ChildProcess.onExit
> (/usr/local/node-v16.15.1-linux-x64/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
> gyp ERR! stack at ChildProcess.emit (node:events:527:28)
> gyp ERR! stack at Process.ChildProcess._handle.onexit
> (node:internal/child_process:291:12)
> gyp ERR! System Linux 3.10.0-1160.36.2.el7.x86_64
> gyp ERR! command \"/swadm/usr/local/node-v16.15.1-linux-x64/bin/node\"
> \"/swadm/usr/local/node-v16.15.1-linux-x64/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js\"
> \"rebuild\"
> gyp ERR! cwd /usr/local/projects/current/dspace-7.3/node_modules/nice-napi
> Done in 107.21s.
>
> A subsequent call to 'yarn install' completes normally -- without actually
> doing anything.
>
> Thanks for your ideas!
> ~~Bill
>
> --
> Human wheels spin round and round
> While the clock keeps the pace... -- John Mellencamp
> 
> Bill TantzenUniversity of Minnesota Libraries
> 612-626-9949 (U of M)612-325-1777 (cell)
>
> --
> 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 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/CADgrb7Guj53YiQTckmmh6exAg3p9AFJXpHWNtvr4yb2T4KW1Ag%40mail.gmail.com
> <https://groups.google.com/d/msgid/dspace-tech/CADgrb7Guj53YiQTckmmh6exAg3p9AFJXpHWNtvr4yb2T4KW1Ag%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7FT-UzKZYCW3L5SS9a68R2LWFjsQjY3OLf1cNWFDcDm3g%40mail.gmail.com.


[dspace-tech] Error in frontend build

2022-06-27 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
When installing the dspace 7.3 frontend, install throws an error.  This is
seemingly harmless so far??  It does not prevent 'yarn build:prod' from
completing normally, and the frontend appears to function normally, but I'm
naturally suspicious of (and curious about) the error.  Anybody else
encounter this?

At the very end of 'yarn install' I get the following error:

make: Entering directory
`/usr/local/projects/current/dspace-7.3/node_modules/nice-napi/build'
  CC(target) Release/obj.target/nothing/../node-addon-api/nothing.o
  AR(target) Release/obj.target/../node-addon-api/nothing.a
  COPY Release/nothing.a
  CXX(target) Release/obj.target/nice_napi/binding.o
g++: error: unrecognized command line option ‘-std=gnu++14’
make: *** [Release/obj.target/nice_napi/binding.o] Error 1
make: Leaving directory
`/usr/local/projects/current/dspace-7.3/node_modules/nice-napi/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit
(/usr/local/node-v16.15.1-linux-x64/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack at ChildProcess.emit (node:events:527:28)
gyp ERR! stack at Process.ChildProcess._handle.onexit
(node:internal/child_process:291:12)
gyp ERR! System Linux 3.10.0-1160.36.2.el7.x86_64
gyp ERR! command \"/swadm/usr/local/node-v16.15.1-linux-x64/bin/node\"
\"/swadm/usr/local/node-v16.15.1-linux-x64/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js\"
\"rebuild\"
gyp ERR! cwd /usr/local/projects/current/dspace-7.3/node_modules/nice-napi
Done in 107.21s.

A subsequent call to 'yarn install' completes normally -- without actually
doing anything.

Thanks for your ideas!
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7Guj53YiQTckmmh6exAg3p9AFJXpHWNtvr4yb2T4KW1Ag%40mail.gmail.com.


Re: [dspace-tech] DSpace 7 SSL - ui and backend on one domain name

2022-06-21 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Mark,
It looks as if your setup is similar to mine, but your apache directives
are a bit different from the ones suggested in the installation docs (
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace) for both the
frontend and the backend -- can you comment on your tweaks?
~~Bill

On Tue, Jun 21, 2022 at 9:47 AM Mark H. Wood  wrote:

> On Tue, Jun 21, 2022 at 06:43:40AM -0700, Karol Sokalski wrote:
> > I am in the process of installing DSpace 7 as a production. (Debian 11,
> > apache2, tomcat9)
> > I have a problem with SSL ( I have a trusted SSL certificate).
> > Unfortunately I cannot run the backend and frontend on the same domain
> > name.
> >
> > Everything works when I create 2 vhosts with two different domain names:
> > frontend.test.pl and backend.test.pl in apache and certificates for
> them.
> > But when I try to do everything in one vhost and one domain name  e.g.
> > dspace.test.pl, it won't work for me, because in apache vhost you can
> add
> > only one proxy-pass.e.g.
>
> That's incorrect.  You can have any number of reverse proxies.
>
> > ServerName dspace.test.pl
> >
> > ProxyRequests On
> > DSpace backend
> > ProxyPass /server http://localhost:8080/server
> > ProxyPassReverse /server http://localhost:8080/server
> > RequestHeader set X-Forwarded-Proto https
> >
> > DSpace FRONTEND
> > ProxyPass / http://localhost:4000/
> > ProxyPassReverse / http://localhost:4000/
>
> That should work, BUT "ProxyRequests On" is for a forward proxy and
> very likely should be "Off".
>
> Here's our local demo.  We're using AJP rather than HTTP to proxy the
> back-end, but in essence it's a lot like yours:
>
> # DSpace v7 demo back-end
> 
>   ProxyPass ajp://[::1]:8509/dspace-v7/
> 
>
> # DSpace v7 demo front-end
> 
>   SetEnvproxy-nokeepalive 1
>   SetEnvproxy-initial-not-pooled 1
> 
> ProxyPass   "/" "http://localhost:4000/"; disablereuse=On max=1
> ProxyPassReverse "/""http://localhost:4000/";
>
> How does your configuration "not work"?  What errors do you see?  What
> behavior?  Is there anything relevant in the backend log? the frontend
> log? the browser console?
>
> --
> 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 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 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/YrHaAcBEoRyxsiu2%40IUPUI.Edu
> .
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7Emp%3D-%3DCNG%3DuqSA%2B5hauUSMPLhCM-ppJWAKhut0-5YHwg%40mail.gmail.com.


Re: [dspace-tech] Solr error when initializing DSpace's search core

2022-06-15 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
near the top of search/conf/solrconfig.xml, try this (original config
commented out):








see if that helps!
~~Bill

On Wed, Jun 15, 2022 at 4:59 PM Thiago Cavalcanti 
wrote:

> Hello, Bill.
>
> Yes, that's the case. I'm running DSpace 7.2.1 and Solr 9.0.0.
>
> Thanks in advance,
> Thiago
> Em quarta-feira, 15 de junho de 2022 às 17:55:50 UTC-3, tant...@umn.edu
> escreveu:
>
>> Thiago,
>> What version of DSpace?  If you are on v7.x and have recently upgraded to
>> solr v9.0.0 there are a few tweaks you need to make in the search core's
>> solrconfig.xml (I can fill you in if this is the case).
>> ~~Bill
>>
>> On Wed, Jun 15, 2022 at 3:33 PM Thiago Cavalcanti 
>> wrote:
>>
>>> Hi there.
>>>
>>> I recently installed a fresh DSpace instance after a while, but I'm
>>> encountering an error with the search core in Solr. When initializing it,
>>> Solr throws this error:
>>>
>>> search:
>>> org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
>>> Could not load conf for core search: Can't load schema
>>> /var/solr/data/new_core/search/conf/schema.xml: Plugin init failure for
>>> [schema.xml] fieldType "text": Plugin init failure for [schema.xml]
>>> analyzer/filter: Error loading class
>>> 'org.apache.lucene.analysis.icu.ICUFoldingFilterFactory'
>>>
>>> Any clues on how to solve this?
>>>
>>> Thanks in advance,
>>> Thiago
>>>
>>> --
>>> 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 Technical Support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to dspace-tech...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/dspace-tech/54046817-1435-4ecf-8597-d27897ff71e0n%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>> Human wheels spin round and round
>> While the clock keeps the pace... -- John Mellencamp
>> 
>> Bill TantzenUniversity of Minnesota Libraries
>> 612-626-9949 <(612)%20626-9949> (U of M)612-325-1777
>> <(612)%20325-1777> (cell)
>>
> --
> 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 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/f6c88496-ce4b-4f92-b11b-0b8ec595a671n%40googlegroups.com
> 
> .
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7G0RHs4BvAzKKmX-PLsFvjG22fm1mVwZzKcybQ2XbRSqw%40mail.gmail.com.


Re: [dspace-tech] Solr error when initializing DSpace's search core

2022-06-15 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Thiago,
What version of DSpace?  If you are on v7.x and have recently upgraded to
solr v9.0.0 there are a few tweaks you need to make in the search core's
solrconfig.xml (I can fill you in if this is the case).
~~Bill

On Wed, Jun 15, 2022 at 3:33 PM Thiago Cavalcanti 
wrote:

> Hi there.
>
> I recently installed a fresh DSpace instance after a while, but I'm
> encountering an error with the search core in Solr. When initializing it,
> Solr throws this error:
>
> search:
> org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
> Could not load conf for core search: Can't load schema
> /var/solr/data/new_core/search/conf/schema.xml: Plugin init failure for
> [schema.xml] fieldType "text": Plugin init failure for [schema.xml]
> analyzer/filter: Error loading class
> 'org.apache.lucene.analysis.icu.ICUFoldingFilterFactory'
>
> Any clues on how to solve this?
>
> Thanks in advance,
> Thiago
>
> --
> 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 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/54046817-1435-4ecf-8597-d27897ff71e0n%40googlegroups.com
> 
> .
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7HZa%2BgEGkeL9yi_31w%2BT6L6ZHvdcTmiYFNeqRJ%3DZmPBHw%40mail.gmail.com.


Re: [dspace-tech] mirage2 build problems

2022-05-13 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Alan,
Cool, if I can take ruby and bower out of the mix, so much the better!  I
think this should work just fine with 5.x with maybe a little tweak here
and there.
~~Bill

On Fri, May 13, 2022 at 3:13 AM Alan Orth  wrote:

> Hi,
>
> Yes you're right that Mirage 2 build issues will be the same for DSpace
> 5.x and 6.x, and the solution would be similar as what I proposed here:
>
> https://github.com/DSpace/DSpace/pull/8292
>
> Basically, we can remove the dependency on Ruby and bower *completely*,
> moving entirely to npm for dependencies and node-sass (via npm) for Sass
> processing. In addition this means we can build with newer versions of
> Node.js (for example, the instructions say to use 0.10.31 but that is
> beyond ancient!). I am currently building Mirage 2 successfully with
> Node.js 10, 12, and even 14.
>
> I won't have time to look at a DSpace 5.x port of this Mirage 2 pull
> request for some time, but you might be able to draw some inspiration from
> the changes there on your own in the meantime...
>
> Regards,
>
> On Thu, May 12, 2022 at 6:14 PM 'Bill Tantzen' via DSpace Technical
> Support  wrote:
>
>> Thanks Jose!
>> I leveraged the instructions at
>> https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2#installation
>>  and
>> a single user installation of rvm to finally get my build to work.  Here's
>> what finally did it for me:
>>
>> ## grab rvm and install for the dspace user only:
>> curl -sSL https://get.rvm.io | bash -s stable
>> source /home/dspace/.rvm/scripts/rvm
>>
>> ## install a newish version of ruby (I did need to install a couple RHEL
>> packages, for which I have sudo)
>> rvm install 3.1.2
>> rvm use 3.1.2
>>
>> ## install nvm, node, bower, grunt, sass and compass
>> curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh
>> | bash
>> nvm install 12
>> nvm alias default 12
>> npm install -g bower
>> npm install -g grunt && npm install -g grunt-cli
>> gem install sass -v 3.3.14
>> gem install compass -v 1.0.1 (compass install actually upgrades sass to
>> 3.4.25)
>>
>> That's it, I was able to build successfully by
>> setting -Dmirage2.deps.included=false which I think is the default anyway.
>>
>> ~~Bill
>>
>> On Thu, May 12, 2022 at 10:05 AM Jose Blanco  wrote:
>>
>>> Hi Bill,
>>>
>>> I had the same problem.  Take a look at last message in this thread:
>>>
>>> https://groups.google.com/g/dspace-tech/c/7_fUBxsxkhs
>>>
>>> I have not tried the patch yet.  What I did is, since I had a
>>> successful Mirage2 build from a previous build in the webapp directory,
>>> copy it to
>>>
>>> dspace-xmlui/src/main/webapp/themes/Mirage2
>>>
>>> And then build it using:
>>> > mvn clean package
>>>
>>> From now on, if I need to make any changes to Mirage2, I will do it from:
>>>
>>> dspace-xmlui/src/main/webapp/themes/Mirage2
>>>
>>> That got me over the issue.
>>>
>>> -Jose
>>>
>>> On Thu, May 12, 2022 at 9:56 AM 'Bill Tantzen' via DSpace Technical
>>> Support  wrote:
>>>
>>>> I am recently required to rebuild my v5.10 instance with mirage2, and
>>>> I'm encountering the same problems as many others here since
>>>> torquebox.org is out of action.
>>>>
>>>> Does anybody have any tips?
>>>>
>>>> One major problem is that I cannot install rvm as root -- can I use
>>>> rbenv as an alternative?  Following the instructions in the mirage2 readme
>>>> (and the url below), here is what I have done:
>>>>
>>>> https://github.com/DSpace/DSpace/tree/dspace-5_x/dspace-xmlui-mirage2
>>>>
>>>> curl https://raw.githubusercontent.com/creationix/nvm/v0.5.1/install.sh
>>>> | sh
>>>> nvm install 0.10.31
>>>> nvm alias default 0.10.31
>>>> npm install -g bower
>>>> npm install -g grunt && npm install -g grunt-cli
>>>>
>>>> now, I break away and use rbenv instead of rvm…
>>>>
>>>> git clone https://github.com/rbenv/rbenv.git ~/.rbenv
>>>> mkdir -p "$(rbenv root)"/plugins
>>>> git clone https://github.com/rbenv/ruby-build.git "$(rbenv
>>>> root)"/plugins/ruby-build
>>>> rbenv install 3.1.2
>>>> rbenv global 3.1.2
>>>>
>>>> The first error I am encountering is:

Re: [dspace-tech] mirage2 build problems

2022-05-12 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Thanks Jose!
I leveraged the instructions at
https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2#installation
and
a single user installation of rvm to finally get my build to work.  Here's
what finally did it for me:

## grab rvm and install for the dspace user only:
curl -sSL https://get.rvm.io | bash -s stable
source /home/dspace/.rvm/scripts/rvm

## install a newish version of ruby (I did need to install a couple RHEL
packages, for which I have sudo)
rvm install 3.1.2
rvm use 3.1.2

## install nvm, node, bower, grunt, sass and compass
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh |
bash
nvm install 12
nvm alias default 12
npm install -g bower
npm install -g grunt && npm install -g grunt-cli
gem install sass -v 3.3.14
gem install compass -v 1.0.1 (compass install actually upgrades sass to
3.4.25)

That's it, I was able to build successfully by
setting -Dmirage2.deps.included=false which I think is the default anyway.

~~Bill

On Thu, May 12, 2022 at 10:05 AM Jose Blanco  wrote:

> Hi Bill,
>
> I had the same problem.  Take a look at last message in this thread:
>
> https://groups.google.com/g/dspace-tech/c/7_fUBxsxkhs
>
> I have not tried the patch yet.  What I did is, since I had a
> successful Mirage2 build from a previous build in the webapp directory,
> copy it to
>
> dspace-xmlui/src/main/webapp/themes/Mirage2
>
> And then build it using:
> > mvn clean package
>
> From now on, if I need to make any changes to Mirage2, I will do it from:
>
> dspace-xmlui/src/main/webapp/themes/Mirage2
>
> That got me over the issue.
>
> -Jose
>
> On Thu, May 12, 2022 at 9:56 AM 'Bill Tantzen' via DSpace Technical
> Support  wrote:
>
>> I am recently required to rebuild my v5.10 instance with mirage2, and I'm
>> encountering the same problems as many others here since torquebox.org
>> is out of action.
>>
>> Does anybody have any tips?
>>
>> One major problem is that I cannot install rvm as root -- can I use rbenv
>> as an alternative?  Following the instructions in the mirage2 readme (and
>> the url below), here is what I have done:
>>
>> https://github.com/DSpace/DSpace/tree/dspace-5_x/dspace-xmlui-mirage2
>>
>> curl https://raw.githubusercontent.com/creationix/nvm/v0.5.1/install.sh
>> | sh
>> nvm install 0.10.31
>> nvm alias default 0.10.31
>> npm install -g bower
>> npm install -g grunt && npm install -g grunt-cli
>>
>> now, I break away and use rbenv instead of rvm…
>>
>> git clone https://github.com/rbenv/rbenv.git ~/.rbenv
>> mkdir -p "$(rbenv root)"/plugins
>> git clone https://github.com/rbenv/ruby-build.git "$(rbenv
>> root)"/plugins/ruby-build
>> rbenv install 3.1.2
>> rbenv global 3.1.2
>>
>> The first error I am encountering is:
>> ...
>> ...
>> > Mirage2@0.1.1 postinstall
>> /swadm/dspace/projects/bill/dspace/modules/xmlui-mirage2/target/themes/Main
>> > bower install
>>
>> [INFO] -- (Main) org.codehaus.mojo:exec-maven-plugin:1.3.1:exec
>>
>>
>> /home/dspace/.nvm/v0.10.31/lib/node_modules/grunt/node_modules/grunt-cli/node_modules/liftup/node_modules/findup-sync/node_modules/micromatch/index.js:3
>> const util = require('util');
>> ^
>> SyntaxError: Use of const in strict mode.
>> at Module._compile (module.js:439:25)
>> at Object.Module._extensions..js (module.js:474:10)
>> at Module.load (module.js:356:32)
>> at Function.Module._load (module.js:312:12)
>> at Module.require (module.js:364:17)
>> at require (module.js:380:17)
>> at Object.
>> (/home/dspace/.nvm/v0.10.31/lib/node_modules/grunt/node_modules/grunt-cli/node_modules/liftup/node_modules/findup-sync/index.js:12:10)
>> at Module._compile (module.js:456:26)
>> at Object.Module._extensions..js (module.js:474:10)
>> at Module.load (module.js:356:32)
>> ...
>> ...
>>
>> Any suggestions on the right cocktail of versions and software I need to
>> get this to build?
>>
>> Thanks all,
>> ~~Bill
>>
>> --
>> Human wheels spin round and round
>> While the clock keeps the pace... -- John Mellencamp
>> 
>> Bill TantzenUniversity of Minnesota Libraries
>> 612-626-9949 (U of M)612-325-1777 (cell)
>>
>> --
>> 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 subscribe

[dspace-tech] mirage2 build problems

2022-05-12 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
I am recently required to rebuild my v5.10 instance with mirage2, and I'm
encountering the same problems as many others here since torquebox.org is
out of action.

Does anybody have any tips?

One major problem is that I cannot install rvm as root -- can I use rbenv
as an alternative?  Following the instructions in the mirage2 readme (and
the url below), here is what I have done:

https://github.com/DSpace/DSpace/tree/dspace-5_x/dspace-xmlui-mirage2

curl https://raw.githubusercontent.com/creationix/nvm/v0.5.1/install.sh | sh
nvm install 0.10.31
nvm alias default 0.10.31
npm install -g bower
npm install -g grunt && npm install -g grunt-cli

now, I break away and use rbenv instead of rvm…

git clone https://github.com/rbenv/rbenv.git ~/.rbenv
mkdir -p "$(rbenv root)"/plugins
git clone https://github.com/rbenv/ruby-build.git "$(rbenv
root)"/plugins/ruby-build
rbenv install 3.1.2
rbenv global 3.1.2

The first error I am encountering is:
...
...
> Mirage2@0.1.1 postinstall
/swadm/dspace/projects/bill/dspace/modules/xmlui-mirage2/target/themes/Main
> bower install

[INFO] -- (Main) org.codehaus.mojo:exec-maven-plugin:1.3.1:exec

/home/dspace/.nvm/v0.10.31/lib/node_modules/grunt/node_modules/grunt-cli/node_modules/liftup/node_modules/findup-sync/node_modules/micromatch/index.js:3
const util = require('util');
^
SyntaxError: Use of const in strict mode.
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.
(/home/dspace/.nvm/v0.10.31/lib/node_modules/grunt/node_modules/grunt-cli/node_modules/liftup/node_modules/findup-sync/index.js:12:10)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
...
...

Any suggestions on the right cocktail of versions and software I need to
get this to build?

Thanks all,
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7E3YVEmw12XQxkdssj9VHeHJFQTc%2BDAnK_YCj9V7FXwpA%40mail.gmail.com.


Re: [dspace-tech] administrator actions in 7.2

2022-02-09 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
OK, problem solved, and it's not really a pm2 issue.

It seems there was a stale node process holding onto port 4000 (even though
netstat did not reveal it).  I manually killed that process, restarted the
server with pm2, and voila!  This was not really apparent in checking the
pm2 logs, which actually indicated everything was fine and executing from
the correct project.

Just a guess, but maybe in the process of upgrading the previous version
was not stopped properly by pm2?  Hard to say now. But everything is
working fine now.

~~Bill

On Wed, Feb 9, 2022 at 9:18 AM Tim Donohue  wrote:

> Hi Bill,
>
> Ok, just double checking.
>
> In that case, my best guess is something is "cached" in PM2 itself.
>
> Make sure that all the PM2 processes related to DSpace are fully stopped.
> Check your running processes.  You also could try "pm2 stop
> dspace-angular.json".
>
> If that also doesn't work, try *deleting*​ your app config (in PM2), and
> starting again.  So, something like:
> pm2 delete dspace-angular.json
> pm2 start dspace-angular.json
> (This obviously won't delete your dspace-angular app entirely, it just
> deletes your previous PM2 configuration for dspace-angular, in case that's
> getting in the way)
>
> That hint came via Google, where I stumbled on what looks to be a similar
> discussion in this old PM2 issue ticket:
> https://github.com/Unitech/pm2/issues/96#issuecomment-817920882
>
> If this works for you (or you find a different fix), let us know...we may
> need to copy this hint into our Upgrade Guide in case others run across
> this same issue.
>
> Tim
> --
> *From:* Bill Tantzen 
> *Sent:* Wednesday, February 9, 2022 8:54 AM
> *To:* Tim Donohue 
> *Cc:* DSpace Technical Support 
> *Subject:* Re: [dspace-tech] administrator actions in 7.2
>
> Yes, the start file is correct -- I have checked and double checked!
>
> On Wed, Feb 9, 2022 at 8:46 AM Tim Donohue 
> wrote:
>
> Bill,
>
> Something simple...have you double checked the "cwd" directory in your
> dspace-angular.json​ configuration for PM2?  That's the directory where
> PM2 should run the "yarn run serve:ssr".  So, if that "cwd" directory is
> your 7.1 root folder, it'll always run 7.1.  If it's your 7.2 root folder,
> it should always run 7.2.
>
> Essentially, I'd first look more closely at the JSON config you are
> passing to PM2.  It sounds like PM2 is either running yarn from the wrong
> folder, or somehow getting confused by your config.
>
> Tim
> --
> *From:* 'Bill Tantzen' via DSpace Technical Support <
> dspace-tech@googlegroups.com>
> *Sent:* Wednesday, February 9, 2022 8:03 AM
> *To:* Tim Donohue 
> *Cc:* DSpace Technical Support 
> *Subject:* Re: [dspace-tech] administrator actions in 7.2
>
> All,
> I believe I have figured out what is going on.  Yes, it seems that I am
> running the old version of the frontend.
>
> This happens because I have both versions (dspace-angular-dspace-7.1
> and dspace-angular-dspace-7.2) in the same directory.  When I execute
>
> pm2 start dspace-angular.json
>
> the old version is served up.  Yes, I have updated my dspace-angular.json
> file to point to the correct directory.  In fact, when I remove the old
> version, pm2 will serve an error page instead:
>
> Error: ENOENT: no such file or directory, stat
> '/dspace/projects/dspace-angular-dspace-7.1/dist/browser/index.html'
>
> pm2 simply refuses to start the correct application.  This is the latest
> version (v4.5.6 by the way).
>
> I realize this is NOT a DSpace problem, but I'm hoping that somebody else
> has run into this problem and solved it.  I have scoured the web trying to
> figure this out with no luck so far.
>
> Any pm2 experts on the list?
> ~~Bill
>
>
>
> On Tue, Feb 8, 2022 at 4:24 PM Tim Donohue 
> wrote:
>
> Hi Bill,
>
> Yes, those GET requests are your UI attempting to check your permissions
> on the backend.
>
> The one you sent has a "uri" equal to your "Site object", and a
> "feature=isCollectionAdmin".  That means it's attempting to check if you
> have Collection Admin rights on *any*​ Collection in the entire site.
> Since it looks to be returning "totalElements: 0" that means the backend
> thinks you are *not*​ a Collection Admin on any Collection.  If you had
> this permission, that "totalElements" would be greater than zero.
>
> Your result from the HAL browser is more accurate (returns "totalElements:
> 1" instead), and you *should*​ see the same result from the UI an

Re: [dspace-tech] administrator actions in 7.2

2022-02-09 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Yes, the start file is correct -- I have checked and double checked!

On Wed, Feb 9, 2022 at 8:46 AM Tim Donohue  wrote:

> Bill,
>
> Something simple...have you double checked the "cwd" directory in your
> dspace-angular.json​ configuration for PM2?  That's the directory where
> PM2 should run the "yarn run serve:ssr".  So, if that "cwd" directory is
> your 7.1 root folder, it'll always run 7.1.  If it's your 7.2 root folder,
> it should always run 7.2.
>
> Essentially, I'd first look more closely at the JSON config you are
> passing to PM2.  It sounds like PM2 is either running yarn from the wrong
> folder, or somehow getting confused by your config.
>
> Tim
> --
> *From:* 'Bill Tantzen' via DSpace Technical Support <
> dspace-tech@googlegroups.com>
> *Sent:* Wednesday, February 9, 2022 8:03 AM
> *To:* Tim Donohue 
> *Cc:* DSpace Technical Support 
> *Subject:* Re: [dspace-tech] administrator actions in 7.2
>
> All,
> I believe I have figured out what is going on.  Yes, it seems that I am
> running the old version of the frontend.
>
> This happens because I have both versions (dspace-angular-dspace-7.1
> and dspace-angular-dspace-7.2) in the same directory.  When I execute
>
> pm2 start dspace-angular.json
>
> the old version is served up.  Yes, I have updated my dspace-angular.json
> file to point to the correct directory.  In fact, when I remove the old
> version, pm2 will serve an error page instead:
>
> Error: ENOENT: no such file or directory, stat
> '/dspace/projects/dspace-angular-dspace-7.1/dist/browser/index.html'
>
> pm2 simply refuses to start the correct application.  This is the latest
> version (v4.5.6 by the way).
>
> I realize this is NOT a DSpace problem, but I'm hoping that somebody else
> has run into this problem and solved it.  I have scoured the web trying to
> figure this out with no luck so far.
>
> Any pm2 experts on the list?
> ~~Bill
>
>
>
> On Tue, Feb 8, 2022 at 4:24 PM Tim Donohue 
> wrote:
>
> Hi Bill,
>
> Yes, those GET requests are your UI attempting to check your permissions
> on the backend.
>
> The one you sent has a "uri" equal to your "Site object", and a
> "feature=isCollectionAdmin".  That means it's attempting to check if you
> have Collection Admin rights on *any*​ Collection in the entire site.
> Since it looks to be returning "totalElements: 0" that means the backend
> thinks you are *not*​ a Collection Admin on any Collection.  If you had
> this permission, that "totalElements" would be greater than zero.
>
> Your result from the HAL browser is more accurate (returns "totalElements:
> 1" instead), and you *should*​ see the same result from the UI and HAL
> Browser if everything is setup properly.
>
> So, this implies to me that something may be wrong with your setup.  My
> guess is that for some reason the backend doesn't "believe" you are
> authenticated...or it isn't *trusting*​ your frontend in some way.
>
> You should look very closely at the "Network" tab of your browser's
> DevTools when you login and especially *after*​ you have just logged in.
> You shouldn't see any red, error responses from the backend...but my best
> guess is you likely will see something odd there.  Again, here's how to
> look for errors on the frontend:
> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>
> I'd venture to guess you might be hitting an installation/upgrade error,
> it might even be one of these common installation issues:
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
> (Usually these are caused by a misconfiguration between the frontend &
> backend)
>
> If none of that helps...check all your backend logs very closely and look
> for ERROR messages there.  Something seems "off", and it sounds to me like
> your Backend is either not trusting the frontend, or your Backend is
> silently erroring out every time you try to login.
>
> Tim
>
>
>
> --
> *From:* 'Bill Tantzen' via DSpace Technical Support <
> dspace-tech@googlegroups.com>
> *Sent:* Tuesday, February 8, 2022 3:31 PM
> *To:* DSpace Technical Support 
> *Subject:* Re: [dspace-tech] administrator actions in 7.2
>
> Sorry, forgot to copy the list.
>
> In the apache logs, I see a number of GETs that look like:
>
> /server/api/authz/authorizations/search/object?uri=
> https://udc-prd.lib.umn.edu/server/api/cor

Re: [dspace-tech] administrator actions in 7.2

2022-02-09 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
All,
I believe I have figured out what is going on.  Yes, it seems that I am
running the old version of the frontend.

This happens because I have both versions (dspace-angular-dspace-7.1
and dspace-angular-dspace-7.2) in the same directory.  When I execute

pm2 start dspace-angular.json

the old version is served up.  Yes, I have updated my dspace-angular.json
file to point to the correct directory.  In fact, when I remove the old
version, pm2 will serve an error page instead:

Error: ENOENT: no such file or directory, stat
'/dspace/projects/dspace-angular-dspace-7.1/dist/browser/index.html'

pm2 simply refuses to start the correct application.  This is the latest
version (v4.5.6 by the way).

I realize this is NOT a DSpace problem, but I'm hoping that somebody else
has run into this problem and solved it.  I have scoured the web trying to
figure this out with no luck so far.

Any pm2 experts on the list?
~~Bill



On Tue, Feb 8, 2022 at 4:24 PM Tim Donohue  wrote:

> Hi Bill,
>
> Yes, those GET requests are your UI attempting to check your permissions
> on the backend.
>
> The one you sent has a "uri" equal to your "Site object", and a
> "feature=isCollectionAdmin".  That means it's attempting to check if you
> have Collection Admin rights on *any*​ Collection in the entire site.
> Since it looks to be returning "totalElements: 0" that means the backend
> thinks you are *not*​ a Collection Admin on any Collection.  If you had
> this permission, that "totalElements" would be greater than zero.
>
> Your result from the HAL browser is more accurate (returns "totalElements:
> 1" instead), and you *should*​ see the same result from the UI and HAL
> Browser if everything is setup properly.
>
> So, this implies to me that something may be wrong with your setup.  My
> guess is that for some reason the backend doesn't "believe" you are
> authenticated...or it isn't *trusting*​ your frontend in some way.
>
> You should look very closely at the "Network" tab of your browser's
> DevTools when you login and especially *after*​ you have just logged in.
> You shouldn't see any red, error responses from the backend...but my best
> guess is you likely will see something odd there.  Again, here's how to
> look for errors on the frontend:
> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>
> I'd venture to guess you might be hitting an installation/upgrade error,
> it might even be one of these common installation issues:
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
> (Usually these are caused by a misconfiguration between the frontend &
> backend)
>
> If none of that helps...check all your backend logs very closely and look
> for ERROR messages there.  Something seems "off", and it sounds to me like
> your Backend is either not trusting the frontend, or your Backend is
> silently erroring out every time you try to login.
>
> Tim
>
>
>
> --
> *From:* 'Bill Tantzen' via DSpace Technical Support <
> dspace-tech@googlegroups.com>
> *Sent:* Tuesday, February 8, 2022 3:31 PM
> *To:* DSpace Technical Support 
> *Subject:* Re: [dspace-tech] administrator actions in 7.2
>
> Sorry, forgot to copy the list.
>
> In the apache logs, I see a number of GETs that look like:
>
> /server/api/authz/authorizations/search/object?uri=
> https://udc-prd.lib.umn.edu/server/api/core/sites/0175ee52-5642-4302-89a1-99c444e5bd2c&feature=isCollectionAdmin&embed=feature
>
> Is this what you are referring to?  With different features like
> isCommunityAdmin, etc.  Likely the stuff I am looking for.  All of them
> result in a code 200; no errors.
>
> The same urls in the HAL browser result in:
>
> {
>   "_embedded": {
> "authorizations": [
>   {
> "id":
> "e12c38cf-c5eb-4174-871c-3ce124d3889b_isCollectionAdmin_core.site_0175ee52-5642-4302-89a1-99c444e5bd2c",
> "type": "authorization",
> "_links": {
>   "eperson": {
> "href": "
> https://udc-prd.lib.umn.edu/server/api/authz/authorizations/e12c38cf-c5eb-4174-871c-3ce124d3889b_isCollectionAdmin_core.site_0175ee52-5642-4302-89a1-99c444e5bd2c/eperson
> "
>   },
>   "feature": {
> "href": "
> https://udc-prd.lib.umn.edu/server/api/authz/authorizations/e12c38cf-c5eb-4174-871c-3ce124d3889b_isCollectionAdmin_core.site_0175ee52-5642-4302-89a1-99c444e5bd2c

Re: [dspace-tech] administrator actions in 7.2

2022-02-08 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
t;> *To:* Tim Donohue 
>> *Subject:* Re: [dspace-tech] administrator actions in 7.2
>>
>> Oh no, I'm sure it's not a code issue;  I was thinking it was a new
>> configuration setup.  I'll check the logs and see if there is any help
>> there.  This worked fine in 7.0 and 7.1 (as well as the demo site), and I'm
>> for sure a member of the Administrator group, so it's a little weird!
>> ~~Bill
>>
>> On Tue, Feb 8, 2022 at 2:47 PM Tim Donohue 
>> wrote:
>>
>> Hi Bill,
>>
>> Those side menus should be checking which groups you are a member of
>> automatically (by querying the backend/REST API when you login). They are
>> coded to do so in the AdminSidebar component, starting around here:
>> https://github.com/DSpace/dspace-angular/blob/main/src/app/admin/admin-sidebar/admin-sidebar.component.ts#L133
>>
>> If you look at each of the sections, they are coded to detect if you are
>> a SiteAdmin (i.e. in "Administrator" group), or a Community or Collection
>> admin (of any community/collection), and based on your permissions, it'll
>> show appropriate menus.  So, for a SiteAdmin, all menus should be displayed.
>>
>> I *doubt*​ it's that code that's to blame...as this is the first time
>> I've heard of this behavior & it seems to work fine on demo7.dspace.org.
>> You may want to look around more closely at your logs (in case any error is
>> occurring), and even look at whether the UI is throwing a client-side
>> error...see this guide for finding UI errors in your browser's DevTools:
>> https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
>>
>> My best guess is there's some sort of error occurring that's causing this
>> behavior... either that, or something with your Administrator group or user
>> account has gotten messed up.
>>
>> Tim
>>
>>
>> --
>> *From:* 'Bill Tantzen' via DSpace Technical Support <
>> dspace-tech@googlegroups.com>
>> *Sent:* Tuesday, February 8, 2022 1:00 PM
>> *To:* DSpace Technical Support 
>> *Subject:* [dspace-tech] administrator actions in 7.2
>>
>> Configuration question I guess.
>>
>> I am a member of the Administrators group.  However when I log in, most
>> of the administrator actions on the sidebar are not available to me (for
>> instance, create a community/collection, access control, administer
>> workflow etc).  The only options available are create an item, and
>> import/export metadata.  All those actions are available to me upon login
>> in our current version, 5.10.
>>
>> Can you point me to where this is configured in 7.2? Or better yet to the
>> documentation (if it exists yet)?
>> Thanks a million,
>> ~~Bill
>>
>> --
>> Human wheels spin round and round
>> While the clock keeps the pace... -- John Mellencamp
>> 
>> Bill TantzenUniversity of Minnesota Libraries
>> 612-626-9949 (U of M)612-325-1777 (cell)
>>
>> --
>> 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 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/CADgrb7G2-TszXbDAHjeYo3bQbUQ2HQYOf_x%3DzGxRLKX6rdBHiQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/dspace-tech/CADgrb7G2-TszXbDAHjeYo3bQbUQ2HQYOf_x%3DzGxRLKX6rdBHiQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>>
>>
>> --
>> Human wheels spin round and round
>> While the clock keeps the pace... -- John Mellencamp
>> 
>> Bill TantzenUniversity of Minnesota Libraries
>> 612-626-9949 (U of M)612-325-1777 (cell)
>>
>
>
> --
> Human wheels spin round and round
> While the clock keeps the pace... -- John Mellencamp
> 
> Bill TantzenUniversity of Minnesota Libraries
> 612-626-9949 (U of M)612-325-1777 (cell)
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7E0NvgjFiBxNiHVHJf%2B7Zbx6MKCL37pGqhbRiZk9AfEBw%40mail.gmail.com.


[dspace-tech] administrator actions in 7.2

2022-02-08 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Configuration question I guess.

I am a member of the Administrators group.  However when I log in, most of
the administrator actions on the sidebar are not available to me (for
instance, create a community/collection, access control, administer
workflow etc).  The only options available are create an item, and
import/export metadata.  All those actions are available to me upon login
in our current version, 5.10.

Can you point me to where this is configured in 7.2? Or better yet to the
documentation (if it exists yet)?
Thanks a million,
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7G2-TszXbDAHjeYo3bQbUQ2HQYOf_x%3DzGxRLKX6rdBHiQ%40mail.gmail.com.


[dspace-tech] warning on ant install

2022-02-07 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
In DSpace 7.2, I am seeing the following warning when executing ant
update.  It seemingly does not hurt anything, but I'm just curious...

 [java] FlywayDB Version: 6.5.7
 [java] 2022-02-07 12:22:31,196 WARN
 org.dspace.services.sessions.StatelessRequestServiceImpl @ Request
interceptor
(org.dspace.services.events.SystemEventService$EventRequestInterceptor@394433c0)
failed to execute on end (request-135-1644258150871): null

openjdk 11.0.12
postgres 12.2
ant 1.10.11

Any red flags here?
Thanks,
~~Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7GCESXmFEe0dxGhH8fUeskNPz_HM8u%2B3fihhp16uW0aDQ%40mail.gmail.com.


[dspace-tech] Configurable Workflow question

2021-12-17 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
I appear to have a permissions problem with configurable workflow in DSpace
v5.10

There is a user who has the roles:
COLLECTION_1709_WORKFLOW_ROLE_editor
COLLECTION_1709_ADMIN
COLLECTION_1709_SUBMIT

When the user attempts to claim a workflow task associated with this
collection, the following stacktrace is produced:

Java stacktrace: org.dspace.authorize.AuthorizeException: Authorization
denied for action WRITE on ITEM:106620 by user 1636
at
org.dspace.authorize.AuthorizeManager.authorizeAction(AuthorizeManager.java:182)
at
org.dspace.authorize.AuthorizeManager.authorizeAction(AuthorizeManager.java:101)
at org.dspace.content.Item.update(Item.java:1035)
at
org.dspace.xmlworkflow.storedcomponents.XmlWorkflowItem.update(XmlWorkflowItem.java:397)
at
org.dspace.xmlworkflow.WorkflowRequirementsManager.addClaimedUser(WorkflowRequirementsManager.java:69)
at
org.dspace.xmlworkflow.state.actions.userassignment.ClaimAction.execute(ClaimAction.java:56)
at
org.dspace.xmlworkflow.XmlWorkflowManager.doState(XmlWorkflowManager.java:176)
at
org.dspace.app.xmlui.aspect.xmlworkflow.ClaimTasksAction.act(ClaimTasksAction.java:48)

and on and on...

Also, this workflowitem is removed from cwf_pooltask, and one is inserted
into cwf_in_progress.

This appears to be related to permissions; Is there an additional role I
need to assign to this user?

Thanks in advance,
Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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 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/CADgrb7FkJuwsVomgU4%2B5OYqkbBotdTM%2BGdUmgf%2B1%2BNTKEmMLxg%40mail.gmail.com.


[dspace-tech] Authentication with Shibboleth

2021-04-26 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
All,
So far, I have not been able to authenticate users via Shibboleth.  I have
found this issue: DS-4396
.
Is this where the issue of shib login currently stands?  An further
information?
Thanks,
~~ Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
All messages to this mailing list should adhere to the 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/CADgrb7Hho5QuU69Lx2s9h00%2BpoUuUsMct5JnamoijJM0UWT8MQ%40mail.gmail.com.


[dspace-tech] Re: running the frontend over ssl

2021-04-22 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Still experimenting with this issue, and I have a little more info:  curl
--verbose gives a few more details and everything looks OK...  My
recollection is that this worked fine in previous betas.

curl --verbose https://:4000/
Trying xxx.xxx.xxx.xxx...
* TCP_NODELAY set
* Connected to  (xxx.xxx.xxx.xxx) port 4000 (#0)
...
...
...
*  SSL certificate verify ok.
> GET / HTTP/1.1
> Host: :4000
> User-Agent: curl/7.64.1
> Accept: */*
>

At this point, curl (like my browser) simply hangs.  There is nothing in
the pm2 out.log nor in the error.log


On Tue, Apr 20, 2021 at 1:19 PM Bill Tantzen  wrote:

> I'm having problems getting the frontend to work over ssl.  I have
> verified that it starts and runs with ssl: false on port 4000.  I have
> added valid .key and .pem files to config/ssl and simply changed ssl to
> true, rebuilt, and started via pm2
>
> The build completes without an error, and dspace-angular starts without
> error as well (specifically, I do not get the error I observed when I
> accidentally loaded a wrong .pem file).
>
> My .pm2/logs/dspace-angular-out.log is:
> yarn run v1.16.0
> $ node dist/server
> [13:03:03 GMT-0500 (Central Daylight Time)] Listening at https://
> .edu:4000/
>
> and my .pm2/logs/dspace-angular-error.log is empty
>
> However, when I try to connect via the url given in the log file, I get no
> response, and the browser or curl simply hangs.
>
> The error log remains empty, and the out log has an additional entry:
> [HPM] Proxy created: /  -> https://.edu/server/sitemaps
>
> Again, this all works OK with ssl: false and no other changes.  Any clue
> as to what I may have done wrong?
> Thank you,
> ~~ Bill
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
All messages to this mailing list should adhere to the 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/CADgrb7HNQemQhybxHMVtA__9iaRj%2BOvfvGYVorFh%3D0vXuiXXRw%40mail.gmail.com.


[dspace-tech] Shibboleth setup for DSpace7

2021-04-21 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Is there updated documentation on how to configure dspace 7 for shibboleth?
Thanks!
~~ Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
All messages to this mailing list should adhere to the 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/CADgrb7F0DZoaqvqU0siDcBjk20SbzbRsaXJEzX_7UjwtaT4Bcg%40mail.gmail.com.


[dspace-tech] question on dc.identifier.uri in dspace 7

2021-04-20 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
In an early build of my backend, I had

dspace.ui.url = https://.edu:3000

now, it is simply

dspace.ui.url = https://.edu

After rebuilding, redeploying, and restarting the server, my
dc.identifier.uri's are all still displaying with :3000. I have cleaned my
dspace directory aggressively, and cleared the browser, but these uri's
remain unchanged in the HAL browser (as well as the frontend of course.).
Is this setting cached somewhere?

~~ Bill
-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
All messages to this mailing list should adhere to the 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/CADgrb7GwA2ofKJGLfui%2BH7Os4WKvM7YqeCkhRKQdB%3DrDo9FgTw%40mail.gmail.com.


[dspace-tech] running the frontend over ssl

2021-04-20 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
I'm having problems getting the frontend to work over ssl.  I have verified
that it starts and runs with ssl: false on port 4000.  I have added valid
.key and .pem files to config/ssl and simply changed ssl to true, rebuilt,
and started via pm2

The build completes without an error, and dspace-angular starts without
error as well (specifically, I do not get the error I observed when I
accidentally loaded a wrong .pem file).

My .pm2/logs/dspace-angular-out.log is:
yarn run v1.16.0
$ node dist/server
[13:03:03 GMT-0500 (Central Daylight Time)] Listening at https://
.edu:4000/

and my .pm2/logs/dspace-angular-error.log is empty

However, when I try to connect via the url given in the log file, I get no
response, and the browser or curl simply hangs.

The error log remains empty, and the out log has an additional entry:
[HPM] Proxy created: /  -> https://.edu/server/sitemaps

Again, this all works OK with ssl: false and no other changes.  Any clue as
to what I may have done wrong?
Thank you,
~~ Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
All messages to this mailing list should adhere to the 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/CADgrb7Gaf-nCwb78UHVkOKvtT7WenU5Uamzz7YyAFKJqibYfaQ%40mail.gmail.com.


[dspace-tech] informal survey regarding bitstream limits and sizes

2021-04-15 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Sorry for the duplication -- I originally sent this to dspace-community,
but I it did not generate a great deal of discussion, so I thought I would
take my chances here:

If you have a minute, I am trying to get a feel for some of the larger
(reasonable) bitstreams the community is currently supporting.  On my site,
we have removed the DSpace upload limits to allow for records containing
research data, but of course there are practical limits that dictate what
makes for a good user experience.

What is the largest bitstream you support?  Do you enforce upload limits?
Assuming download speeds are faster than upload speeds, what are some of
the methods in use (besides the DSpace gui) to get large files onto the
server?  What are some alternatives to simple DSpace upload currently
utilized -- like globus for instance?

I realize the answer to these questions will always include "it
depends...", but are these all questions you have had at your institution
and how have you dealt with them?

Thanks for any discussion you wish to contribute!
~~ Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
All messages to this mailing list should adhere to the 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/CADgrb7EdmEZ9kYOVT%2BzNLQQhwYJpYFDG5wXLQOqv6FcJeBORPg%40mail.gmail.com.


Re: [dspace-tech] Withdrawn Items

2020-10-29 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
A little followup on this -- in our case this is the result of specific
bitstream (not item) urls in the google search index.  When
interpreting these urls in BitstreamReader.java, DSpace responds with a 302
Found response and redirects to the request-a-copy page regardless of
whether or not the bitstream was embargoed or not.  It looks like this is
exactly how DSpace was designed to respond in this situation.

Hope that sheds some light on your situation!
~~ Bill

On Wed, Oct 28, 2020 at 1:40 PM Bill Tantzen  wrote:

> Coincidentally, I just received a complaint about this behavior myself...
> We are running DSpace v5.10 and xmlui as well.  The withdrawn items are in
> google search results and the link in google is to the Request a copy
> page.  This explains how the user is able to obtain the link to the Request
> a copy page, but it doesn't explain why, since the records were never
> embargoed to begin with.
>
> I haven't investigated this any further, but I seem to recall that
> withdrawn items are still discoverable, but are they still crawled (or
> placed in sitemaps)?  How are they interpreted as embargoed?  I'll be
> digging a little deeper, since this is highly undesirable behavior, but has
> anybody else noticed this?
> ~~ Bill
>
> On Mon, Oct 26, 2020 at 8:16 AM Keith Jones  wrote:
>
>> Hi All,
>>
>> I'm running an instance of dspace 5.3 using the xmlui interface, and
>> recently had a user send me a request for a withdrawn item. I was
>> wondering how the user was able to send the request, when I try to
>> access the item, the public interface just says the item is withdrawn.
>> How did the user generate the "Request copy of document" email?
>>
>> Thanks
>> Keith
>>
>> --
>> 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/CAJ6iCzMGqi438h_FmF4grkVqNweD%3DpD4y4WHPoFjSb_gFCssLA%40mail.gmail.com
>> .
>>
>
>
> --
> Human wheels spin round and round
> While the clock keeps the pace... -- John Mellencamp
> 
> Bill TantzenUniversity of Minnesota Libraries
> 612-626-9949 (U of M)612-325-1777 (cell)
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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/CADgrb7Ej5NdeoRz2oAVtaC-zDZHysPdMiV2HmOPtRL3zgrcd4w%40mail.gmail.com.


Re: [dspace-tech] Withdrawn Items

2020-10-28 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Coincidentally, I just received a complaint about this behavior myself...
We are running DSpace v5.10 and xmlui as well.  The withdrawn items are in
google search results and the link in google is to the Request a copy
page.  This explains how the user is able to obtain the link to the Request
a copy page, but it doesn't explain why, since the records were never
embargoed to begin with.

I haven't investigated this any further, but I seem to recall that
withdrawn items are still discoverable, but are they still crawled (or
placed in sitemaps)?  How are they interpreted as embargoed?  I'll be
digging a little deeper, since this is highly undesirable behavior, but has
anybody else noticed this?
~~ Bill

On Mon, Oct 26, 2020 at 8:16 AM Keith Jones  wrote:

> Hi All,
>
> I'm running an instance of dspace 5.3 using the xmlui interface, and
> recently had a user send me a request for a withdrawn item. I was
> wondering how the user was able to send the request, when I try to
> access the item, the public interface just says the item is withdrawn.
> How did the user generate the "Request copy of document" email?
>
> Thanks
> Keith
>
> --
> 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/CAJ6iCzMGqi438h_FmF4grkVqNweD%3DpD4y4WHPoFjSb_gFCssLA%40mail.gmail.com
> .
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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/CADgrb7GNOzUAuHgHHP2pgQdwUYKWK5bt4Vy79V%3Dp6hrVYPT5%2BQ%40mail.gmail.com.


[dspace-tech] DSpace 7 new item page question

2020-07-22 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
DSpace 7, beta 3:

On the "new item"  submission form, there is a button labeled "Lookup" next
to the Author fields that leads to a popup search form.  Sorry if I'm
missing something in the documentation, but what's that all about (and how
do I enable it)?

Cheers!
~~ Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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/CADgrb7ExngLtYfZHBiSp8mZmtu0rHyZZdM4NUMzXxbMNOX1i6Q%40mail.gmail.com.


[dspace-tech] Re: Shibboleth login on dspace 7 fails with Safari

2020-07-15 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
I should add that I experience the same results when logging into the HAL
browser; works on Firefox and Chrome, fails in the same way with Safari.
This used to work on beta 2.
~~ Bill

On Tue, Jul 14, 2020 at 4:09 PM Bill Tantzen  wrote:

> My client is at https://ui.lib.umn.edu:3000 and the REST API at
> rest.lib.umn.edu. My apache shib configuration is as described at
> https://wiki.lyrasis.org/display/DSPACE/DSpace+7+Shibboleth+Configuration.
> I can login with Firefox and Chrome, but when logging in with Safari, the
> REST server responds with a 403.
>
> A successful login (via Chrome) looks like this in the apache logs:
> 10.21.41.171 - - [14/Jul/2020:15:35:06 -0500] "GET
> /Shibboleth.sso/Login?target=
> https://rest.lib.umn.edu/server/api/authn/shibboleth?redirectUrl=https://ui.lib.umn.edu:3000/home
> HTTP/1.1" 302 860
> 10.21.41.171 - - [14/Jul/2020:15:35:28 -0500] "POST
> /Shibboleth.sso/SAML2/POST HTTP/1.1" 302 289
> 10.21.41.171 - tantz...@umn.edu [14/Jul/2020:15:35:28 -0500] "GET
> /server/api/authn/shibboleth?redirectUrl=https://ui.lib.umn.edu:3000/home
> HTTP/1.1" 302 -
>
> An unsuccessful login (via Safari) from the same workstation is similar:
> 10.21.41.171 - - [14/Jul/2020:15:32:48 -0500] "GET
> /Shibboleth.sso/Login?target=
> https://rest.lib.umn.edu/server/api/authn/shibboleth?redirectUrl=https://ui.lib.umn.edu:3000/home
> HTTP/1.1" 302 858
> 10.21.41.171 - - [14/Jul/2020:15:33:21 -0500] "POST
> /Shibboleth.sso/SAML2/POST HTTP/1.1" 302 289
> 10.21.41.171 - tantz...@umn.edu [14/Jul/2020:15:33:21 -0500] "GET
> /server/api/authn/shibboleth?redirectUrl=https://ui.lib.umn.edu:3000/home
> HTTP/1.1" 403 20
>
> Which is identical except for the 403, and a small text file from the IdP
> that contains "Invalid CORS request"
>
> I'm not sure -- angular bug?  server bug?  Safari bug?  This worked fine
> across all browsers in beta 2...  My next test will be to place the client
> and server on the same host...  Meanwhile, I'm not sure where to go!
>
> Thanks for any advice!
> ~~ Bill
>
> --
> Human wheels spin round and round
> While the clock keeps the pace... -- John Mellencamp
> 
> Bill TantzenUniversity of Minnesota Libraries
> 612-626-9949 (U of M)612-325-1777 (cell)
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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/CADgrb7FPWoTQuzrpohc7Vdg4Rq5XkWWDG0dxt2VUEqBhmrKXNg%40mail.gmail.com.


[dspace-tech] Shibboleth login on dspace 7 fails with Safari

2020-07-14 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
My client is at https://ui.lib.umn.edu:3000 and the REST API at
rest.lib.umn.edu. My apache shib configuration is as described at
https://wiki.lyrasis.org/display/DSPACE/DSpace+7+Shibboleth+Configuration.
I can login with Firefox and Chrome, but when logging in with Safari, the
REST server responds with a 403.

A successful login (via Chrome) looks like this in the apache logs:
10.21.41.171 - - [14/Jul/2020:15:35:06 -0500] "GET
/Shibboleth.sso/Login?target=
https://rest.lib.umn.edu/server/api/authn/shibboleth?redirectUrl=https://ui.lib.umn.edu:3000/home
HTTP/1.1" 302 860
10.21.41.171 - - [14/Jul/2020:15:35:28 -0500] "POST
/Shibboleth.sso/SAML2/POST HTTP/1.1" 302 289
10.21.41.171 - tantz...@umn.edu [14/Jul/2020:15:35:28 -0500] "GET
/server/api/authn/shibboleth?redirectUrl=https://ui.lib.umn.edu:3000/home
HTTP/1.1" 302 -

An unsuccessful login (via Safari) from the same workstation is similar:
10.21.41.171 - - [14/Jul/2020:15:32:48 -0500] "GET
/Shibboleth.sso/Login?target=
https://rest.lib.umn.edu/server/api/authn/shibboleth?redirectUrl=https://ui.lib.umn.edu:3000/home
HTTP/1.1" 302 858
10.21.41.171 - - [14/Jul/2020:15:33:21 -0500] "POST
/Shibboleth.sso/SAML2/POST HTTP/1.1" 302 289
10.21.41.171 - tantz...@umn.edu [14/Jul/2020:15:33:21 -0500] "GET
/server/api/authn/shibboleth?redirectUrl=https://ui.lib.umn.edu:3000/home
HTTP/1.1" 403 20

Which is identical except for the 403, and a small text file from the IdP
that contains "Invalid CORS request"

I'm not sure -- angular bug?  server bug?  Safari bug?  This worked fine
across all browsers in beta 2...  My next test will be to place the client
and server on the same host...  Meanwhile, I'm not sure where to go!

Thanks for any advice!
~~ Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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/CADgrb7Fip73uL%2BXt217Nx5z%3DTFCEF4ScPg9X%3DzQqapt2in_Cbw%40mail.gmail.com.


[dspace-tech] Re: problems with dspace-angular-beta3

2020-07-10 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Hi all!

A little followup information regarding my problems getting
dspace-angular-beta03 up and running.  The client works if it is installed
and running on my localhost:4000 against the test api
at dspace7.4science.cloud.  Running the client on localhost on any other
port, or against my own server results in the preflight/cors errors
described below.  It all means that nobody but me can see the latest
version (it seems that nobody wants to come to my house anymore...). Sorry
this is long, so thanks in advance for reading through!!

Closer examination shows that the 403 Errors I am catching are preflight
requests from the browser.  My attempts at a fix include setting the
Access-Control-Allow-Origin="*" both in apache and in tomcat. Neither of
which helped.  What is strange is that the preflight seems to be a result
of a simple GET request, which I think should not trigger such a request,
but I'm a little out of my depth with this.  Here is the complete request
info (from Chrome in this case):


   - *General*
  - *Request URL: *https://udc-prd.lib.umn.edu/server/api/authn/status
  - *Request Method: *OPTIONS
  - *Status Code: *403 403
  - *Remote Address: *128.101.65.121:443
  - *Referrer Policy: *no-referrer-when-downgrade
   - *Response Headers*view source
  - *Cache-Control: *no-cache, no-store, max-age=0, must-revalidate
  - *Connection: *Keep-Alive
  - *Date: *Fri, 10 Jul 2020 13:39:00 GMT
  - *Expires: *0
  - *Keep-Alive: *timeout=5, max=100
  - *Pragma: *no-cache
  - *Server: *Apache/2.4.6 (Red Hat Enterprise Linux)
  OpenSSL/1.0.2k-fips mod_jk/1.2.48
  - *Strict-Transport-Security: *max-age=31536000 ; includeSubDomains
  - *Transfer-Encoding: *chunked
  - *Vary: *
  Origin,Access-Control-Request-Method,Access-Control-Request-Headers
  - *X-Content-Type-Options: *nosniff
  - *X-Frame-Options: *DENY
  - *X-XSS-Protection: *1; mode=block
   - *Request Headers*view source
  - *Accept: **/*
  - *Accept-Encoding: *gzip, deflate, br
  - *Accept-Language: *en-US,en;q=0.9
  - *Access-Control-Request-Headers: *content-type
  - *Access-Control-Request-Method: *GET
  - *Connection: *keep-alive
  - *Host: *udc-prd.lib.umn.edu
  - *Origin: *https://udc-dev.lib.umn.edu:3000
  - *Referer: *https://udc-dev.lib.umn.edu:3000/
  - *Sec-Fetch-Dest: *empty
  - *Sec-Fetch-Mode: *cors
  - *Sec-Fetch-Site: *same-site
  -
  *User-Agent: *Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5)
  AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36

and a snippet from the javascript console for the same request:

Access to XMLHttpRequest at '
https://udc-prd.lib.umn.edu/server/api/authn/status' from origin '
https://udc-dev.lib.umn.edu:3000' has been blocked by CORS policy: Response
to preflight request doesn't pass access control check: No
'Access-Control-Allow-Origin' header is present on the requested resource.


zone.js.pre-build-optimizer.js:3372 GET
https://udc-prd.lib.umn.edu/server/api/authn/status net::ERR_FAILED


And this is the result in my apache logs:

10.21.37.74 - - [10/Jul/2020:08:39:00 -0500] "OPTIONS
/server/api/authn/status HTTP/1.1" 403 20


With an identical log entry on the tomcat side:

10.21.37.74 - - [10/Jul/2020:08:39:00 -0500] "OPTIONS
/server/api/authn/status HTTP/1.1" 403 20




On Thu, Jul 9, 2020 at 7:08 AM Bill Tantzen  wrote:

> Sorry for cross posting, but autocomplete tricked me into posting this on
> dspace-devel...  Anyway
>
> Out of the box, my angular client works fine against the test REST
> server.  However, when I run the client against my own REST server, every
> OPTIONS request generates a response code 403. (which usually results in
> the client hanging).
>
> I think this is a problem with either my tomcat or my apache setup, but I
> have not been able to track down the cause.  (it's probably tomcat, because
> the response is initially returned there).  In terms of configuration, both
> are pretty vanilla.
>
> One interesting side note: any identical request sent via Postman succeeds
> with response code 200!  A problem with headers perhaps?
>
> I have apache version: Apache/2.4.6 (Red Hat Enterprise Linux),
> tomcat version 9.0.34
> openjdk 11.07
>
> Example errors from the java console:
> [Error] XMLHttpRequest cannot load
>   https://.lib.umn.edu/server/api/statistics/viewevents
>  due to access
> control checks.
> [Log] Error:  – t (main.07d9b2d02aa94962fe83.js, line 1)
> t
> [Error] Object
> [Error] Failed to load resource: Preflight response is not successful
> (viewevents, line 0)
>
> And this is repeated for each and every OPTIONS request.
>
> Any ideas?
> Thanks,
> Bill
>
> --
> Human wheels spin round and round
> While the clock keeps the pace... -- John Mellencamp
> 
> Bill TantzenUnivers

[dspace-tech] problems with dspace-angular-beta3

2020-07-09 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Sorry for cross posting, but autocomplete tricked me into posting this on
dspace-devel...  Anyway

Out of the box, my angular client works fine against the test REST server.
However, when I run the client against my own REST server, every OPTIONS
request generates a response code 403. (which usually results in the client
hanging).

I think this is a problem with either my tomcat or my apache setup, but I
have not been able to track down the cause.  (it's probably tomcat, because
the response is initially returned there).  In terms of configuration, both
are pretty vanilla.

One interesting side note: any identical request sent via Postman succeeds
with response code 200!  A problem with headers perhaps?

I have apache version: Apache/2.4.6 (Red Hat Enterprise Linux),
tomcat version 9.0.34
openjdk 11.07

Example errors from the java console:
[Error] XMLHttpRequest cannot load
  https://.lib.umn.edu/server/api/statistics/viewevents
 due to access
control checks.
[Log] Error:  – t (main.07d9b2d02aa94962fe83.js, line 1)
t
[Error] Object
[Error] Failed to load resource: Preflight response is not successful
(viewevents, line 0)

And this is repeated for each and every OPTIONS request.

Any ideas?
Thanks,
Bill

-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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/CADgrb7HG4mjp1zgFm2tHejdwAS4B1QnALH6Lumb5aGrHhMu91g%40mail.gmail.com.


Re: [dspace-tech] Re: metadata element="identifier" qualifier="handle" is missing in pageMeta or DRI

2020-05-20 Thread &#x27;Bill Tantzen&#x27; via DSpace Technical Support
Well, I can't specifically answer your question, but I can verify that this
element exists in v5.10 in the !

On Tue, May 19, 2020 at 5:46 PM euler  wrote:

> Dear All,
>
> I would like to reiterate my query about why there is no metadata
> element="identifier" qualifier="handle" in the pageMeta of my items. I got
> a response from Paul, thanks Paul but it did not address why it is missing.
> I am aware that I can select metadata values from the 'dim:field' of the
> item's metadata mets.xml. What I would really like to know is why it is
> missing and how to make the metadata element="identifier"
> qualifier="handle" appear in the pageMeta. I assumed that this is supposed
> to exist because it is being referenced in the global-variables.xsl in
> Mirage theme.
>
> Even in my local instance using the default 6.3 version without any
> customizations, it is still missing. I looked for many repositories of
> others to see if the element="identifier" qualifier="handle" is also
> missing and I found an example here:
> https://iris.paho.org/DRI/handle/10665.2/52154 although it is using the
> 6.4-SNAPSHOT version.
>
> If anybody could shed light on this and how to resolve and what to look
> for would be really appreciated.
>
> Thanks in advance!
> Euler
>
> On Thursday, January 16, 2020 at 5:46:27 PM UTC+8, euler wrote:
>>
>> Dear All,
>>
>> I wonder, if I view the DRI of an item, there is no metadata
>> element="identifier" qualifier="handle" in the DRI
>> or //dri:meta/dri:pageMeta/dri:metadata. I asked because I created a
>> variable name identifier_handle in the global-variables.xsl which will be
>> used by Altmetrics template in item-view.xsl.
>>
>> 
>> >
>> select='//dri:meta/dri:pageMeta/dri:metadata[@element="citation_doi"]'/>
>> >
>> select='//dri:meta/dri:pageMeta/dri:metadata[@element="identifier" and
>> @qualifier="handle"]'/>
>>
>> Below is a snippet of my altmetrics template where the variable
>> identifier_handle is called:
>>
>> 
>> 
>> > select='$identifier_doi'/>
>> 
>> 
>> > select='$identifier_handle'/>
>> 
>> 
>>
>> Since there is no value for identifier_handle because it is missing in
>> dri:pageMeta/dri:metadata, the Altmetrics badge is not shown. Altmetrics is
>> shown for items with doi by the way since it is present in pageMeta.
>>
>> My question now is how can I make the handle appear in pageMeta and what
>> file should I modify? I am using DSpace version 6.3 Mirage2. I did not edit
>> any *.java files in this repository, since when I tried to look where
>> pageMeta was generated, I assumed that it is generated by ItemViewer.java
>> (please correct me if I'm wrong) which I did not modify.
>>
>> In other repositories that I am working on (with almost the exact
>> customizations), the handle is there in pageMeta.
>>
>> Thanks in advance!
>>
> --
> 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/fbc404f6-702c-492f-acd8-319e76918aff%40googlegroups.com
> 
> .
>


-- 
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp

Bill TantzenUniversity of Minnesota Libraries
612-626-9949 (U of M)612-325-1777 (cell)

-- 
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/CADgrb7ETyno4PrnbPeaSvQuZ9i%3DsgZBiAZWnkSbvLPoTNsbFAg%40mail.gmail.com.