Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#3214: new field approved usage #3275

Merged
merged 17 commits into from
Jan 22, 2024
Merged

#3214: new field approved usage #3275

merged 17 commits into from
Jan 22, 2024

Conversation

ewolf47
Copy link
Collaborator

@ewolf47 ewolf47 commented Nov 24, 2023

A new filed has been added to the datapacke form and detail page. The new field was also added to the filter

return "data-package-management.common.approvedUsage.nonCommercialUse"
case 'COMMERCIAL_USE':
return "data-package-management.common.approvedUsage.commercialUse"
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bräuchte es hier noch einen default case mit einem console log?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ich bau es mal mit mein. Aber prinzipiell können hier eigentlich nur die Fälle auftreten, die hier definiert sind.

case 'NON_COMMERCIAL_USE':
return "data-package-management.common.approvedUsage.nonCommercialUse"
case 'COMMERCIAL_USE':
return "data-package-management.common.approvedUsage.commercialUse"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

analog

md-floating-label="{{'data-package-management.detail.label.approvedUsage' | translate}}"
md-input-maxlength="512"
md-input-name="approvedUsage"
md-is-error="!dataPackageForm.approvedUsage.$valid && (dataPackageForm.approvedUsage.$dirty dataPackageForm.approvedUsage.$touched) "
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hier fehlt noch ein Operator? bspw. OR

Suggested change
md-is-error="!dataPackageForm.approvedUsage.$valid && (dataPackageForm.approvedUsage.$dirty dataPackageForm.approvedUsage.$touched) "
md-is-error="!dataPackageForm.approvedUsage.$valid && (dataPackageForm.approvedUsage.$dirty || dataPackageForm.approvedUsage.$touched) "

md-floating-label="{{'data-package-management.detail.label.approvedUsage' | translate}}"
md-input-maxlength="512"
md-input-name="approvedUsage"
md-is-error="!dataPackageForm.approvedUsage.$valid && (dataPackageForm.approvedUsage.$dirty dataPackageForm.approvedUsage.$touched) "
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

analog

@@ -197,7 +200,9 @@ angular.module('metadatamanagementApp').config([
'study-series': 'By which study series do you want to filter?',
'institution': 'By which institute do you want to filter?',
'sponsor': 'By which sponsor do you want to filter?',
'survey-method': 'By which survey method do you want to filter?'
'survey-method': 'By which survey method do you want to filter?',
'approved-usage': 'By which special restrictions for the data use do you want to filter?',
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bin mir bei dieser Englischen Übersetzung nicht sicher...vielleicht According to which special restrictions for the data use would you like to filter? oder What specific data usage restrictions would you like to filter by?; 'approved-usage-list' analog

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ich habe mich hier an den anderen labels orientiert. Die sind alle nach dem Schema:
"By which <filter type> do you want to filter?"

Würde es daher mal so lassen.

@ewolf47 ewolf47 merged commit 09ecbd1 into dev-2023-2-1 Jan 22, 2024
2 checks passed
@ewolf47 ewolf47 deleted the ewolf47/issue3214 branch January 22, 2024 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

As a data user I would like to have a new attribute for approved uses
2 participants