Need Syntax for Updating JVM options for bagit

[Sherry Lake]

Good morning,

UVa upgraded to V6.2 last week and now I need to update our bagit customizations (I think....).

According to the V6.2 documentation bagit metadata (name/address/email) is now customized in domain.xml with new JVM options.

https://guides.dataverse.org/en/latest/installation/config.html#configuring-bag-info-txt

First question - we have these customized in Bundle.properties, but can I assume that those will no longer work and we must put them domain.xml?

What is the syntax for the asadmin command to add them to domain.xml?

Thanks,

Sherry Lake

UVA Dataverse - LibraData

[James Myers]

Sherry,

Yes – looking at the code, there’s no backward compatibility to keep using the Bundle.properties entries. The code to add these (and any JVM/microprofile entries) via asadmin is of the form shown in https://guides.dataverse.org/en/latest/installation/config.html#jvm-options :

 

bin/asadmin create-jvm-options  -Ddataverse.bagit.sourceorg.name=<Org name>

 

(Quotes are needed if your value has any characters that would be interpreted by your shell.)

 

You’ll need to restart Payara for the new settings to go into effect.

 

-- Jim

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/5cc9bf5d-d31b-478e-a0de-dfb7635f9975n%40googlegroups.com.

[Philip Durbin]

Right, the properties file is no longer supported:

"For BagIT export, it is now possible to configure the following information in bag-info.txt. (Previously, customization was possible by editing `Bundle.properties` but this is no longer supported.) For details, see https://guides.dataverse.org/en/6.1/installation/config.html#bag-info-txt "

From https://github.com/IQSS/dataverse/releases/tag/v6.1

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/SN6PR19MB2271AC3C9D87B9DC3B1C3C1DBFCD2%40SN6PR19MB2271.namprd19.prod.outlook.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Sherry Lake]

Thanks Jim and Phil,

I finally had time to do our quarterly bagging (of latest datasets only). Everything worked great!

I added the metadata (bagit info properties) as JVM options and that worked fine.

But.... you know there was a "but"

there is a WARNING in the log file about missing "key" in the bundle file - so even though not being used... the bagit routine is still looking for this one entry "bagit.sourceOrganization" in the bundle file. That entry was added to the JVM options and the Source-Organization is in the bag-info.txt file, so all is good. Just an FYI:

[2024-07-10T14:34:32.955+0000] [Payara 6.2023.8] [WARNING] [] [edu.harvard.iq.dataverse.util.BundleUtil] [tid: _ThreadID=19211 _ThreadName=Thread-57] [timeMillis: 1720622072955] [levelValue: 900] [[
  Could not find key "bagit.sourceOrganization" in bundle file: ]]

--

Sherry

[Philip Durbin]

D'oh! You're right, there it is:

src/main/java/edu/harvard/iq/dataverse/util/bagit/BagGenerator.java
879:        String catalog = BundleUtil.getStringFromBundle("bagit.sourceOrganization") + " Catalog";

Sherry, if you're inclined to open an issue about this, I'd appreciate it!

I think the fix is to use this instead...

String orgName = JvmSettings.BAGIT_SOURCE_ORG_NAME.lookupOptional(String.class).orElse("Dataverse Installation (<Site Url>)");

... but it'll take a little study. It has something to do with what's shown under "Internal-Sender-Identifier".

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/8f57333f-ccb3-4d09-a1f5-ccf867e52aa4n%40googlegroups.com.

[Sherry Lake]

issue created 

https://github.com/IQSS/dataverse/issues/10680