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

Review all the roles of the Ontology to see if they belong to the correct module #727

Open
AchillesDougalis opened this issue Dec 11, 2024 · 0 comments
Assignees
Labels
act: for internal discussion it needs to be discussed within the team module: none no module in particular because the issue is of technical or documentation nature type: feature request something requested to be implemented in a future release
Milestone

Comments

@AchillesDougalis
Copy link
Contributor

AchillesDougalis commented Dec 11, 2024

Most of the roles in the Ontology are part of the ePO core module, but if these roles do not appear in any relations of the core module, then they should be moved to a module where such relations exist. The same applies for the rest of the roles and modules.

Note that if a role should be moved to another module, then the role's prefix should reflect this change. For example, if role epo:X that is part of epo core should be moved to eCatalogue then it should become epo-cat:X. The newly moved role should also appear in the "roles" diagram of that module.

An exception to the movement of the roles is that if a role that is part of a module other than core appears in other modules as well, then it should be moved to core, even if it would not appear in any relation in core. For example, if epo-acc:Y that is part of the eAccess module also appears in a relation in the eSubmission module, then it should be moved to epo core.

See ePO's Modular Approach on the Guide to the ePO Modules for more information on modules.

@AchillesDougalis AchillesDougalis added type: feature request something requested to be implemented in a future release act: for internal discussion it needs to be discussed within the team module: none no module in particular because the issue is of technical or documentation nature labels Dec 11, 2024
@AchillesDougalis AchillesDougalis added this to the 5.0.0 milestone Dec 11, 2024
@AchillesDougalis AchillesDougalis self-assigned this Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
act: for internal discussion it needs to be discussed within the team module: none no module in particular because the issue is of technical or documentation nature type: feature request something requested to be implemented in a future release
Projects
None yet
Development

No branches or pull requests

1 participant