Open mrovnanik opened 1 year ago
the table mentioned in https://github.com/ufal/clarin-dspace/pull/1025#discussion_r1106098915 (but without the color coding). I've added my comments into the last column. IMO there's bit more to discuss; if v7 offers some of the functionality out of the box, it should be mentioned so we know it's not "lost". E.g. reserve.pid.on.start
or alternative.license
5.* | 7.2. | Comments by OK | |
---|---|---|---|
lr.pid.service.type | lr.pid.service.type | ||
lr.pid.service.url | lr.pid.service.url | ||
lr.pid.service.user | lr.pid.service.user | ||
lr.pid.service.pass | lr.pid.service.pass | ||
lr.pid.service.testPid | NO | Is there some other way to test the EPIC pid setup? E.g., are the credentials working, and can we modify a target of a handle? | |
lr.help.mail | lr.help.mail | ||
lr.help.phone | lr.help.phone | ||
lr.harvestable.assetstore | NO | Probably ok for now; afaik not used | |
lr.ignore.notFound | NO | ||
lr.errors.emai | NO | ||
lr.errors.ignore | NO | ||
lr.login.welcome.message | NO | ||
lr.login.welcome.message.ignore | NO | ||
lr.download.email.cc | NO | We need some way to do this | |
lr.download.email.cc.hamledt_3.0_license_terms | NO | ||
lr.download.email.cc.agreement_on_the_use_of_data_in_qt21 | NO | ||
lr.download.email.cc.agreement_on_the_use_of_data_in_qt21_ape_task | NO | ||
lr.pid.community.configurations | lr.pid.community.configurations | ||
lr.pid.resolvemetadata | lr.pid.resolvemetadata | ||
reserve.pid.on.start | NO | We need this | |
lr.autocomplete.on | NO | how do I configure custom solr fields; static json for languages? | |
lr.autocomplete.solr.url | NO | ||
lr.autocomplete.json_static.url | NO | ||
lr.download.all.limit.min.file.count | NO | download all zipped? | |
lr.download.all.limit.max.file.size | NO | ||
lr.download.all.alert.min.file.size | NO | ||
lr.upload.file.alert.max.file.size | spring.servlet.multipart.max-file-size and spring.servlet.multipart.max-request-size | ||
lr.cron.user | NO | ||
lr.curation.handle.correction | NO | not sure; some sort of handle correction called from ItemHandleChecker | |
lr.metaqa.max.processed | NO | CP metadata QA functionality | |
lr.extrametadata.required.check.col.ids | NO | Maybe…I don't think there are required metadata in the extrametadatastep atm; is there even extramdstep in 7? | |
lr.allow.edit.metadata | NO | list of collections where item owners/submitters can edit metadata of published items. AFAIK this was a requirement for LRT, not sure how much it's actually used | |
lr.xmlui.user.showlanguage | NO | ||
lr.shibboleth.log.path | NO | ||
lr.shibboleth.log.defaultName | NO | ||
feeds | discojuice.feeds | ||
rewriteCountries | discojuice.rewriteCountries | ||
NO | discojuice.refresh | ||
lr.shibboleth.discofeed.url | shibboleth.discofeed.url | ||
lr.aai.url | NO | It is in the aai.js | |
lr.harvester.info.url | NO | clarin/vlo results page; should check our items are there | |
lr.default.eperson.language | NO | ||
lr.default.eperson.language | NO | default.language | |
lr.metadata.hide.local.*.* | NO | don't know | |
lr.webui.submit.submitted.limit | NO | show this many previous submissions | |
lr.utilities.db.url | NO | ||
lr.utilities.db.username | NO | ||
lr.utilities.db.password | NO | ||
lr.post.error | NO | xmlui error handler; depends if the errors are displayed in some other manner | |
lr.item.viewer | NO | don't know | |
lr.license.agreement | NO | ok, at this point disabling licenses makes no sense | |
lr.scope.recognition | NO | from shibboleth probably not used | |
lr.shibboleth.name.acceptation.allowedEmailTemplate | NO | TEST shibboleth email validation and splitting | |
lr.shibboleth.name.acceptation.allowedEmailTemplateSeparator | NO | ||
lr.shibboleth.name.conversion.inputEncoding | NO | What are the reasons for dropping the conversion? | |
lr.shibboleth.name.conversion.outputEncoding | NO | ||
lr.tracker.enabled | matomo.track.enabled | ||
lr.tracker.type | NO | ||
lr.tracker.api.url | NO | ||
lr.tracker.api.auth.token | matomo.auth.token | ||
lr.tracker.oai.site_id | matomo.tracker.oai.site_id | ||
lr.tracker.bitstream.site_id | matomo.tracker.bitstream.site_id | ||
lr.statistics.api.url | statistics.cache-server.uri | ||
lr.statistics.api.mode | NO | if the mode is dropped is there only one implementation (the one using the cache server) | |
lr.statistics.api.cached.url | NO | ||
lr.statistics.api.auth.token | NO | ||
lr.statistics.api.site_id | NO | ||
lr.statistics.report.path | NO | is the pdf reports functionality still available? | |
lr.statistics.show_last_n | NO | ||
lr.lindat.logo.mono | NO | ||
lr.statistics.keep.reports | NO | ||
lr.curation.metadata.checkrequired.ignore | NO | ||
lr.link.checker.user.agent | NO | ||
lr.link.checker.connect.timeout | NO | ||
lr.link.checker.read.timeout | NO | ||
featured.services | featured.services | ||
featured.service.kontext.fullname | featured.service.kontext.fullname | ||
featured.service.kontext.url | featured.service.kontext.url | ||
featured.service.kontext.description | featured.service.kontext.description | ||
featured.service.pmltq.fullname | featured.service.pmltq.fullname | ||
featured.service.pmltq.url | featured.service.pmltq.url | ||
featured.service.pmltq.description | featured.service.pmltq.description | ||
featured.service.teitok.fullname | featured.service.teitok.fullname | ||
featured.service.teitok.url | featured.service.teitok.url | ||
featured.service.teitok.description | featured.service.teitok.description | ||
shortener.enabled | NO | if you can't disable the shortener, how do you set the other variables? Blacklist all and leave the shortener.handle.prefix empty? | |
shortener.handle.prefix | shortener.handle.prefix | ||
shortener.post.url.blacklist.regexps | shortener.post.url.blacklist.regexps | ||
shortener.post.host.whitelist.regexps | shortener.post.host.whitelist.regexps | ||
shortener.post.host.blacklist.regexps | shortener.post.host.blacklist.regexps | ||
shortener.post.error | shortener.post.error | ||
license.alternative.path | NO | How do you show the translation of deposition license? | |
license.show_localized_explanation | NO | ||
XSendFileHeader | NO | If dspace+tomcat behaves normally while serving huge files, can resume downloads etc. this should be ok. | |
XSendFilePathPrefix | NO | ||
ufal.build_time | NO | ||
description.institution | NO | These are used in the TOS template | |
description.location | NO | ||
description.country | NO | ||
description.city | NO | ||
NO | authentication-shibboleth.clarin.custom.groups | ||
role.ufal.mff.cuni.cz | authentication-shibboleth.role.ufal.mff.cuni.cz | ||
default.auth.group | authentication-shibboleth.default.auth.group | ||
role-header.ignore-scope | authentication-shibboleth.role-header.ignore-scope | ||
role-header.ignore-value | authentication-shibboleth.role-header.ignore-value | ||
role-header | authentication-shibboleth.role-header | ||
header.entitlement | authentication-shibboleth.header.entitlement | ||
header.unscoped-affiliation | authentication-shibboleth.header.unscoped-affiliation | ||
NO | webui.submit.distribution.license.required | ||
NO | bitstream.download.token.expiration.days | ||
NO | delete.big.file.after.upload | ||
NO | rest.properties.exposed |
@kosarko you asked how do I configure custom solr fields; static json for languages?
in the lr.autocomplete.on
. I think the properties lr.autocomplete.json_static.url
and lr.autocomplete.solr.url
is not needed.
lr.autocomplete.json_static.url
: instead of defining autocomplete values in the json you can use vanilla dspace autocomplete feature in the way that you define suggestion values as a vocabularies e.g., https://github.com/dataquest-dev/DSpace/blob/dtq-dev/dspace/config/submission-forms.xml#L1538lr.autocomplete.solr.url
: autocomplete suggestions are loaded as metadata values from the current metadata field e.g., author
suggestions are loaded from the dc.contributor.author
,.. You can also configure from which metadata field should be loaded the suggestions e.g., dc.contributor.author
.Do you think the lr.autocomplete.json_static.url
and lr.autocomplete.solr.url
properties may be ommited?
@kosarko could this issue be closed?
lang_codes.txt
Unfinished conversation about lr.extrametadata.required.check.col.ids
OK: Maybe…I don't think there are required metadata in the extrametadatastep atm; is there even extramdstep in 7?
Answer: Extrametadatastep is defined in the DSpace7 item-submission.xml
, but it's never used - only in tests.
We identified these items as those that need further discussion. As of 20/02/2023, these are not supported.