On Wednesday, August 22, 2018 at 7:33:49 PM UTC+5:30, Sneha wrote:
>
> Hi,
>
> My dspace service was working perfectly. However, some issues with my IBM
> server occurred which was resolved. Now all my services are working
> perfectly except xmlui interface (503 Service Unavailable). Other
Hello.
Thank you for the answer! I hope one day we can configure all of email
notifications.
среда, 22 августа 2018 г., 17:45:51 UTC+3 пользователь Tim Donohue написал:
>
> Hello,
>
> Unfortunately, at this time, you can only turn off the entire mail server,
> and not individual notifications.
Hi all,
I finally got around to trying this out on our dev server: updated the “handle”
table to point two different handles to the one resource_id (and none to the
withdrawn resource_id). It seemed in the first instance to work – following the
links did what I expected.
Then I tried running
In the last month, the DSpace project has created Docker images for the 4
active branches of DSpace and DSpace-angular. These images will be
automatically rebuilt as changes are merged onto each branch.
The August 28 DSpace Developer Show and Tell will be a demonstration
of the DSpace
Docker
And further to that (having tripped over this myself about five minutes
ago) - the url property in that file doesn't carry over to the
collection.url and servicedocument.url properties, so if you use a non
standard "url" value then (as stated in the comments of the file) you'll
have to adjust
Hi,
check what you have configured as the service document URL - probably in
[dspace]/config/modules/swordv2-server.cfg. It's the first property in that
file "url". The default is {dspace.url}/swordv2 and the base URL you use in
your sword deposit must match that exactly.
cheers,
Andrea
On Thu,
We're attempting to enable the SWORDv2 endpoint in our DSpace instance for
use in a DSpace-Symplectic Elements Repository Tools 2 integration. The
service document gives this error: "Unable to recognise URL as a valid
service document:..."
Does anyone have any insight into what could be
I was happy to see the return of ORCID in 6.3, however I'm experiencing
some odd behavior which I think may be a bug.
Using the Lookup button, the initial interaction with the OCRID v2 API
seems to work great
[image: orcid_bug_01.png]
A match is found, I can see the ORCID and I can add
Hello,
Whether you upgrade is really a local decision. It recent years, DSpace
Developers have put significant effort into ensuring your *data*
(files/database) upgrades automatically.
So, moving your data to the latest version of DSpace is vastly simplified
(and usually completely automated,
Hello Habibi,
Here's the metadata schemas/fields that come out of the box with DSpace:
https://wiki.duraspace.org/display/DSDOC6x/Metadata+and+Bitstream+Format+Registries
You can add custom schemas/fields, but they must be of the same general
format as Qualified Dublin Core. That format is
Hello,
Unfortunately, at this time, you can only turn off the entire mail server,
and not individual notifications.
If you want DSpace to no longer send any emails, you can uncomment this
configuration (in dspace.cfg or local.cfg) and set it to "true"
mail.server.disabled = false
Here's where
Hi there
Running DSpace 6.2.
After deleting a number of items using the REST API
DELETE {rest_url}/items/{item id} - Delete item.
Some of which were in a collection with restricted read access.
I find that neither it's parent community nor collections can be viewed (read)
unless I am
Hello Abhishek,
Unfortunately, DSpace doesn't support cascading dropdowns out-of-the-box.
You'd likely need to look for a third-party library (perhaps a Javascript
library) to help you achieve this sort of customization.
Hopefully, if others have done this locally they will respond to this
Hi Evgeni,
I *think* that's why DS-3979 exists...cause it's a bug. I admit, though, I
haven't had a chance to review that ticket or the PR associated myself.
So, I'd recommend commenting directly on the ticket or PR and ask how to
reproduce this problem. It might clarify to you (and me) what the
Thank you Tim,
I really did not know this. But still I don't see why change of the
filename or the format should affect the authorization policy of the
bitstream.
Best regards
Evgeni
On Wednesday, August 22, 2018 at 5:09:04 PM UTC+3, Tim Donohue wrote:
>
> Hi Evgeni,
>
> This DS-3979 issue is
Hi Evgeni,
This DS-3979 issue is referring to editing a bitstream's *metadata* (not
the actual file associated with the bitstream). A bitstream's metadata is
editable from the UI, but the file itself is not editable (you can only
upload a new file).
Here's how you get to the edit a bitstream's
Hi,
My dspace service was working perfectly. However, some issues with my IBM
server occurred which was resolved. Now all my services are working
perfectly except xmlui interface (503 Service Unavailable). Other services
are configured on 8080 and they work perfectly. However, the xmlui
Hi all.
I have noticed that when an author is added using the ORCID lookup
during the submission process (and choosing an Orcid author), a
confidence is attributed to that metadata entry (600), but if one edits
the metadata after submission and adds an author (also using the ORCID
lookup),
In issue DS-3979 I noticed a comment:
Chris Herron (Atmire) added a comment - 10/Aug/18 11:52 AM
Without this in place, if DEFAULT_ITEM_READ is Anonymous and
DEFAULT_BITSTREAM_READ is Administrator, then any edit to a bitstream will
add an Anonymous READ policy, making the bitstream public
Hi Freddy
either a SIP export (and then Import) or an AIP export (small
differences in the behaviour), followed by an import into the new
repository wold serve
See in
https://wiki.duraspace.org/display/DSDOC6x/Exchanging+Content+Between+Repositories
1. Transferring Content via
Hello friends, I need to export a collection with more than 2000 items and
their files (bitstream), and then import into another repository, what
would the procedure be?. I have administrator profile in both repositories
(origin and destination)
Freddy
--
All messages to this mailing list
21 matches
Mail list logo
