Bulk UI updates #4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "updates"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This takes the changes in https://hub.psychoinformatics.de/www/pool.psychoinformatics.de-ui of the past two weeks in bulk. @jsheunis I would be greatful if you could give this a quick skim
@ -18,3 +18,3 @@cp favicon.ico $(DIST_DIR)/favicon.icocp *logo* $(DIST_DIR)/cp templates/* $(DIST_DIR)/cp -r templates/* $(DIST_DIR)/this should be
cp -r templates $(DIST_DIR)/if we're going to use the same pattern as psyinf poolthx!
@ -16,2 +15,4 @@url: templates/DocumentUploadTemplate.ttlFrontPageHTML:url: frontpage.htmlDOIWizardTemplate:It's probably a good idea to use a single convention for file naming regarding cases. I started using pascal case initially because that's a thing in Javascript, and @mih used the dashes. I am not married to either, but I think we should select one and stick with it. The dashes do look a bit easier on the eye.
This would affect several config options but also filenames.
I've picked the pascal case (and learned this term today)
@ -18,0 +18,4 @@DOIWizardTemplate:url: templates/DOIWizardTemplate.ttlDOIlogo:url: images/DOI_logo_24.svgAfter I added this line and the logo to the psyinf pool repo, I moved the logo also to https://hub.psychoinformatics.de/datalink/assets/src/branch/main/shacl-vue/DOI_logo_24.svg, and in TRR379 pool I reference that link. So that we don't have to distribute the same logo everywhere. So I think we can do the same here, i.e. same as
hub.trr379.de/q02/pool.v0.trr379.de-ui@3647a04bd3/config.yaml (L78).This means the images directory can be removed and the copy command can be removed from the makefile
thx, done!
@ -54,0 +79,4 @@# pattern:# default:template: content:DOIWizardTemplateFileUploadWizard:Looks like an indentation typo here
thx for spotting that!
@ -54,3 +100,4 @@- FileUploadWizardhide_classes:- https://concepts.datalad.org/s/demo-rse-group/unreleased/XYZDistribution- https://concepts.datalad.org/s/demo-rse-group/unreleased/XYZDataTypethese two can be removed because they're still using the rse-group namespace (so they are doing nothing). First one shouldn't be replaced because the XYZDistribution class doesn't exist anymore. Whether you specifically want to hide XYZFile (the replacement) is up to you.
sorry, can you say concretely which can be removed? The webui places your comment such that is looks like it is about the first two items among the five. But I infer that https://concepts.datalad.org/s/demo-rse-group/unreleased/XYZDataType and https://concepts.datalad.org/s/demo-rse-group/unreleased/XYZPublicationVenue shall be removed, and convention and competitionType kept?
Yeah that is definitely a weird web ui thing. I was talking about :
@ -23,0 +14,4 @@dlthings:distribution_of <{pid}>;dlthings:byte_size "{size}"^^xsd:nonNegativeInteger;dlthings:attributes _:n0-1._:n0-1 a dlthings:FlatAttributeSpecification;I think this is outdated. The
FlatAttributeSpecificationdoesn't exist anymore in the ri schema.Actually, looking at the schema it shows that a XYZDocument has a
distributionsslot, which means with the current configuration thefile-uploadwizard would render for it. So this documentupload thing might not even be necessary, unless there is a reason via a specific user workflow that you think it's necessary?no, not specific reasoning at all. I was copy-pasting
the webui again makes it difficult to guess what exactly can be removed.
This part, or more?
I think we should remove the whole template. And then argue from the POV of a specific required use case whether a
DocumentUploadTemplate(the way it was initially implemented, with theCommunicationassociation class andKeyInfoRoleandgitAnnexUploadannotations) is still necessary or whether it would be better to use the more generic file upload wizard approach that was implemented recently.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.