ATTENDEES: Wendy, Jon, Darren, Flavio, Dan, Oliver, Christophe, Jared, Jeremy AWS and Drupal site interaction and support
Recap: some sections will move to AWS (specifications) remaining will be moved to wordpress
Is it wise to split this down the middle and move to 2 sites. This might be difficult to split correctly and to maintain in the future.
--Is it possible to move everything to AWS? How complex might this be to maintain and supervise
--Need to move away from Drupel as it is not supported by ICPSR and want to move it to a vendor
--Fee for moving it over and an annual maintenance amount ($3-4,000 a year)
--Urgency because support for their version of Drupal had gone away, did get year's reprieve
--In the mean time the AWS option arose and discussion of how
--Lots of static content that would just be moved
--Some functinality - bibliography that is maintained in an ongoing basis; posting news etc.
--Happy if it did not got to vendor
--Can we support on-going posting and maintenance
--If not, we can still go to WordPress keeping basic content there and other on AWS Current view of what goes to AWS:
(1) Content under the following virtual URLs will be moved to the new UMich AWS instance
https://ddialliance.org/Specification/* - static content
https://ddialliance.org/products/* - static content
https://ddialliance.org/learn/resources - single static web page
https://ddialliance.org/learn/resources/ddi-profiles - single static web page
https://ddialliance.org/resources/tools - single static web page with filter
o Also move relevant referenced items under https://ddialliance.org/tool/*
https://ddialliance.org/learn/markup-examples-by-version?field_ddi_product_tid=All
o Also move relevant referenced items under https://ddialliance.org/sites/default/files/*
At the root level under http://ddialliance.org .
o https://ddialliance.org/Tables.dtd - downloadable document --Clean up even before vendor
--Hidden stuff would not move and Darren's list may include that --Splitting may have unintended consiquenses such as loss of database functions (publications, examples, etc.)
--Do we need all the functionality that is there (examples etc.) - if we add in with the vendor --Would the options we are looking support these --Issue about having to shadow the brand and sync it between 2 sites and with a 3rd party vendor --What potential costs there would be with backup etc. - there is still need for web support (not completely volunteer) --It seems to me that we are missing a written target sitemap (whether we have one or two platforms) that would guide the specifics of the migration. --Could we take a few weeks out to design what we want the site to look like
Include Training Group
We have a current website that needs a spring clean but we have no idea what it should look like
Can we take 4 weeks to say this is where we want to end up (google doc) - we don't have much written down on this at the moment
Drupal to WordPress is somewhat automated there is also a lot of sorting and hand work to make the move. https://docs.google.com/spreadsheets/d/1y54OKTmJeSV3YwxR6RBa7yJyHvD8P1drjPmG4C2vZoM/edit#gid=517461823
Lists out the sections and owner groups
Detail gets complex in the products sections
Resources has some sections
What exactly do we have - can we flatten it out?
ACTION:
We should look at what we want rather than just what we have
Create small group to look at this: Jared(co), Jon, Darren (co), Wendy CDI technical review kickoff
Flavio looked at it
No draft of production process review issues - get from Arofan (send him a draft of request and list of people we've identified)
Automation is still lacking so how is that evaluated
We did write to them some time ago regarding - dig out letter we sent to them and verify all the parts are there
Asking more information on production process itself; make sure its available
Jon will look next Friday Funding requests
see google sheet: https://docs.google.com/document/d/111V1om6vbaJQCgxYI_znA03xDWW9HwW0iMGHxNVVnHU/edit?usp=sharing Workplan for coming year
Review workplan for tweaks Updates on feedback for DDI LIFECYCLE V.4.0 BETA
No only had one piece of feedback from Romain
BETA 2 would be good to do when we have the ordered flags
|