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 ORI
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,
Sorry, just wanted to bump this up to see if anybody has any experience
with this configuration?
Thanks for looking,
~~Bill
On Friday, October 28, 2022 at 9:01:38 AM UTC-5 tant...@umn.edu wrote:
> In DSpace 7.4, I would like to NOT display the Access Conditions step on
> my "Edit bitstream" for
That's it exactly! Thanks!
On Wednesday, November 2, 2022 at 12:34:20 PM UTC-5 Tim Donohue wrote:
> Hi Bill,
>
> The "access conditions" that appear in the Submission Form after you click
> Edit on a file are configured in the new "access-conditions.xml" Spring
> configuration file. See the d
Aha, Got it:
https://github.com/DSpace/dspace-angular/blob/main/src/app/shared/pagination/pagination-component-options.model.ts#L25
Correct?
Cheers,
~~Bill
On Wednesday, November 9, 2022 at 2:09:05 PM UTC-6 tant...@umn.edu wrote:
> In DSpace 7, is it possible to adjust the choices and default va
That's helpful, and the new style is actually more predictable, however, in
my instance when I click on a bitstream link I am redirected to a new url
that looks like a REST endpoint, for example
https://xxx.xxx.xxx/server/api/core/bitstreams/12ea09a7-d9aa-4666-9a51-aef6358351a5/content
It would
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:
> Greeting
I can confirm the same problem.
The dspace logs offer no clue -- everything looks normal there.
In the javascript console (and in the apache logs) the failing request is
the same:
https://yyy.xxx.edu/server/api/core/bitstreams/fe32d1f1-5e85-43b8-85d9-471b113d504f/content
This is the correct RE
Are we talking about 2 different issues here? In my case, I can upload the
thumbnail, but I cannot display it. I have confirmed that the image is
there on disk, and it is present in the database. However, the actual
display of the image fails with a 400 - Bad Request error.
On Wednesday, Jan
I have traced my problem to the fact that all community/collection logos
have a bitstream format of Unknown, (and there is no metadata for the
bitstream, although this has no effect on the error). If I update the
bitstream_format_id to it's correct value, the logo displays.
I am on version 7.6
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 sub
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 erro
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
All,
Despite the stated requirements for node in the documentation ("Node.js
(v16.x or v18.x)"), I am getting the following error when attempting to
build the version 7.6.3 frontend:
$ yarn install
yarn install v1.22.22
[1/4] Resolving packages...
[2/4] Fetching packages...
error isbot@5.1.22: T
14 matches
Mail list logo
