[dspace-tech] Re: Dspace 6.3 Problem with type-bind feature
Hi, I've encountered this also. Make sure that all the metadata fields in your input-forms.xml actually exist in the metadata registry. In your example, by default, there is a dc.contributor field in the metadata registry but perhaps other metadata fields in your input forms are not yet defined in the metadata registry hence the error when a submitter tried to continue on the next page. Hope this helps. Regard, euler On Thursday, May 12, 2022 at 11:14:30 PM UTC+8 agustin...@unr.edu.ar wrote: > Hi, I need to use the type-bind feature to request my users to complete > specific metadata for each document type. Since i want to be able to have > different types of documents in the same collection, this is the solution > that works best for me. > > *The configuration i've tried is like this:* > The user is in a collection and starts a submission, when they arrive to > the *Description Step* the *first page of the input form* asks them to > select the document type. Then, in the *second page of the input form*, > they are shown only the metadata that applies to that specific document > type. > I've tried to achieve this by modifying the *input-forms.xml* file to > have the following lines: > > > > > > > dc > type > > false > File type > dropdown > File type > > > > > !<-- And then, for example, a metadata only available for the "thesis" > type --> > > > > dc > contributor > > true > Thesis director > name > > > Thesis > > > > > > This works but the *problem* is that when the user reloads the second > page or it's done automatically (for example, when clicking the "add" > button) the page becomes blank. I believe this is because Dspace fails to > remember the Doc Type and so no type-bind metadata is shown. > > *Failed solution:* > I've tried to fix this by having the type metadata and the rest of the > metadata in the same page. But in this case if the user doesn't mannually > reloads the page, the type-bind metadata is not shown. Also, it gives the > user the ability to fill the metadata specific to a thesis for example and > then change the Doc type. > > *What can I do to fix this? Is there a better solution to my problem?* > -- 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/9853002e-9dc7-4d2b-8e03-0f4945da38dbn%40googlegroups.com.
[dspace-tech] Issues with classloader for additions-7.2.1.jar in DSpace 7.2.1
Hi all, I'm experiencing a weird issue in local environment which is running DSpace 7.2.1 with the order of customised classes being loaded. I have some customised classes in the additions module, e.g. DOIIdentifierProvider.java which also require some modifications to the spring beans configuration. When I try to run any dspace commands via the dspace utility I get errors that indicate that the dspace classes are being loaded instead of the ones I have in the additions module. This is also confirmed by the fact that if I add this to the dspace script: Get the JARs in $DSPACEDIR/jsp/WEB-INF/lib, separated by ':' JARS="$DSPACEDIR/lib/additions-7.2.1.jar:$DSPACEDIR/lib/*" Things work as expected. Moreover, when I deploy in our of our test environments (based on Ubuntu 20.04) I am able to run the dspace script without any issues. Is anyone else experiencing a similar issue? Is there any way to ensure that additions classes are always loaded first? Best, Agustina -- 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/053a815b-e638-4f74-9ac5-61f758a5eea8n%40googlegroups.com.
[dspace-tech] Re: Relationships problem and question
Hi Chris, While the "dspace.entity.type" metadata field does exist in the database by default, it is not used by default in the submission forms, etc. So, you shouldn't need to modify any configurations to disable that field from being used in the creation/deposit process. However, it seems you are correct that it *is* possible for an Administrator to add a "dspace.entity.type" metadata field to an existing Item if they edit the Item, search for that field and add it manually to the Item. This is unlikely to occur, but it is a possible mistake someone could make (and it sounds like that happened for you). The odd thing though is that adding an invalid "dspace.entity.type" should NOT block your ability to delete or edit the Item. That was a bug in 7.1, but we fixed it in 7.2 in this PR: https://github.com/DSpace/dspace-angular/pull/1503 So, that's confusing to me why you still experienced this bug. If you have the time to document how this occurred, or (if you have a test site which you can play with) you are willing to try and reproduce the issue, it'd be very useful to use if you could create a bug ticket in https://github.com/DSpace/dspace-angular/issues It sounds like you've hit some behavior that is entirely unexpected, and either we should consider blocking people from manually adding the "dspace.entity.type" field, or find a way to ensure that doing so doesn't cause unexpected errors. But, in order to track that down, we'd need more information on how to potentially reproduce this bug in an issue ticket. Thanks, Tim On Thursday, May 12, 2022 at 10:01:07 AM UTC-5 Chris Clawson wrote: > I understand that 'Relationships' and configurable entities are now part > of DS Angular 7.2. It seems to be controlled by a new (?) metadata term, > 'dspace.entity.type' , which enabled the ability to edit values under the > Edit> Relationships tab. This term now seems enabled by default when a new > item is created. > > We are not planning to use this feature in the near future and one of our > editors mistakenly just entered invalid data into this term while editing > an item. This changed the item into an undefined entity. The caused the > item to be uneditable and we could not delete it. It also may have > corrupted metadata exports at the collection level. > > Fortunately, I was able to correctly export Community metadata as a CSV > spreadsheet. A column for the term 'dspace.entity.type' was defined and I > was able to find and delete the cell with the bad data. Importing the > correcting, single row csv fixed my problem for this item and I was then > able to edit the item and normally export collection metadata. > > Question: Can/should I disable the default addition of this term when > creating a new item? Can someone provide a config file and method to do > this? We could always enable it later, right? > -- 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/e7d28208-71bd-4b80-a024-4777b866c0den%40googlegroups.com.
Re: [dspace-tech] mirage2 build problems
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 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
>>
>> .
>>
>
--
Human wheels spin round and round
While the clock keeps the pace... -- John Mellencamp
[dspace-tech] Dspace 6.3 Problem with type-bind feature
Hi, I need to use the type-bind feature to request my users to complete specific metadata for each document type. Since i want to be able to have different types of documents in the same collection, this is the solution that works best for me. *The configuration i've tried is like this:* The user is in a collection and starts a submission, when they arrive to the *Description Step* the *first page of the input form* asks them to select the document type. Then, in the *second page of the input form*, they are shown only the metadata that applies to that specific document type. I've tried to achieve this by modifying the *input-forms.xml* file to have the following lines: dc type false File type dropdown File type !<-- And then, for example, a metadata only available for the "thesis" type --> dc contributor true Thesis director name Thesis This works but the *problem* is that when the user reloads the second page or it's done automatically (for example, when clicking the "add" button) the page becomes blank. I believe this is because Dspace fails to remember the Doc Type and so no type-bind metadata is shown. *Failed solution:* I've tried to fix this by having the type metadata and the rest of the metadata in the same page. But in this case if the user doesn't mannually reloads the page, the type-bind metadata is not shown. Also, it gives the user the ability to fill the metadata specific to a thesis for example and then change the Doc type. *What can I do to fix this? Is there a better solution to my problem?* -- 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/abe96d7c-eebb-40fa-8fcd-867e0ea492abn%40googlegroups.com.
Re: [dspace-tech] mirage2 build problems
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 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
>
> .
>
--
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/CAK%3DKc-u20yqqvv4CdEw1aFMNurwSTM3JAEgitb3K%3DTSfgE5Xqg%40mail.gmail.com.
[dspace-tech] Relationships problem and question
I understand that 'Relationships' and configurable entities are now part of DS Angular 7.2. It seems to be controlled by a new (?) metadata term, 'dspace.entity.type' , which enabled the ability to edit values under the Edit> Relationships tab. This term now seems enabled by default when a new item is created. We are not planning to use this feature in the near future and one of our editors mistakenly just entered invalid data into this term while editing an item. This changed the item into an undefined entity. The caused the item to be uneditable and we could not delete it. It also may have corrupted metadata exports at the collection level. Fortunately, I was able to correctly export Community metadata as a CSV spreadsheet. A column for the term 'dspace.entity.type' was defined and I was able to find and delete the cell with the bad data. Importing the correcting, single row csv fixed my problem for this item and I was then able to edit the item and normally export collection metadata. Question: Can/should I disable the default addition of this term when creating a new item? Can someone provide a config file and method to do this? We could always enable it later, right? -- 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/e448e2c8-f24a-49b0-b259-b23b25b79f40n%40googlegroups.com.
[dspace-tech] mirage2 build problems
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.
