[dspace-community] Copyright for translations

[Fitchett, Deborah]

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 Duraspace as I 
understand it does for code contributions?

Thanks very much,

Deborah Fitchett
Senior Advisor, Digital Access
Library, Teaching and Learning

p +64 3 423 0358
e deborah.fitch...@lincoln.ac.nz | w 
ltl.lincoln.ac.nz

Lincoln University, Te Whare Wānaka o Aoraki
New Zealand's specialist land-based university



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

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-community@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-community] Copyright for translations

[Fitchett, Deborah]

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] Copyright for translations

No, we do not require a CLA (Contributor License Agreement) for neither code 
nor other contributions. In fact, that the license headers contain DuraSpace is 
just a historic artifact of the license that is not technically true - all 
contributors retain their copyright, they only grant the license.

So just submit your pull request or send the file, no other formalities are 
required.


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


On Sun, Oct 2, 2016 at 11:14 PM, Fitchett, Deborah 
<deborah.fitch...@lincoln.ac.nz<mailto:deborah.fitch...@lincoln.ac.nz>> wrote:
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 Duraspace as I 
understand it does for code contributions?

Thanks very much,

Deborah Fitchett
Senior Advisor, Digital Access
Library, Teaching and Learning

p +64 3 423 0358<tel:%2B64%203%20423%200358>
e deborah.fitch...@lincoln.ac.nz<mailto:deborah.fitch...@lincoln.ac.nz> | w 
ltl.lincoln.ac.nz<http://library.lincoln.ac.nz/>

Lincoln University, Te Whare Wānaka o Aoraki
New Zealand's specialist land-based university



P Please consider the environment before you print this email.
"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."
--
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com<mailto:dspace-community+unsubscr...@googlegroups.com>.
To post to this group, send email to 
dspace-community@googlegroups.com<mailto:dspace-community@googlegroups.com>.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-community@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-community] Equella vs DSpace

[Fitchett, Deborah]

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

· Equella does quite a bit more than just store objects – eg it can 
also let you manage copyright reporting, it can integrate with learning 
management systems like Moodle, etc and deal with activating/deactivating 
access on a course-by-course basis

· That said, because Equella’s trying to do a lot of things I’ve never 
felt it does any of them superbly. Fairly competently, sure.

Personally, if all I wanted was a place that let an admin or team or admins 
upload content to be available to certain groups and/or the public, I’d almost 
certainly go for DSpace. But if you need some of the advanced features around 
copyright reporting, course management, etc, then Equella may be worth 
considering.

Deborah

From: dspace-community@googlegroups.com  On 
Behalf Of alejopachonsant...@gmail.com
Sent: Wednesday, 9 May 2018 1:12 AM
To: DSpace Community 
Subject: [dspace-community] Equella vs DSpace

Hi,

I would like to implement a learning resources repository but I want to know if 
you can give me your opinion about the Equella repository and its differences 
with DSpace 6.2.

Thanks for your comments
--
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-community@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

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

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-community@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-community] controlled vocabulary

[Fitchett, Deborah]

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 that javascript to connect directly to your external catalog. 
But maybe there’s some indirect way you can come up with.

Of course if the catalog doesn’t get modified too often then you might be able 
to periodically download a copy manually into 
/dspace/config/controlled-vocabularies/ in the right format.

Deborah

From: dspace-community@googlegroups.com 
[mailto:dspace-community@googlegroups.com] On Behalf Of Angélica Landaverde
Sent: Tuesday, 30 January 2018 12:52 p.m.
To: DSpace Community 
Subject: [dspace-community] controlled vocabulary


Hi





I am trying to use controlled vocabulary through a catalog that is consumed 
with rest services with user and password.

I do not know how to do this. What files should I to add or modify?

Someone knows how I can do this?





Thank you for your attention.
--
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-community@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

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

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-community@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-community] licences and copyright

[Fitchett, Deborah]

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, that’s called 
a license. Eg for something to be put on a repository, the copyright holder has 
to grant permission (ie a license) to the repository to make a copy. If they’re 
only granting permission to the repository and not to anyone else then it’s 
appropriate to display “all rights reserved”.

But the copyright holder can choose to grant other licenses, like a Creative 
Commons license. If they did that, they should display the CC license 
information instead of “all rights reserved” because they’re no longer 
reserving all rights – they’re granting some rights, and reserving some rights, 
and these are described by the CC license.

It’s always easy for a copyright holder to grant new permissions – so if 
something you own is “all rights reserved” you can change that to a CC license. 
But it’s harder to take away permissions, so if it already has a CC license it 
would be difficult or maybe impossible to change it back to “all rights 
reserved”.

(More information about Creative Commons licenses is at 
https://creativecommons.org/licenses/ - the bottom of the page links to 
translations in other languages.)

Deborah

From: dspace-community@googlegroups.com  On 
Behalf Of Joseph Frank Rogani
Sent: Friday, 30 November 2018 4:54 AM
To: susan.matvey...@wichita.edu
Cc: abdullrahman.hega...@gmail.com; dspace-community@googlegroups.com
Subject: Re: [dspace-community] licences and copyright

Hello again,
I am not a lawyer either, but I agree there is a contradiction.

It also depends on what kind of document you are depositing: if it is a Ph.D., 
say, unless it has embargoes or patent restrictions, it should be open, though 
respecting citations in case of use. What I actually meant is that Abdulrahman 
should go for a CCL, leaving the author free to decide (is he the author?) 
which permissions to give for the use of the item.
I don't know if you agree on this.

Kind regards
Joseph

--
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-community@googlegroups.com.
Visit this group at 
https://groups.google.com/group/dspace-community.
For more options, visit 
https://groups.google.com/d/optout.



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

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-community@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-community] licences and copyright

[Fitchett, Deborah]

Hi,

This probably involves editing your theme to display the Creative Commons 
information stored in your metadata. Can you tell us what version of DSpace 
you’re on (and especially JSPUI or XMLUI) and someone may be able to point to 
some documentation for getting started editing the theme.

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 was able to understand how this issue works. I confess I was a bit lost on 
the subject. Now, I need to understand, for example how CCL inserts into the 
repository. For example, here in our authorization term has a part that says: I 
authorize the Library System of the Federal University of Rondônia to make 
available

the work in the Institutional Repository free of charge, according to the 
public license Creative

Commons License 4.0 International by me declared under the following 
conditions. If there is

publisher's interest and have the options:

Do you allow commercial use of your work?

( ) Yes No

Allow changes to your work?

( ) yea

() yes counting others share for the same license

( ) not

The work remains protected by Copyright and / or other applicable laws. Any use 
of the

work other than that authorized under this license or by copyright law is 
prohibited.



But in the repository for all publications only the message appears: Items in 
the repository are protected by copyright, with all rights reserved, except 
where indicated otherwise.



Forgive me, I am now entering this universe and trying to understand how it 
works.

This discourse is being of great value.

Em qui, 29 de nov de 2018 às 18:24, Fitchett, Deborah 
mailto:deborah.fitch...@lincoln.ac.nz>> 
escreveu:
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, that’s called 
a license. Eg for something to be put on a repository, the copyright holder has 
to grant permission (ie a license) to the repository to make a copy. If they’re 
only granting permission to the repository and not to anyone else then it’s 
appropriate to display “all rights reserved”.

But the copyright holder can choose to grant other licenses, like a Creative 
Commons license. If they did that, they should display the CC license 
information instead of “all rights reserved” because they’re no longer 
reserving all rights – they’re granting some rights, and reserving some rights, 
and these are described by the CC license.

It’s always easy for a copyright holder to grant new permissions – so if 
something you own is “all rights reserved” you can change that to a CC license. 
But it’s harder to take away permissions, so if it already has a CC license it 
would be difficult or maybe impossible to change it back to “all rights 
reserved”.

(More information about Creative Commons licenses is at 
https://creativecommons.org/licenses/<https://creativecommons.org/licenses/> - 
the bottom of the page links to translations in other languages.)

Deborah

From: 
dspace-community@googlegroups.com<mailto:dspace-community@googlegroups.com> 
mailto:dspace-community@googlegroups.com>> 
On Behalf Of Joseph Frank Rogani
Sent: Friday, 30 November 2018 4:54 AM
To: susan.matvey...@wichita.edu<mailto:susan.matvey...@wichita.edu>
Cc: abdullrahman.hega...@gmail.com<mailto:abdullrahman.hega...@gmail.com>; 
dspace-community@googlegroups.com<mailto:dspace-community@googlegroups.com>
Subject: Re: [dspace-community] licences and copyright

Hello again,
I am not a lawyer either, but I agree there is a contradiction.

It also depends on what kind of document you are depositing: if it is a Ph.D., 
say, unless it has embargoes or patent restrictions, it should be open, though 
respecting citations in case of use. What I actually meant is that Abdulrahman 
should go for a CCL, leaving the author free to decide (is he the author?) 
which permissions to give for the use of the item.
I don't know if you agree on this.

Kind regards
Joseph

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: 
https://duraspace.org/about/policies/code-of-conduct/<https://duraspace.org/about/policies/code-of-conduct/>
---
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com<mailto:dspace-community+unsubscr...@googlegroups.com>.
To post to this group, send email to 
dspace-community@googlegroups.com<ma

RE: [dspace-community] Metadata finding

[Fitchett, Deborah]

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 version 5.* are at 
https://wiki.duraspace.org/display/DSDOC5x/Batch+Metadata+Editing#BatchMetadataEditing-WebInterfaceExport

(If you have a lot of communities so this would be onerous, and you’re 
confident with postgres and the database structure, you could alternatively run 
a query directly against the database. It’d be a fairly complex one though; I 
think in most cases using the export option would be easier.)

Deborah

From: dspace-community@googlegroups.com  On 
Behalf Of Javier Fernandez
Sent: Thursday, 14 February 2019 8:40 AM
To: DSpace Community 
Subject: [dspace-community] Metadata finding

Hello, people.

I need help. I'm having problems with our repository metadata harvesting. There 
are some items that are missing some metatada fields. What I need help with is 
the following: how do I find (other than checking each item one by one) which 
items lack a certain metadata field?

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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to 
dspace-community@googlegroups.com.
Visit this group at 
https://groups.google.com/group/dspace-community.
For more options, visit 
https://groups.google.com/d/optout.



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

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-community@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

RE: [dspace-community] Statistics

[Fitchett, Deborah]

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: dspace-community@googlegroups.com  On 
Behalf Of Nkululeko Magwaza
Sent: Monday, 16 August 2021 11:57 PM
To: DSpace Community 
Subject: [dspace-community] Statistics

Dear Colleagues

I hope you are still well and safe,

How is statistics counted on DSpace, and how can statistics on DSpace for 
example if we want statistics from 2017 to 2021 can be done.

Looking forward to your kind replies,

Thank You
Nkululeko Magwaza


--
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/CAEhQ1FEhe4%3DVEmDRGMpqU29Q%3Dhh%2BamBOLnkhF6k%3DzwFoqtbSiA%40mail.gmail.com.



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

-- 
All messages to this mailing list should adhere to the 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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/SYCPR01MB5037CCD6E8FD94D157C228A9C5FE9%40SYCPR01MB5037.ausprd01.prod.outlook.com.

RE: [dspace-community] Pulling dc.date.issued into Alma

[Fitchett, Deborah]

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 instead of crosswalking all 
the dc.date.* options, it only uses dc.date.issued

  2.  Alternatively you could create a separate “context” so that most 
harvesters use your default context but Primo uses a dedicated one with only 
the data you want there. Then you can leave the crosswalk alone for other 
harvesters, but edit the crosswalk for Primo.

Eg we have:
“request” 
https://researcharchive.lincoln.ac.nz/dspace-oai/request?verb=ListSets as our 
default context
“catalog” 
https://researcharchive.lincoln.ac.nz/dspace-oai/catalog?verb=ListSets as the 
context for harvesting into Primo

(At the moment our crosswalks are practically the same, For Reasons, but the 
option is there.  )

See 
https://wiki.lyrasis.org/display/DSDOC7x/OAI+2.0+Server#OAI2.0Server-AdvancedConfiguration
 for documentation.

Deborah

From: dspace-community@googlegroups.com  On 
Behalf Of Yvonne
Sent: Friday, October 13, 2023 5:06 AM
To: DSpace Community 
Subject: [dspace-community] Pulling dc.date.issued into Alma

Caution: This email originated from outside our organisation. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Hello DSpace Community,

The State University of New York--64 campuses--use ExLibris's Alma/Primo VE. 
Alma has a method to import digital collections from the major players in 
repositories, including, of course, DSpace.

We have been working to import collections from DSpace so they are discoverable 
in Primo VE, but we have not found a way to get the dc.date.issued to display 
in the item records. No matter what we have tried, dc.date.accessioned is the 
displayed field. As with other Dublin Core fields, precedence is given to 
alphabetical order, and unfortunately the field we want is at the bottom of the 
list.

Has anyone out there successfully imported DSpace collections into Alma with 
dc.date.issued being displayed in the item record?

We have tried normalization rules, regex, and the sorting function in the 
import profiles, and none have made any difference in the result.

Many thanks for your kind attention.
Yvonne Kester
SUNY Library Services
--
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/CAKZKP2At4WPDVAobWvf7OiPQ5PNuATDAtAtOts-5tmY%3DnHcneg%40mail.gmail.com.



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

-- 
All messages to this mailing list should adhere to the 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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/ME3PR01MB7524EA5D9A87C5E535F5D2C4C5D2A%40ME3PR01MB7524.ausprd01.prod.outlook.com.

[dspace-community] Hiding "audit" bitstreams / creating new bundles

[Fitchett, Deborah]

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 written for public consumption. I 
don’t think any would *actually* breach privacy, but – it’s not ideal.

In DSpace 5.8 we left them in ORIGINAL, manually edited the auth policy for 
these bitstreams to restrict access to Admin-only, and I did some messy hacking 
with xsl to hide admin-only items from display. But we’re needing to use DSpace 
7.* in a more out-of-the-box way.

We can’t restrict the bundle ORIGINAL as a whole because there are other files 
that are open access so need to remain visible.

Options I can see:

  *   If the bitstream is in the ORIGINAL bundle (our practice to date) then 
the filename displays on the item simple view page. This is the default 
behaviour I’m trying to avoid.
  *   If we add the bitstream to the LICENSE bundle instead then the filename 
doesn’t appear on the simple view page but does appear in the expanded view. 
This is a slight improvement but starts being a bit of an abuse of the 
“LICENSE” terminology and still isn’t ideal.
  *   In the Edit > Bitstreams > Upload I see the option to create a new 
bundle. If I create a bundle AUDIT and upload a file to it, this bitstream 
doesn’t appear anywhere publically, which is excellent. (It does seem to be 
created with an Anonymous READ policy so we’d still want to edit this to be 
safe.) OTOH I also don’t see the bitstream (or the AUDIT bundle itself) appear 
in Edit > Status > Authorisations. So I’m not sure if this is the most robust 
approach.

Are there any unobvious ramifications of creating a new bundle in this last way 
/ for this purpose?

Is it a bug that a newly created bundle isn’t visible in Edit > Status > 
Authorisations? (I can log this if so.)

Are there any ways to move a bitstream from one bundle to another so that we 
can fix up items retrospectively? So far my best guess is either

  *   to mess in the database – but I’ve only got direct access to that for a 
couple more days and we have no way to programmatically identify the affected 
bitstreams, so this isn’t feasible; or
  *   to download each one from ORIGINAL, delete it, then upload it to LICENSE 
or AUDIT, which would obviously be painfully timeconsuming.

Or does anyone have any other better ideas for how to deal with this problem?

Deborah
––
Deborah Fitchett (she/her) MLIS, RLIANZA
Associate University Librarian, Digital Scholarship

––
Learning, Teaching and Library – Te Whare Pūrākau
PO Box 85064, Lincoln University
Lincoln 7647, Christchurch, New Zealand
+64 3 423 0358
deborah.fitch...@lincoln.ac.nz
ltl.lincoln.ac.nz

––
Lincoln University
Te Whare Wānaka o Aoraki
––




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

-- 
All messages to this mailing list should adhere to the 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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/ME3PR01MB75246FB6CC3361252A8E6145C515A%40ME3PR01MB7524.ausprd01.prod.outlook.com.

[dspace-community] RE: 2-step workflow display in DSpace 7

[Fitchett, Deborah]

Kia ora Daryl,

Thanks – I eventually did find that issue on the github project site but it 
looks like it is a matter of waiting for someone to volunteer to fix it. 
Unfortunately I’m getting the strong impression (from general silence on the 
mailing list, on that github issue, and from discussions with Atmire who’ll be 
hosting our upgraded site) that there aren’t any real workarounds.

My own team are going to be keeping their own spreadsheet to track what stage 
each item is in, which is less than ideal, and once our upgrade settles down 
I’ll be discussing with them whether we actually need to keep the two-step 
process.

Following the upgrade I’ll also be collating a list of the various bugs / 
desirable features we’d like to be addressed, and seeing if we’ve got budget to 
pay for development for any of these (aiming to contribute to the main codebase 
of course). No guarantees 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 from outside our organisation. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Hi Deborah,

We have similar step labels showing in DSpace 5 and are looking to see if we 
can do something similar in DSpace 7. It looks to me like it has been raised as 
an issue but no one has volunteered to fix it 
(https://github.com/DSpace/dspace-angular/issues/1609 ).

If you find a solution before it is fixed in the main code, please share it as 
it would be helpful to us and potentially others as well.

Regards,
Daryl

From: 
dspace-community@googlegroups.com<mailto:dspace-community@googlegroups.com> 
mailto:dspace-community@googlegroups.com>> 
On Behalf Of Fitchett, Deborah
Sent: Friday, June 23, 2023 12:29 AM
To: dspace-community@googlegroups.com<mailto:dspace-community@googlegroups.com>
Subject: [EXTERNAL] [dspace-community] 2-step workflow display in DSpace 7

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 through a set of Check-submission items all at once, or work on a set 
of Final-check items.

In DSpace 5, we configured the list of tasks in the pool to include a column 
displaying the stage each task was at. We’ve done some other custom 
configuration (as you can see) but I’d thought the option to list the workflow 
step was relatively out-of-the box – maybe I’m wrong though.
[cid:image001.jpg@01D9DA62.959E4CD0]


In DSpace 7.4, it seems that by default, no matter which workflow step the item 
is at, it shows with the status “Waiting for Controller”, so curators can’t 
identify what stage the item is at until after they’ve claimed it. Before we 
put this up as an issue, are there any ways we’ve missed that we can set a 
status based on the workflow step, or otherwise make the workflow step visible 
to the curators?

Ngā mihi,

Deborah
––
Deborah Fitchett (she/her) MLIS, RLIANZA
Associate University Librarian, Digital Scholarship

––
Learning, Teaching and Library – Te Whare Pūrākau
PO Box 85064, Lincoln University
Lincoln 7647, Christchurch, New Zealand
+64 3 423 0358
deborah.fitch...@lincoln.ac.nz<mailto:deborah.fitch...@lincoln.ac.nz>
ltl.lincoln.ac.nz<http://ltl.lincoln.ac.nz/>

––
Lincoln University
Te Whare Wānaka o Aoraki
––




"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."
--
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx<https://urldefense.com/v3/__https:/www.lyrasis.org/about/Pages/Code-of-Conduct.aspx__;!!Nmw4Hv0!y1Z7fy4qYgVbPf8kslQV8we6UOwCd9gyeWhnfl6uPY7DwkrdqBomDIi6QA6K5P1kCx-xvpGSefRgI5egmhJC4atr1wk0sLYHM6bCGr4$>
---
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com<mailto:dspace-community+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/M

RE: [dspace-community] Make some fields visible to only admin users

[Fitchett, Deborah]

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: [dspace-community] Make some fields visible to only admin users

Caution: This email originated from outside our organisation. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Is there an easy to hide exclude/hide fields in the REST API (or UI) so that 
they only appear for admin users (or logged in users)?

Steve
--
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/cacc301d-9c65-4c57-ae2d-e6b9fa1db10en%40googlegroups.com.



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

-- 
All messages to this mailing list should adhere to the 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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/ME3PR01MB7524F4FBCCA12355EF32164EC5A8A%40ME3PR01MB7524.ausprd01.prod.outlook.com.

[dspace-community] Author name changes and provenance

[Fitchett, Deborah]

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 included the author’s name 
this is also repeated in each dc.description.provenance field as it’s approved 
and made available.  While these fields are admin-only, it would be ideal for 
authors’ privacy to redact or replace their old name wherever we don’t actively 
need it.

We’ve never referred back to checksums and are unlikely to have resource in 
future to do any proper digital curation that would use them.

So, other than records management purist reasons, are there any technical 
implications of editing the dc.description.provenance fields, including 
submitter’s name and email address and file names?

(In case it makes a difference, currently we’re on v5.8 xmlui, and like most 
people will at some point in the future migrate to v7.x.)

Deborah
––
Deborah Fitchett (she/her) MLIS, RLIANZA
Associate University Librarian, Digital Scholarship

––
Learning, Teaching and Library – Te Whare Pūrākau
PO Box 85064, Lincoln University
Lincoln 7647, Christchurch, New Zealand
+64 3 423 0358
deborah.fitch...@lincoln.ac.nz
ltl.lincoln.ac.nz

––
Lincoln University
Te Whare Wānaka o Aoraki
––




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

-- 
All messages to this mailing list should adhere to the 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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/SY6PR01MB7529409C700970674C50CA5FC58B9%40SY6PR01MB7529.ausprd01.prod.outlook.com.

RE: [dspace-community] Re: How to change the metadata of search results items? (dspace6 - Mirage)

[Fitchett, Deborah]

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. Scanning through I 
see a snippet:



xmlui.dri2xhtml.METS-1.0.no-author
  

--you may be able to instead get it to test if there’s a dc.contributor.editor 
and/or dc.publisher.

(This is assuming you’re using XMLUI.)

Deborah

From: dspace-community@googlegroups.com  On 
Behalf Of Tianyi Gu
Sent: Wednesday, 19 April 2023 2:59 pm
To: DSpace Community 
Subject: Re: [dspace-community] Re: How to change the metadata of search 
results items? (dspace6 - Mirage)

Caution: This email originated from outside our organisation. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Hi Aroldo,

You can change the submission form 
(https://github.com/DSpace/DSpace/blob/main/dspace/config/submission-forms.xml)
On Tuesday, April 18, 2023 at 10:43:42 PM UTC-4 Aroldo Rique wrote:
Hi Tianyi, I think I didn't explain myself correctly.

In the case of the figure, I want the metadata dc.contributor.editor and 
dc.publisher to appear (the latter in parentheses). I believe that dspace is 
looking for the dc.contributor.author metadata, which is empty and, therefore, 
the message (in Portuguese), of Author unknown. Do you know which file should I 
change so that I can exchange the dc.contributor.author metadata for the 
dc.contributor.editor metadata?

Em ter., 18 de abr. de 2023 às 23:17, Tianyi Gu  escreveu:
Hi Aroldo,

You could log in as an administrator and then edit that item. In the metadata 
tab, you will be able to edit the actual data.
On Tuesday, April 18, 2023 at 9:31:42 PM UTC-4 Aroldo Rique wrote:
Hello!

I need to change this metadata that appears in the result of a search. Does 
anyone know which file (and where in it) I should edit?

[https://groups.google.com/group/dspace-community/attach/183b13062a20cd/image.png?part=0.1=1]

Aroldo Rique
--
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-communi...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/e4672c6b-bae4-43fe-9a43-8a20c75d4ab2n%40googlegroups.com.
--
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/15c835e5-bc31-43cd-9540-83039964e257n%40googlegroups.com.



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

-- 
All messages to this mailing list should adhere to the 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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/ME3PR01MB7524CF7CA6D78D80B106AED6C5629%40ME3PR01MB7524.ausprd01.prod.outlook.com.

RE: [dspace-community] Copyright infringement on theses and dissertations

[Fitchett, Deborah]

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 comes down to responding to it: lay a complaint with Amazon / whatever 
other sites are hosting the content. Any otherwise legitimate site should have 
a DMCA/other takedown process. How the student (as copyright holder) phrases 
the complaint will depend on what, if any, licence the item has:

  *   No licence = All rights reserved: this is a straight-forward case where 
they’re breaching copyright by making copies at all.
  *   A Creative Commons “Non-Commercial” licence: here they’d be allowed to 
make a copy but by selling it they’re breaching the licence
  *   Another Creative Commons licence: they’re allowed to make a copy and are 
allowed to sell it – but they must still 
Attribute it correctly, which 
includes:
 *   The author’s name
 *   The original copyright notice and CC licence
 *   A link to the original material
They’re also not allowed to add any technological measures that restrict others 
from doing anything the licence permits.

So if they’ve missed out any of that information, or if they or Amazon have 
added any DRM, then they’re still in breach of the licence.

Deborah



From: dspace-community@googlegroups.com  On 
Behalf Of Yvonne
Sent: Thursday, 4 May 2023 5:59 am
To: Paige Morgan 
Cc: DSpace Community 
Subject: Re: [dspace-community] Copyright infringement on theses and 
dissertations

You don't often get email from ykeste...@gmail.com. 
Learn why this is important

Caution: This email originated from outside our organisation. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Thank you Paige,

I don't think the institution uses ProQuest ETDAdmin, but this is very 
interesting! I appreciate your sharing. I'm thinking the use of CC licenses 
that do not allow commercial use is a step in the right direction, but that of 
course does not prevent people from doing this anyway.

Best wishes,
Yvonne

On Wed, May 3, 2023 at 1:36 PM Paige Morgan 
mailto:paig...@udel.edu>> wrote:
Hi, Yvonne--

This is actually a fairly common thing to have happen, especially for 
institutions that use ProQuest ETDAdmin. ETDAdmin offers graduating students 
the choice between what they call "Traditional Publishing" and "Open Access 
Service." The Traditional Publishing option is free (except for the $50 they 
optionally charge to file copyright); the OA publishing is $90.

ProQuest asks students to agree to the agreement I've pasted below in its 
entirety, which includes the following clause:


ProQuest® Publishing Program - Election and Elements. The rights granted above 
shall be exercised according to the publishing option selected by Author on the 
previous Publishing Options screen, and subject to the following additional 
Publishing Program requirements:

  *   Redistribution of the Work. Except as restricted by Author in the 
publishing option selected, the rights granted by Author automatically include 
(1) the right to allow sale and distribution of the Work, in whole or in part, 
by agents and distributors, and (2) the right to make the Abstract, 
bibliographic data and any meta data associated with the Work available to 
search engines and harvesters.

Could this be what's happened in your situation? I know that a lot of students 
(and indeed, faculty members and advisors) aren't aware of it, and aren't in 
the habit of reading ProQuest's agreement carefully.

Paige


-
Meeting/regular work hours: Monday - Thursday, 9am-5pm; limited email on Friday 
mornings.


Dr. Paige C. Morgan
(she/her/they)
Digital Publishing and Copyright Librarian,
Head of Digital Initiatives & Preservation
University of Delaware Library, Museums and Press (on Lenape 
land)
Morris 118
ORCID: https://orcid.org/-0001-8076-7356
paig...@udel.edu
302.831.7153

Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings 
available via Zoom, phone, etc.)
** I observe email-free evenings and weekends. **


Traditional Publishing Agreement

This Agreement is between the author (Author) and ProQuest LLC, through its 
ProQuest® Dissertation Publishing business (ProQuest). Under this Agreement, 
Author grants ProQuest certain rights to preserve, archive and publish the 
dissertation or thesis, abstract, and index terms (the Work) provided by Author 
to ProQuest.

Section I. License for Inclusion of the Work in ProQuest® Publishing Program.

Grant of Rights. Author hereby grants to ProQuest the non-exclusive, worldwide 
right to reproduce, 

RE: [dspace-community] Create new schema is not showing

[Fitchett, Deborah]

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

From: dspace-community@googlegroups.com  On 
Behalf Of Christoforos Korifidis
Sent: Wednesday, 3 May 2023 4:06 am
To: DSpace Community 
Subject: [dspace-community] Create new schema is not showing

Caution: This email originated from outside our organisation. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Hello,

I have create a new schema from the admin interface.
I add three fields.
When I going to add new item on onw of my collection those new three fields are 
not showing.
What can I do ?
--
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/6370546a-33ff-426d-a4c8-426a28312e4an%40googlegroups.com.



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

-- 
All messages to this mailing list should adhere to the 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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/ME3PR01MB7524B6C94401C43E737EC7ACC56F9%40ME3PR01MB7524.ausprd01.prod.outlook.com.

RE: [dspace-community] Sort the collections

[Fitchett, 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.

Deborah

From: dspace-community@googlegroups.com  On 
Behalf Of Shanthi Govindan
Sent: Monday, July 10, 2023 9:32 PM
To: DSpace Community 
Subject: [dspace-community] Sort the collections

You don't often get email from 
bshanthigovin...@gmail.com. Learn why this 
is important

Caution: This email originated from outside our organisation. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

I request you to help me to sort the collections within a subcommunity in the 
month wise order ie (January, February, march December).

In Dspace it sorts alphabetcally, Please help me to sort as per the calendar 
year.

thanks

Shanthi
--
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/7e643322-1af3-4956-ba2c-262691d6n%40googlegroups.com.



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

-- 
All messages to this mailing list should adhere to the 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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/ME3PR01MB7524D5B5A23E879299716EF0C531A%40ME3PR01MB7524.ausprd01.prod.outlook.com.

RE: [dspace-community] Specify the type of metadata

[Fitchett, Deborah]

Kia ora Chandrika,

I agree such documentation would be useful but I haven’t seen it personally. 
Generally if I’m looking for information I’d start by browsing the wiki. If 
it’s not there, then I’d do a general websearch and/or look in the mailing list 
archives. Otherwise it’s a matter of testing it out for myself and asking on 
the mailing list if I get stuck, in case anyone else can help.

If you’re getting into more technical questions it can be useful to ask on the 
dspace-tech list instead. Make sure you mention which version of DSpace you’re 
using in that case.

But bear in mind that most people on both mailing lists are just other DSpace 
users, just like you. Sometimes we’ll know the answer, sometimes we won’t…

Deborah

From: dspace-community@googlegroups.com  On 
Behalf Of Chandrika Hebbar
Sent: Wednesday, August 9, 2023 1:47 AM
To: DSpace Community 
Subject: Re: [dspace-community] Specify the type of metadata

Caution: This email originated from outside our organisation. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Hi Deborah,

Could you please provide an update on the above?

Regards,
Chandrika Hebbar

On Tuesday, August 1, 2023 at 10:51:52 AM UTC+5:30 Chandrika Hebbar wrote:
Hi Deborah,

It would be really helpful to have a more descriptive implementation guide on 
adding validation of custom metadata (like Date, DateTime, etc..) with sample 
XML configuration. Please share the documentation 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 
dc.contributor.editor  or dc.identifier.isbn vs dc.identifier.doi, but there’s 
no validation performed on it.

You can define the submission form to validate specific fields based on a 
regular expression. There’s a little information about this in the submission 
form documentation at 
https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface

Deborah

From: dspace-c...@googlegroups.com<mailto:dspace-c...@googlegroups.com> 
mailto:dspace-c...@googlegroups.com>> On Behalf 
Of Chandrika Hebbar
Sent: Thursday, July 27, 2023 4:21 AM
To: DSpace Community 
mailto:dspace-c...@googlegroups.com>>
Subject: [dspace-community] Specify the type of metadata

You don't often get email from 
chandrik...@gmail.com<mailto:chandrik...@gmail.com>. Learn why this is 
important<https://aka.ms/LearnAboutSenderIdentification>

Caution: This email originated from outside our organisation. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Hi Team,

While creating metadata in the metadata registry, is there any way to specify 
the type that metadata should take (for example String, Date, Number...). There 
is an option to specify values in the Qualifier. Is this meant for specifying 
the type of metadata (If so, what are the values it can take)?


Thank you.

Regards,
Chandrika Hebbar
--
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-communi...@googlegroups.com<mailto:dspace-communi...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/90173036-363b-4daa-86be-60fc259cdcefn%40googlegroups.com<https://groups.google.com/d/msgid/dspace-community/90173036-363b-4daa-86be-60fc259cdcefn%40googlegroups.com?utm_medium=email_source=footer>.



"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."
--
All messages to this mailing list should adhere to the 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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com<mailto:dspace-community+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/829b20c9-6a58-4780-9d20-5c3871ebd83fn%40googlegroups.com<https://groups.google.com/d/msgid/dspace-community/829b20c9-6a58-4780-9d20-5c3871ebd83fn%40googlegroups.com?utm_

RE: [dspace-community] Specify the type of metadata

[Fitchett, Deborah]

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 submission form to validate specific fields based on a 
regular expression. There’s a little information about this in the submission 
form documentation at 
https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface

Deborah

From: dspace-community@googlegroups.com  On 
Behalf Of Chandrika Hebbar
Sent: Thursday, July 27, 2023 4:21 AM
To: DSpace Community 
Subject: [dspace-community] Specify the type of metadata

You don't often get email from 
chandrikahebba...@gmail.com. Learn why this 
is important

Caution: This email originated from outside our organisation. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Hi Team,

While creating metadata in the metadata registry, is there any way to specify 
the type that metadata should take (for example String, Date, Number...). There 
is an option to specify values in the Qualifier. Is this meant for specifying 
the type of metadata (If so, what are the values it can take)?


Thank you.

Regards,
Chandrika Hebbar
--
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/90173036-363b-4daa-86be-60fc259cdcefn%40googlegroups.com.



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

-- 
All messages to this mailing list should adhere to the 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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/ME3PR01MB7524CF00A1E9C112DE6AD884C500A%40ME3PR01MB7524.ausprd01.prod.outlook.com.

[dspace-community] 2-step workflow display in DSpace 7

[Fitchett, Deborah]

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 through a set of Check-submission items all at once, or work on a set 
of Final-check items.

In DSpace 5, we configured the list of tasks in the pool to include a column 
displaying the stage each task was at. We’ve done some other custom 
configuration (as you can see) but I’d thought the option to list the workflow 
step was relatively out-of-the box – maybe I’m wrong though.
[cid:image001.png@01D9A5B3.D21A2C80]


In DSpace 7.4, it seems that by default, no matter which workflow step the item 
is at, it shows with the status “Waiting for Controller”, so curators can’t 
identify what stage the item is at until after they’ve claimed it. Before we 
put this up as an issue, are there any ways we’ve missed that we can set a 
status based on the workflow step, or otherwise make the workflow step visible 
to the curators?

Ngā mihi,

Deborah
––
Deborah Fitchett (she/her) MLIS, RLIANZA
Associate University Librarian, Digital Scholarship

––
Learning, Teaching and Library – Te Whare Pūrākau
PO Box 85064, Lincoln University
Lincoln 7647, Christchurch, New Zealand
+64 3 423 0358
deborah.fitch...@lincoln.ac.nz
ltl.lincoln.ac.nz

––
Lincoln University
Te Whare Wānaka o Aoraki
––




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

-- 
All messages to this mailing list should adhere to the 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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/ME3PR01MB75244F0B835EF0150AC9B23BC522A%40ME3PR01MB7524.ausprd01.prod.outlook.com.

[dspace-community] Staff training for DSpace 7

[Fitchett, Deborah]

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

I wondered if any other institutions have developed staff training resources 
they might be able to share?

Many thanks!

Deborah
––
Deborah Fitchett (she/her) MLIS, RLIANZA
Associate University Librarian, Digital Scholarship

––
Learning, Teaching and Library – Te Whare Pūrākau
PO Box 85064, Lincoln University
Lincoln 7647, Christchurch, New Zealand
+64 3 423 0358
deborah.fitch...@lincoln.ac.nz
ltl.lincoln.ac.nz

––
Lincoln University
Te Whare Wānaka o Aoraki
––




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

-- 
All messages to this mailing list should adhere to the 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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/ME3PR01MB7524BCC617414EAD1C35BFB7C5719%40ME3PR01MB7524.ausprd01.prod.outlook.com.

RE: [dspace-community] Switching from "dc" to "dcterms" in DSpace

[Fitchett, Deborah]

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 it using xsl rules 
to whatever we want the harvesters to pick up. You can even use multiple 
contexts and/or metadata formats if different harvesters have different 
preferences.

Deborah

From: dspace-community@googlegroups.com  On 
Behalf Of Peter
Sent: Wednesday, April 10, 2024 10:56 PM
To: DSpace Community 
Subject: Re: [dspace-community] Switching from "dc" to "dcterms" in DSpace

You don't often get email from ad...@ispan.edu.pl. 
Learn why this is important

Caution: This email originated from outside our organisation. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Do you think it makes sense to use dc terms (but still, only standard 
qualifiers) for basic metadata just to avoid braking DSpace and then dcterms 
namespace (again, official set) for extending metadata? Can it negatively 
impact the "harvesting" tools? I'm curious if anyone has any experience from 
this perspective.

Peter

wtorek, 9 kwietnia 2024 o 14:38:39 UTC+1 Baer,Helen napisał(a):
Hi Peter,

I hear you about the unauthorized DC qualifiers that are in the DC namespace. 
We had been using some of them in our repository, and for the most part I ended 
their use a couple of years ago. I tried deleting a few of these elements and 
it caused problems for our developers because as Jorge and Tim explained, some 
of those elements are hard-coded into DSpace.

Best,

Helen

From: dspace-c...@googlegroups.com  on behalf of 
Peter 
Sent: Tuesday, April 9, 2024 4:56 AM

To: DSpace Community 
Subject: Re: [dspace-community] Switching from "dc" to "dcterms" in DSpace


** Caution: EXTERNAL Sender **
Hello,

Thank you all for your interest in the topic and for your insights so far. It 
looks like transition to dcterms is less straightforward than expected.

The reason behind this issue is that I would prefer to stick with official DCMI 
namespaces 
only. DSpace introduces many unofficial elements, and although I presume they 
are well established already, this is difficult to determine whether they will 
be correctly recognized by increasingly abundant external tools. I wouldn't 
mind using dc namespace, but dcterms has broader scope, so this is why I 
thought I would focus on this set of terms at first. However, attempting to 
adjust our current metadata to fit a stricter dc scope could be worthwhile.

Best,
Peter

poniedziałek, 8 kwietnia 2024 o 21:33:11 UTC+1 Reed, Marianne A. napisał(a):

Peter, could you please share why your institution wants to switch to “dcterms” 
instead of “dc” ?  I’m curious about the use case for this.



If you prefer, feel free to email me directly rather than replying to the list.



Best,

Marianne



Marianne Reed (she/her/hers)

Digital Publishing & Repository Manager

Watson Library, Room 470-G

University of Kansas Libraries

mr...@ku.edu

785-864-8913



From: DSpace Community 
mailto:dspace-c...@googlegroups.com>>
Sent: Monday, April 8, 2024 3:02 PM
To: DSpace Community 
mailto:dspace-c...@googlegroups.com>>
Subject: Re: [dspace-community] Switching from "dc" to "dcterms" in DSpace



Hi Peter,

I can verify that what Jorge says is true.  DSpace's User Interface (not only 
in 6.x, but also in 7.x) assumes you are using "dc" fields.  While it's not 
*impossible* to make the switch to "dcterms", I suspect it'd take a lot of 
effort to make it happen.  DSpace has always relied on the existence of many 
key "dc" fields for title, author, descriptions, etc.  To remove all those 
hardcoded assumptions would be a lot of work. If you still want to do it, your 
first step may be to search the codebase and configuration of any hardcoded 
references to "dc.*" fields, and replace them with "dcterms.*" equivalents.



Tim

On Monday, April 8, 2024 at 9:56:42 AM UTC-5 
jgspe...@gmail.com wrote:

Hello everyone,



In my opinion it would be a problem to make that change.

I think that several functionalities linked to specific dc fields would be 
affected.



Your idea is very interesting, but doing it en masse would involve 
reconditioning several elements in configurations in my opinion. In addition to 
reconditioning the worksheet, which would be the least important thing in this 
case.



I only recommend it if you have significant knowledge or assistance, and in a 
trial instance.



Greetings,

Jorge



El dom, 31 mar 2024 a las 9:44, Peter 
(mailto:ad...@ispan.edu.pl>>) escribió:

Hello,



We are considering switching from "dc" to "dcterms"