[dspace-tech] fields in submission-forms.xml
How can I make a field load based on another previously loaded? For example: in this code I need the "races" are charged according to the "faculties". uni faculty false Faculty dropdown Select faculty. You must select a faculty uni career false Career dropdown Select career You must select a career I hope you can help me. Thank you. Emilia.- -- 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/556b310f-f0f1-4ebd-a549-cc0d22488156n%40googlegroups.com.
Re: [dspace-tech] Export to CSV in Administrator Workflow
Thanks for your answer. I am using version 7.6.1 of DSpace. The button is still not shown. Emilia.- El martes, 28 de mayo de 2024 a las 10:18:24 UTC-3, Morgan, Paige escribió: > > Hi, Emilia-- > > Are you running 7.1? I remember when I encountered this problem myself – > it turned out that the export button had been written into the interface, > but it didn't actually have any functionality behind it. > > I did, at Tim Donohue's suggestion, put in a ticket suggesting that > functionality be built in, but I don't think anything has happened with > that, and in more recent versions (7.4), the icon/button has been removed. > > Good luck! > Paige > > - > *Meeting/regular work hours: Monday - Friday, 9am-4:30pm* > > *Dr. Paige C. Morgan* > (she/they) > > Digital Publishing and Copyright Librarian, > Head of Digital Initiatives & Preservation > University of Delaware Library, Museums and Press (on > Lenape land <https://native-land.ca/maps/territories/lenape/>) > Morris 118 > ORCID: https://orcid.org/-0001-8076-7356 > pai...@udel.edu > 302.831.7153 <(302)%20831-7153> > > *** I observe email-free evenings and weekends. *** > > > <https://outlook.office.com/bookwithme/user/9cba1be23fdf4b4098e3adab10600...@udel.edu?anonymous=bwmEmailSignature> > Book > time to meet with me > <https://outlook.office.com/bookwithme/user/9cba1be23fdf4b4098e3adab10600...@udel.edu?anonymous=bwmEmailSignature> > > -- > *From:* dspac...@googlegroups.com on behalf > of Emilia Lobo > *Sent:* Monday, May 27, 2024 09:54 > *To:* DSpace Technical Support > > *Subject:* Re: [dspace-tech] Export to CSV in Administrator Workflow > search-export-metadata > > Hello!, > This process indicates that it completed successfully but I don't see > where to download the completed script from the administrator account. > I don't see any link to recover that generated file. > What can be? > Thanks, > Emilia > > El miércoles, 30 de noviembre de 2022 a las 18:11:20 UTC-3, Tim Donohue > escribió: > > Hi Paige, > > Yes that makes sense. It's clear that in your use case this "Export to > CSV" is not for "Batch Metadata Editing"... it's just to generate a basic > "status report" of items in workflow. > > If you would, could you or Keith submit a bug ticket to > https://github.com/DSpace/dspace-angular/issues ? I'd recommend adding > the step by step instructions for reproducing the error. Then add in some > basic details of how you'd like to use this feature. I can then see if I > can find someone to work on this in the near future, with the hope that we > can fix it (instead of remove it). They will have to investigate the > underlying issue though to see if it's easier to fix quickly.. or remove it > (to solve the bug) temporarily & fix later. > > Overall though, the more I look at this feature, the more I think this was > accidental & never meant to appear on that page. :) So, it may turn out to > be a happy accidental feature! > > Tim > > On Wednesday, November 30, 2022 at 2:57:55 PM UTC-6 pai...@udel.edu wrote: > > Hi Tim, > > Thanks for this response! For use cases, I would find it helpful to have > in process workflow items exportable as a way of tracking what’s going on > with items that are in process, and/or that have been orphaned. When we > were running DSpace 5.3, there was no way for an administrator to even see > broadly what was happening, and what workflow items *were* in process. We > have a number of items that have been hanging out in that space, and this > is the first time that I've actually been able to see them. > > My hope is that I can work on cleaning those up, and then not have so many > sitting around -- but I would find it very helpful to be able to check and > export a CSV periodically, just to check in with folks who use the workflow > setup. > > Does that make sense as a use case? > > Thanks again, > Paige > > On Wed, Nov 30, 2022 at 15:36 Tim Donohue wrote: > > Hi Paige & Keith, > > I can confirm this is happening locally for me as well. It looks like a > possible bug. This "Export to CSV" works fine in normal search results & > also in the "Your submissions" part of MyDSpace. But, I can verify that it > doesn't work when viewing "Workflow tasks". > > That said, I admit, I wonder if that "Export to CSV" link should even > appear on the "Workflow tasks" page, as it's not really possible to perform > batch metadata editing on "Workflow tasks". (The Export
Re: [dspace-tech] Export to CSV in Administrator Workflow
search-export-metadata Hello!, This process indicates that it completed successfully but I don't see where to download the completed script from the administrator account. I don't see any link to recover that generated file. What can be? Thanks, Emilia El miércoles, 30 de noviembre de 2022 a las 18:11:20 UTC-3, Tim Donohue escribió: > Hi Paige, > > Yes that makes sense. It's clear that in your use case this "Export to > CSV" is not for "Batch Metadata Editing"... it's just to generate a basic > "status report" of items in workflow. > > If you would, could you or Keith submit a bug ticket to > https://github.com/DSpace/dspace-angular/issues ? I'd recommend adding > the step by step instructions for reproducing the error. Then add in some > basic details of how you'd like to use this feature. I can then see if I > can find someone to work on this in the near future, with the hope that we > can fix it (instead of remove it). They will have to investigate the > underlying issue though to see if it's easier to fix quickly.. or remove it > (to solve the bug) temporarily & fix later. > > Overall though, the more I look at this feature, the more I think this was > accidental & never meant to appear on that page. :) So, it may turn out to > be a happy accidental feature! > > Tim > > On Wednesday, November 30, 2022 at 2:57:55 PM UTC-6 pai...@udel.edu wrote: > >> Hi Tim, >> >> Thanks for this response! For use cases, I would find it helpful to have >> in process workflow items exportable as a way of tracking what’s going on >> with items that are in process, and/or that have been orphaned. When we >> were running DSpace 5.3, there was no way for an administrator to even see >> broadly what was happening, and what workflow items *were* in process. We >> have a number of items that have been hanging out in that space, and this >> is the first time that I've actually been able to see them. >> >> My hope is that I can work on cleaning those up, and then not have so >> many sitting around -- but I would find it very helpful to be able to check >> and export a CSV periodically, just to check in with folks who use the >> workflow setup. >> >> Does that make sense as a use case? >> >> Thanks again, >> Paige >> >> On Wed, Nov 30, 2022 at 15:36 Tim Donohue wrote: >> >>> Hi Paige & Keith, >>> >>> I can confirm this is happening locally for me as well. It looks like a >>> possible bug. This "Export to CSV" works fine in normal search results & >>> also in the "Your submissions" part of MyDSpace. But, I can verify that it >>> doesn't work when viewing "Workflow tasks". >>> >>> That said, I admit, I wonder if that "Export to CSV" link should even >>> appear on the "Workflow tasks" page, as it's not really possible to perform >>> batch metadata editing on "Workflow tasks". (The Export to CSV feature is >>> primarily used for Batch Metadata Editing purposes) >>> >>> So, this is all to say, I think there's a bug here. But, the bug might >>> be that the option even appears on this page. Is this a specific use case >>> you had for wanting to export Workflow Tasks to CSV? Just curious as maybe >>> there's a way to get this possibly accidental feature "working" rather than >>> remove it altogether. Either way, I do think this is a bug, I'm just not >>> sure which fix is appropriate yet (remove it, or fix it). >>> >>> If you have time, please feel free to submit a bug ticket to >>> https://github.com/DSpace/dspace-angular/issues I'm assuming you >>> likely want it "fixed" (rather than removed), so it'd be useful to >>> understand your use cases in this ticket. >>> >>> Thanks! >>> >>> Tim >>> >>> Tim >>> -- >>> *From:* dspac...@googlegroups.com on behalf >>> of Paige Morgan >>> *Sent:* Tuesday, November 29, 2022 3:35 PM >>> *To:* mad...@udel.edu >>> *Cc:* DSpace Technical Support >>> *Subject:* Re: [dspace-tech] Export to CSV in Administrator Workflow >>> >>> To add on to this, I get the exact same response when I try this on the >>> https://demo7.dspace.org/ site. >>> >>> I go to Administer Workflow (while logged in as administrator); it shows >>> 1-10 of 67 total items in process. On the righthand side, there's an icon >>> to export search results as a CSV. When I click that, the process starts, >>> and finishes normally, and offers me a CSV that I can download (titled >>> metadataExportSearch). The spreadsheet is 14b, and its only content is a >>> top row for id and collection -- no other info is included. >>> >>> It seems like this might be a more widespread bug -- can anyone confirm? >>> >>> Thanks, >>> 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
[dspace-tech] Re: DSpace 7 localization issue
Hello! I couldn't fix this on the server (debian). I ran both commands in .../dspace-angular: yarn run sync-i18n yarn merge-i18n -s src/themes/mytheme/assets/i18n And I keep seeing keys instead of translations. On the development team I can see them without problem. Is there a missing step to take into account? Thank you.- El jueves, 16 de noviembre de 2023 a las 14:01:49 UTC-3, Andrew K escribió: > Hi Tim! > > Thank you! > Looking deeper into this issue, I found this topic "Syncing existing > translations with changes to en.json5" > > https://wiki.lyrasis.org/pages/viewpage.action?pageId=117735441#DSpace7TranslationInternationalization(i18n)Localization(l10n)-Syncingexistingtranslationswithchangestoen.json5 > > I just run *yarn run sync-i18n* and magically received fully updated > localization file synced to the authoritative English file. > Moreover, all translated keys I had added before were kept! > So I highly recommend this tool. It completely solves the problem of > missing keys. > > Best regards, > Andrew > > > > четвер, 16 листопада 2023 р. о 00:56:22 UTC+2 DSpace Technical Support > пише: > >> Hi Andrew, >> >> We're aware that these i18n files can get "out of sync" easily and are >> working on ways to improve that. See this ticket: >> https://github.com/DSpace/dspace-angular/issues/2340 >> >> There's no exact solution yet, but many developers agree it's a >> frustration. So, if you have more ideas to share, feel free to add to that >> ticket. >> >> Regarding the display of missing keys, the current behavior is the same >> as it was in DSpace 6.x (where the key was displayed if missing). I'm not >> aware of a way to change that to be English by default, but you are welcome >> to create a ticket regarding that and I can ask other developers to look >> into it. I agree that it might be better to show English instead of a >> (cryptic) i18n key. >> >> Tim >> >> On Tuesday, November 7, 2023 at 8:18:21 AM UTC-6 Andrew K wrote: >> >>> Hello! >>> >>> I noticed that the localization files lag behind. And this is perfectly >>> normal. >>> The documentation says: "*When new keys are introduced, TODO messages >>> are automatically added to the catalogs of other languages*" >>> >>> https://wiki.lyrasis.org/pages/viewpage.action?pageId=117735441#DSpace7TranslationInternationalization(i18n)Localization(l10n)-Translations(forexample,nl.json5) >>> But that does not happen, new keys are missing, at least for uk.json5. >>> Is there a way to correct that? >>> >>> And the next problem is that missing keys in the .json5 file are >>> displayed as key names. It would be much much better if the English names >>> were shown instead. >>> Is that possible? >>> >>> Best regards, >>> Andrew >>> >>> P.S.: >>> >> -- 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/af8559b9-2f51-4a24-a5e3-e26d9a6059e7n%40googlegroups.com.
[dspace-tech] yarn merge-i18n does not update changes
The first time I made changes to the es.json5 file, the changes were
applied after running the command: yarn merge-i18n -s
src/themes/mytheme/assets/i18n
and now the changes I add are not reflected.
For example these lines:
// "dso-selector.placeholder": "Look for a {{ type }}",
"dso-selector.placeholder": "Busque un {{ type }}",
Where do I translate {{ type }} to be a collection or community?
"admin.access-control.epeople.edit.breadcrumbs": "Edit user",
"admin.access-control.epeople.add.breadcrumbs": "Create user",
Thanks,
Emilia.-
--
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/69f568cb-5a9f-4b2c-a4a4-9257b4114ee0n%40googlegroups.com.
[dspace-tech] Re: Subject Keyword - Where to add or change values?
Hi! Query: You can automatically translate the srsc.xml file into Spanish, for example Thanks... El martes, 21 de mayo de 2024 a las 11:19:49 UTC-3, DSpace Technical Support escribió: > Hi, > > By default the Subject Keyword field is configured to use the "srsc.xml" > controlled vocabulary as defined in the "subject" field in your > "submission-forms.xml" on the backend: > https://github.com/DSpace/DSpace/blob/dspace-7_x/dspace/config/submission-forms.xml#L189-L202 > > The "srsc.xml" file is providing those various values and can be found in > your config directory as well here: > https://github.com/DSpace/DSpace/blob/dspace-7_x/dspace/config/controlled-vocabularies/srsc.xml > > You can turn off this controlled vocabulary by removing or commenting out > the "srsc" tag in that submission-forms.xml > configuration. This would turn this field into a free text field. > > More information on configuring the Submission UI can be found in the docs > at https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface > Especially take a look at the sections on the "submission-forms.xml" which > is where you define the fields in each of the forms. > > Tim > > On Monday, May 20, 2024 at 11:45:05 AM UTC-5 michel.m...@gmail.com wrote: > >> Can I leave the text free in the "subject Keyword" option when >> registering the item? >> >> Files: /opt/dspace/config/controlled-vocabularies/*.* >> >> Em seg., 20 de mai. de 2024 às 10:31, Michel Montenegro < >> michel.m...@gmail.com> escreveu: >> >>> In the system I didn't find where to change it, if so where is it? >>> In the database or XML file where can I add new values? >>> >>> [image: image.png] >>> >>> -- >>> Atenciosamente, >>> *Michel Pinheiro Montenegro* >>> - *Bacharel* em Sistema de Informação >>> - [Lato Sensu] *Especialista* em Engenharia de Sistemas >>> - [Stricto Sensu] *Mestre* em Ciência da Computação >>> - [Stricto Sensu] *Doutorando* em Ciência da Computação >>> >>> *Linkedln*: https://www.linkedin.com/in/michelmontenegro/ >>> *E-mail/Gtalk*: michel.m...@gmail.com >>> >> >> >> -- >> Atenciosamente, >> *Michel Pinheiro Montenegro* >> - *Bacharel* em Sistema de Informação >> - [Lato Sensu] *Especialista* em Engenharia de Sistemas >> - [Stricto Sensu] *Mestre* em Ciência da Computação >> - [Stricto Sensu] *Doutorando* em Ciência da Computação >> >> *Linkedln*: https://www.linkedin.com/in/michelmontenegro/ >> *E-mail/Gtalk*: michel.m...@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/0ec48694-f842-4c7d-98fa-57cbcf7a0672n%40googlegroups.com.
Re: [dspace-tech] Re: disable browse subject tree
Thank you! I was able to solve it with your instructions. Now I would like to be able to add a search by item type (dc.type) to the menu bar. What files should I modify? Thank you.- Emilia.- El miércoles, 27 de marzo de 2024 a las 15:40:51 UTC-3, Bill Tantzen escribió: > I discovered this setting in config.yml, and documented here: > https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Configuration > > - filter: 'subject' > vocabulary: 'srsc' > enabled: false > > Setting this to false in tandem with the setting in dspace.cfg noted above > will get rid of any 'browse by subject tree' options. > > On Wed, Mar 27, 2024 at 12:58 PM Emilia Lobo wrote: > >> Hello! >> >> I want to try to do the same or replace that search so that I can perform >> it by document type for example. >> >> What files should I modify? >> Are the changes made from DSpace and from dspace-angular? >> Thanks. >> >> El viernes, 15 de marzo de 2024 a las 17:26:49 UTC-3, tant...@umn.edu >> escribió: >> >>> In DSpace 7.6.1, we do not user Hierarchical Browse Indexes. In >>> dspace.cfg, I have >>> >>> webui.browse.vocabularies.disabled = srsc >>> >>> so that "By Subject Category" is not an option in the global browse >>> menu. However, when expanding the Subject filter in discovery, there is >>> still a link to "Browse subject tree" >>> >>> Can I / How do I disable this? >>> Regards, >>> Bill >>> >> -- >> 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...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/dspace-tech/ab1cdfa5-182b-4d73-b6e1-f6c480767b72n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/dspace-tech/ab1cdfa5-182b-4d73-b6e1-f6c480767b72n%40googlegroups.com?utm_medium=email_source=footer> >> . >> > > > -- > __ > Bill TantzenUniversity of Minnesota Libraries > 612-626-9949 <(612)%20626-9949> (U of M) 612-325-1777 <(612)%20325-1777> > (mobile) > -- 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/a315b100-6ad5-4f70-b00a-c653676938dfn%40googlegroups.com.
[dspace-tech] Re: Subject keywords: choice of free text or controlled vocabulary
Hello Julia. You can enter free text by simply typing it in the text box and then pressing the TAB key to add other keywords. You can also comment on the controlled vocabulary line. Greetings. Emilia.- El viernes, 5 de abril de 2024 a las 11:56:42 UTC-3, Julia Gilmore escribió: Hello, This is a subject keywords question (and apologies if I missed this answer somewhere else in the group!): We are not seeing how to set up the field so we can add either free text *or* select from the controlled vocabulary (srcs)? This is how our field currently looks: [image: Screenshot 2024-04-05 at 10.09.30 AM.png] Thanks! Julia -- 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/7048f7a5-ef76-49ce-9313-12141af3837bn%40googlegroups.com.
[dspace-tech] Problem with merge branch main (8.0-SNAPSHOT) with branch desarrollo (tag dspace-7.6.1)
Hello! I wanted to consult the following: I'm working with a git clone tagged dspace-7.6.1 but I have conflicts when I want to do a merge with the main branch (after updating the files I can't get the DSpace up again). Therefore I avoid the merge with main on the development machine and do git push from the development branch to the remote repository. I use command git push -u origin development. On GitHub I do not have this branch created so I have nothing to compare with to make a Pull Request. What am I doing wrong? I also want to stay working only with Dspace version 7.6.1 (tag dspace-7.6.1) and continue syncing with bug fixes for this version. In the main it already appears as 8.0-SNAPSHOT DSpace Parent Project. I don't want to move to this version yet. I hope you have been able to understand me. Thank you. Greetings. Emilia.- -- 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/9878bc67-d244-421e-a99a-f22e0065f0b8n%40googlegroups.com.
[dspace-tech] Re: disable browse subject tree
Hello! I want to try to do the same or replace that search so that I can perform it by document type for example. What files should I modify? Are the changes made from DSpace and from dspace-angular? Thanks. El viernes, 15 de marzo de 2024 a las 17:26:49 UTC-3, tant...@umn.edu escribió: > In DSpace 7.6.1, we do not user Hierarchical Browse Indexes. In > dspace.cfg, I have > > webui.browse.vocabularies.disabled = srsc > > so that "By Subject Category" is not an option in the global browse menu. > However, when expanding the Subject filter in discovery, there is still a > link to "Browse subject tree" > > Can I / How do I disable this? > Regards, > Bill > -- 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/ab1cdfa5-182b-4d73-b6e1-f6c480767b72n%40googlegroups.com.
[dspace-tech] Error in merge
Hello, I am working on a development branch and I want to perform a merge to the main branch and I get these errors. Could someone help me? - biblioteca@biblioteca-Aspire-E5-575:~/rdilocal/DSpace$ sudo git branch * desarrollo main biblioteca@biblioteca-Aspire-E5-575:~/rdilocal/DSpace$ git merge main error: permisos insuficientes para agregar un objeto a la base de datos del repositorio .git/objects error: error: No es posible agregar dspace/pom.xml a la base de datos error: permisos insuficientes para agregar un objeto a la base de datos del repositorio .git/objects error: permisos insuficientes para agregar un objeto a la base de datos del repositorio .git/objects error: error: No es posible agregar dspace/config/submission-forms.xml a la base de datos error: permisos insuficientes para agregar un objeto a la base de datos del repositorio .git/objects error: error: No es posible agregar dspace/config/dspace.cfg a la base de datos error: permisos insuficientes para agregar un objeto a la base de datos del repositorio .git/objects error: permisos insuficientes para agregar un objeto a la base de datos del repositorio .git/objects error: permisos insuficientes para agregar un objeto a la base de datos del repositorio .git/objects error: error: No es posible agregar dspace-server-webapp/pom.xml a la base de datos error: permisos insuficientes para agregar un objeto a la base de datos del repositorio .git/objects error: error: No es posible agregar dspace-api/src/main/java/org/dspace/eperson/EPersonServiceImpl.java a la base de datos error: permisos insuficientes para agregar un objeto a la base de datos del repositorio .git/objects error: error: No es posible agregar dspace-api/src/main/java/org/dspace/content/authority/ChoiceAuthorityServiceImpl.java a la base de datos error: permisos insuficientes para agregar un objeto a la base de datos del repositorio .git/objects error: error: No es posible agregar dspace-api/pom.xml a la base de datos fatal: unable to read tree c1e8b5953f1f0909a515cc4c5a01360a076a52cc -- 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/5898774f-36fe-48a2-8edb-993309e1e842n%40googlegroups.com.
[dspace-tech] Re: No showing thumbnails on DSpace 7.6
Hello! In development, can this also be executed? How can thumbnails be generated for PDF type files? Thank you. Greetings.- El lunes, 11 de marzo de 2024 a las 10:35:16 UTC-3, Joshua Kim escribió: > Thank you. > > On Tuesday, March 5, 2024 at 8:35:36 AM UTC-5 Victorhugo Bisangwa wrote: > >> Hello Kim, >> >> For them to be displayed, you should go to processes and run a process >> called filter-media. When it's done running, all the thumbnails will show >> up! >> >> Hope this helps! >> >> On Monday, March 4, 2024 at 6:19:33 PM UTC+2 Kim, Joshua wrote: >> >>> Hello, >>> >>> I am still new to DSpace 7. After installing DSpace 7.6, now the >>> thumbnails are not displayed on the home page as well as in any pages >>> though we have images. How can I figure out this issue? Thank you for your >>> help in advance. >>> >>> >> -- 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/ff6a8a26-606b-42b5-82ad-aa49241fb9a3n%40googlegroups.com.
[dspace-tech] Re: Relationships problem and question
Buenas tardes. En mi caso, el problema se presenta cuando voy a crear una nueva colección y debo seleccionar el tipo de entidad (collection.form.entityType), este metadato no muestra ningún valor, no se despliega. Podrían orientarme en la solución. ¿Dóndedebo definir o habilitar los tipos de entidad para que puedan visualizarse? Saludos. Emilia.- El jueves, 12 de mayo de 2022 a las 12:25:38 UTC-3, Tim Donohue escribió: > 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/ae322fea-d9f1-4389-aa16-5feda0d5588dn%40googlegroups.com.
