Hi all,
I’m drafting a project proposal for a translation of the DSpace interface
(messages.xml files) into Te Reo Māori and making this available to the DSpace
community. I understand the translation should be published under the BSD
licence, but does copyright also need to be assigned to
Brilliant, thanks very much!
Deborah
From: ivan.ma...@gmail.com [mailto:ivan.ma...@gmail.com] On Behalf Of helix84
Sent: Monday, 3 October 2016 11:11 a.m.
To: Fitchett, Deborah <deborah.fitch...@lincoln.ac.nz>
Cc: dspace-community@googlegroups.com
Subject: Re: [dspace-community] Cop
This depends a lot on the things that are important to you, but from my
experience (noting we’re still on DSpace 5.x):
· The DSpace community is much stronger; I don’t know to what extent
Equella is being maintained by its community since Pearson open-sourced it, so
there’s some risk
Hi Angélica,
The out-of-the-box controlled vocabulary support is done using
/dspace/webapps/xmlui/static/js/vocabulary-support.js (which refers to separate
files for the actual controlled vocabulary).
I’m not sure it’s possible (or at least not easy, given cross-site scripting
issues) to get
Another not-lawyer here. ☺
Essentially, the person who owns the copyright (usually but not always the
author) has the right to determine whether, how, and by whom copies of the work
(either print or electronic) can be made.
If the copyright holder gives someone permission to make copies,
.
Deborah
From: Edoneia Sampaio da Silva Miranda
Sent: Saturday, 1 December 2018 3:27 AM
To: Fitchett, Deborah
Cc: joseph.rog...@unical.it; susan.matvey...@wichita.edu;
abdullrahman.hega...@gmail.com; dspace-community@googlegroups.com
Subject: Re: [dspace-community] licences and copyright
Hi!
I
The easiest way I can think of would be to export the metadata for each of your
communities, open it in Excel, find the metadata field you’re interested in
(listed along the top row), then use Excel’s functionality to filter that
column by blanks.
Instructions for exporting metadata in eg
Hello, I’d start by reading the documentation about the SOLR statistics – the
latest version is at https://wiki.lyrasis.org/display/DSDOC7x/SOLR+Statistics
but if you’re on an older version of DSpace note the link at the top goes to
other versions of the documentation.
Deborah
From:
Kia ora,
It sounds like you’ve tried a lot of things on the Primo side. What about
modifying the OAI feed on the DSpace side?
There are two options for doing this:
1. If you don’t think any other harvesters would want all the different
dates, you could simply edit the crosswalk so that
Kia ora koutou,
We have a bunch of files that we need to keep for auditing purposes – in some
cases to do with copyright permissions, in others proof that a conference did
actually take place – but we don’t want the files or even the filenames to be
visible to users as the filenames weren’t
this issue will make the top of our list, but if it
does I’ll keep you in the loop.
Deborah
From: Daryl M. Grenz
Sent: Tuesday, August 29, 2023 2:15 AM
To: Fitchett, Deborah
Cc: dspace-community@googlegroups.com
Subject: RE: 2-step workflow display in DSpace 7
Caution: This email originated
You’re probably looking for
https://wiki.lyrasis.org/display/DSDOC7x/Configuration+Reference#ConfigurationReference-HidingMetadata
Deborah
From: dspace-community@googlegroups.com On
Behalf Of Stephen Brush
Sent: Thursday, November 9, 2023 4:53 AM
To: DSpace Community
Subject:
Kia ora koutou,
I’m working on an early draft of an author name change policy for our
repository. One of the less obvious places author names are included is the
dc.description.provenance field generated when they first submit the item
(submitter name and email address). If the file name
Editing the submission form will allow people submitting the item to add data
to those fields. If the data is already in those fields and you want to change
how it displays on the search results page then you probably want to edit the
theme’s … /xsl/aspect/artifactbrowser/item-list.xsl page.
Nothing can completely prevent it. Putting it behind a login or not digitising
it at all would make it harder, but then it’s not so available to the general
public at all which is counterproductive. Theoretically some kind of DRM might
help but I don’t believe that’s a feature of DSpace.
So it
You need to customise your submission form as well to add input fields for the
new fields. How you do this depends on your DSpace version eg
5.x - https://wiki.lyrasis.org/display/DSDOC5x/Submission+User+Interface
7.x - https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface
Deborah
I had a vague feeling this functionality isn’t in DSpace 7 unless it’s been
added to one of the later versions.
If you don’t find existing functionality allowing it, then you could ‘hack’ it
by adding the month number to the start of the collection name. Eg “01
January”, “02 February” etc.
if it is present.
Regards,
Chandrika Hebbar
On Thursday, July 27, 2023 at 5:12:55 AM UTC+5:30 Fitchett, Deborah wrote:
Kia ora,
No, this can’t be specified in the metadata registry. The qualifier is more to
clarify to humans what kind of data is intended eg dc.contributor.author vs
Kia ora,
No, this can’t be specified in the metadata registry. The qualifier is more to
clarify to humans what kind of data is intended eg dc.contributor.author vs
dc.contributor.editor or dc.identifier.isbn vs dc.identifier.doi, but there’s
no validation performed on it.
You can define the
Kia ora koutou,
We have a two-step approval process:
* “Check submission” (workflow_step_2) lets curators reject, edit, or
approve
* “Final check” (workflow_step_3) lets curators edit or approve
Curators often want to choose tasks depending on which stage it’s at, so they
can work
Kia ora koutou,
We’ll be upgrading from 5.8 to 7.4-ish soon, and I’m starting to plan what
staff training will be needed, especially for staff who edit and approve
incoming submissions (including moving and mapping to different collections,
applying embargoes, managing bitstream permissions
For us, the external harvesters we care about all use OAI-PMH. So for that
purpose, we can use any schema/combination of schemas we like in DSpace itself
(we’ve got a mix of dc, thesis, a schema from our CRIS, and a local schema for
miscellaneous fields we wanted to store…), we just transform
22 matches
Mail list logo
