[dspace-tech] Re: Change color from blue to green in Dspace jspui
There are two potential methods.that I can think of. 1) The green colour is being set by the 'btn-success', change this to 'btn-primary' and it should be the same colour as the 'Learn More' button above it. 2) If you wanted to change the 'success' colour then you could customise the Bootstrap theme. DSpace appears to be using Bootstrap 3 so you can look at other resources online as to how to change the colour by modifying Bootstrap. On Thursday, August 15, 2019 at 11:53:29 PM UTC+10, Asim Ullah wrote: > > How to change the color from green to blue in DSpace jspui. > -- 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 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/2e8f1449-7d55-4ce0-a363-45eb5615fa5e%40googlegroups.com.
[dspace-tech] Re: Multiple item submission forms - examples?
Our input form XML: https://github.com/anu-doi/DSpace/blob/anu-dspace58/dspace/config/input-forms.xml Our submission form XML: https://github.com/anu-doi/DSpace/blob/anu-dspace58/dspace/config/item-submission.xml There was also some issue I think with BTE (though I could be wrong and it may be a larger issue). Unfortunately I can't remember exactly how the issue manifests itself. We now use the following two updated files: https://github.com/anu-doi/DSpace/blob/anu-dspace58/dspace/modules/additions/src/main/java/org/dspace/app/util/DCInputsReader.java https://github.com/anu-doi/DSpace/blob/anu-dspace58/dspace/modules/additions/src/main/java/org/dspace/submit/lookup/DSpaceWorkspaceItemOutputGenerator.java On Saturday, September 7, 2019 at 12:23:00 AM UTC+10, Julie Shedd wrote: > > Good morning - > > I am working on creating a custom submission form for theses and > dissertations. We'll only have 2 forms - the default form and this one. > > Could someone who is doing this send me an example of what your > input-forms.xml and item-submission.xml files look like? I have gotten one > form half-working and can't see where I'm going wrong, but an example would > help. > > I would really appreciate it! > -- 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 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/76f1f2c8-2daf-4043-81ac-fc1b7e08b264%40googlegroups.com.
Re: [dspace-tech] starting dspace 6.3
The tables are created when you start up the application.
On Friday, February 14, 2020 at 9:15:07 AM UTC+11, Jose Blanco wrote:
>
> Tim,
>
> How do I get the database to be recreated. I have the db, but it has not
> tables. I dropped them. I thought the fresh_install would create them.
>
>
> On Thu, Feb 13, 2020 at 3:32 PM Jose Blanco > wrote:
>
>> When I merged the code, I had this:
>>
>> * private Context bfContext;*
>>
>>
>> which actually, I'm not sure what purpose it served, so I'm going to
>> comment it out, and try again.
>>
>>
>> Thanks!
>>
>> On Thu, Feb 13, 2020 at 3:18 PM Tim Donohue > > wrote:
>>
>>> Hi Jose,
>>>
>>> The error says: "Could not determine type for: org.dspace.core.Context,
>>> at table: bitstreamformatregistry, for columns:
>>> [org.hibernate.mapping.Column(bfContext)]"
>>>
>>> Have you modified the org.dspace.content.BitstreamFormat class in some
>>> way? Does "bfContext" maybe represent something you've added to the
>>> codebase? I'm not sure myself what "bfContext" is (as I don't see anything
>>> by that name in DSpace code). But, the error makes it sound like Hibernate
>>> thinks "bfContext" is supposed to be a Database column in the
>>> "bitstreamformatregistry" table, and cannot find it.
>>>
>>> So, maybe some sort of custom code in the "BitstreamFormat" class (which
>>> corresponds to the "bitstreamformatregistry" table) is confusing Hibernate
>>> & causing this error?
>>>
>>> Tim
>>>
>>> --
>>> *From:* Jose Blanco >
>>> *Sent:* Thursday, February 13, 2020 12:10 PM
>>> *To:* Tim Donohue >
>>> *Cc:* José Geraldo >; DSpace Technical
>>> Support >
>>> *Subject:* Re: [dspace-tech] starting dspace 6.3
>>>
>>> I did add the following, but did not think it would cause an issue:
>>>
>>> private String sessionStatus;
>>>
>>>
>>> this gets initialized:
>>>
>>> sessionStatus = "";
>>>
>>>
>>> And these two methods:
>>>
>>>
>>> > public void setSessionStatus(String info)
>>>
>>> > {
>>>
>>> > sessionStatus = info;
>>>
>>> > }
>>>
>>> >
>>>
>>>
>>> > public String getSessionStatus()
>>>
>>> > {
>>>
>>> > return sessionStatus;
>>>
>>> > }
>>>
>>>
>>>
>>>
>>>
>>> On Thu, Feb 13, 2020 at 12:47 PM Tim Donohue >> > wrote:
>>>
>>> Jose,
>>>
>>> Have you customized the v6.3 "Context" class in some way? The error
>>> line numbers there do not seem to match up with the out-of-the-box DSpace
>>> 6.3 codebase. These are the error lines I'm talking about
>>>
>>> at org.dspace.core.Context.init(Context.java:173)
>>> at org.dspace.core.Context.(Context.java:129)
>>>
>>> In the v6.3 codebase, lines #129 and #173 in the Context class are both
>>> empty lines:
>>>
>>> https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-api/src/main/java/org/dspace/core/Context.java#L129
>>>
>>> https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-api/src/main/java/org/dspace/core/Context.java#L173
>>>
>>> It's difficult to help you debug the issue here as it doesn't look like
>>> your Context class is the same as out-of-the-box DSpace 6.3. So, my
>>> immediate guess is that your customizations may be causing an issue here --
>>> either customizations in the Context class, or some sort of database
>>> customizations or both. If you didn't mean to customize the Context class,
>>> then you might want to try and re-sync it with the one in DSpace 6.3.
>>>
>>> Tim
>>>
>>> --
>>> *From:* dspac...@googlegroups.com <
>>> dspac...@googlegroups.com > on behalf of Jose Blanco <
>>> bla...@umich.edu >
>>> *Sent:* Thursday, February 13, 2020 11:35 AM
>>> *To:* José Geraldo >
>>> *Cc:* DSpace Technical Support >
>>> *Subject:* Re: [dspace-tech] starting dspace 6.3
>>>
>>> Still stuck on this issue.
>>>
>>> On Wed, Feb 12, 2020 at 3:16 PM Jose Blanco >> > wrote:
>>>
>>> The dspace.log does not have much info. I think the error happens when
>>> the code tries to do this:
>>>
>>> https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-api/src/main/java/org/dspace/core/Context.java#L160
>>>
>>> Not sure why it was not able to get the db connection in:
>>>
>>>
>>> https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-api/src/main/java/org/dspace/core/Context.java#L160
>>>
>>> I see I get the same error when I try this:
>>>
>>> *> /l1/dspace/repository/dev63/bin/dspace create-administrator*
>>>
>>> Exception: The schema validator returned: Could not determine type for:
>>> org.dspace.core.Context, at table: bitstreamformatregistry, for columns:
>>> [org.hibernate.mapping.Column(bfContext)]
>>>
>>> org.dspace.core.exception.DatabaseSchemaValidationException: The schema
>>> validator returned: Could not determine type for: org.dspace.core.Context,
>>> at table: bitstreamformatregistry, for columns:
>>> [org.hibernate.mapping.Column(bfContext)]
>>> at org.dspace.core.Context.init(Context.java:173)
>>> at org.dspace.core.Context.(Context.java:129)
>>> at
>>> org.dspace.administer.Create
[dspace-tech] Re: Importing CSV file with special characters into DSpace.
Hi Fahad, Are you using the "Improt metadata" or "Batch import" method? If using the Batch Import method I would suggest looking at your bte.xml and you will need to use the fields as defined, and in the order defined there (this is the one where you select the type input data). With the Import metadata (where you just upload a csv) then I'm not sure what the the problem is. Personally for CSV imports I would recommend the Import metadata over Batch import. Regards, Genevieve On Wednesday, February 12, 2020 at 12:59:10 AM UTC+11, Fahad Ubaid wrote: > > Asalam-o-Aliakum/ Greetings Ali, > > I am new user of dspace & facing problem in importing metadata from csv > file to the dspace. > > whenever I import a data from csv to the dspace, It change the filed > location for example value of author field goes into the date field, and so > on. For the reference picture is attached. > > can you help me in this regard, > > I am very thankful if you help me > > > > On Monday, March 28, 2016 at 8:40:20 PM UTC+5, Ali Mansoor wrote: >> >> Dear, >> >> Open the CSV file in the notepad & go to the save as option & below their >> is a encoding option then select the encoding to the UTF-8 & save.Upload >> again that csv file in the dspace & see the changes if not then check your >> tomcat server.xml file at the "connector" weather the Encoding has set to >> the UTF-8 or not, if not then set for UTF-8 & restart the tomcat. >> >> >> On Thursday, March 10, 2016 at 8:18:05 PM UTC+3, Xiping Liu wrote: >>> >>> Hello everyone, >>> >>> A few months ago we started a project of cleaning up our electronic >>> thesis and dissertation records from DSpace. We exported our data from >>> Dspace as a csv file and after the cleanup we are ready to import the data >>> back into Dspace. But we noticed that some of the names (accent marks and >>> quotes) in our data are not showing correctly (I am assuming the encoding >>> is not set correctly in the very beginning after we export). But since we >>> have already done our clean up in our file, it will be really painful to go >>> back and re export the file from Dspace (so we can set the encoding >>> correctly this time) and redo all the editing. I wonder is there any way we >>> can correct the encoding after we import the data back into Dspace? Or any >>> suggestions to solve this problem? I have attached a small sample of our >>> data. >>> >>> Your help is greatly appreicated. >>> >>> Xiping >>> >>> >>> -- 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 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/5cf2c6f8-fe4d-4448-b78e-b8c7ced473d9%40googlegroups.com.
[dspace-tech] Re: Deploying dspace7 server webapp failed
My first question would be have you checked the logs (starting by looking at the tomcat server logs, probably one of the catalina files)? Is anything not starting up/are there errors occuring here? Do you have Solr up? Also what do you mean by 'It didn't display the expected page', what were you expecting and what did you get? I used Technique A on Windows and that worked. Also as a tip when you get to it, to get the different entity types e.g. Publication or Person rather than the default, then you need to set the relationship.type to an appropriate value to get for example a person's name in search result list. On Tuesday, 23 June 2020 00:56:40 UTC+10, Abeer El-Aydi wrote: > > I am new to dspace. > I followed the steps of backend installation documentation to install > dspace7 byta2 on ubuntu 18.0.4. > > https://wiki.lyrasis.org/plugins/servlet/mobile?contentId=183076533#content/view/183076533 > > > In step 10, I copied the server webapp to tomcat webapp folder, and > restarted tomcat, then I visited http://localhost:8080/server/; it didn't > display the expected page, I did all steps again, it is still not working. > I can't identify the problem. -- 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 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/258e24e5-9850-43d0-8649-44713e9da3c8o%40googlegroups.com.
