Skip to content

Combine dkan and metastore modules #4413

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

Open
dafeder opened this issue Feb 19, 2025 · 0 comments
Open

Combine dkan and metastore modules #4413

dafeder opened this issue Feb 19, 2025 · 0 comments

Comments

@dafeder
Copy link
Member

dafeder commented Feb 19, 2025

Continuing the work laid out in #3746, we do not need separate a module for "metastore". There is no DKAN w/o the metastore. One #4412 is complete, merge "metastore" into "dkan" as well.

Acceptance criteria

  • Metastore services can maintain the same name. It is fine for them to be prefixed with dkan.metastore.
  • As appropriate, move Drupal\metastore namespaces into Drupal\dkan root or Drupal\dkan\Metastore. More discussion needed to determine what goes where here.
  • Of course, upgrade path. Table names should not change but there will likely be some update hook magic needed for this to be smooth. Documentation for custom code integrations refactor a must.

More discussion needed to finalize sequence of merging/release here. Should this and #4412 merge into a 3.x branch that we maintain in parallel? Can this be released under 2.x as it doesn't technically add or rename any modules?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants