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

Define architecture #162

Open
sherakama opened this issue Mar 28, 2018 · 3 comments
Open

Define architecture #162

sherakama opened this issue Mar 28, 2018 · 3 comments

Comments

@sherakama
Copy link
Member

sherakama commented Mar 28, 2018

Define the necessary components in order to make this happen in Drupal 8.
Start by evaluating the functionality in Drupal 7 and then evaluate what is available to expedite the development.

The major functionality included in Drupal 7 includes:

  • Import by organization
  • Import by workgroup
  • Import by sunet
  • Duplication reduction (One content node per person)
  • Authentication Endpoint configuration (with encryption)
  • CAPx API endpoint configuration
  • Data Browser
  • Entity Field Mapping
  • Nested Entity Field Mapping (field collections etc)
  • Data tampering
  • Import filtering
  • Cron + cron frequency & throttling
  • Batch processing
  • Orphan handling (both people and field data)
  • Profile metadata (API ids etc) NODES
  • Entity relationships (to CAPx and other Imported entities)
  • Webauth and SAML mappings
  • Entity edit form field disabling (and ability to override)
  • Entity data augmentation (not all fields locked)
  • Ability to update a single entity from the edit form
  • Views relationships to mappers/importers
  • Imported entities browser
  • Organizations as taxonomy terms
  • Enable / Disable single item syncing
  • Enable / Disable importer
  • Forced update on cron every sync run
  • Etag comparison skip checks
  • File downloading
  • Authentication token caching
  • Exportable configuration
  • Granular(ish) permissions
  • Dumb skip field errors.
@sherakama
Copy link
Member Author

After having talks with @boznik and @pookmish the migrate module will be able to power the core of this new version. Additional plugins will have to be written and modules/services to extend and create the configuration entities required for the Migrate module to do its thing but this will get us the heavy lifting we had write in the Drupal 7 version.

@sherakama
Copy link
Member Author

sherakama commented Mar 28, 2018

screen shot 2018-03-27 at 10 53 32 pm

Source: https://docs.google.com/drawings/d/1CdwaO9LzQr1D5zqFjCO-s8__dc8bd7VBn7b02Q_Kx2E/edit?usp=sharing

Building session outcome. See source link for additional comments and details.

@sherakama
Copy link
Member Author

CAPx will provide APIs or helper services/classes that will generate the configuration entity that migrate with migrate_plus will use to fetch and save profiles from the API.

Authz module will likely piggy back off of the key module to provide the oauth authentication credentials that are needed for migrate to communicate with the api.

@sherakama sherakama modified the milestone: 8.x-1.0-alpha1 Apr 6, 2018
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

1 participant