...
2022-2023 Minutes Page, 2020-2021 Minutes Page, 2018-2019 Minutes Page, 2016-2017 Minutes Page, Pre-2016 Minutes Page
| Expand |
|---|
|
ATTENDEES: Wendy, Jon, Darren, Flavio, Christophe, Dan Pages from Alliance site We need to clarify what is moving from the current alliance site before it shifts to WordPress The Alliance wants to keep this site a simple as possible and there are currently some pages under LEARN/Resources that have underlying databases The majority of content we are looking at is static and is under Products Everything that is under Specification is easy but need to determine what needs to be moved The real question is about being able to identify specific nodes that can be handled by the remote site (RDF resolution system and CV services on UKDA site plus new DDI Alliance AWS space) One possible way is just a lift and shift move all the /Specification Landing page on WordPress site and then it sends you off to other system What Darren needs is a site map (node list) so he knows what gets moved
Specific questions: docs.ddialliance.org - what is this intended to provide Currently we have a number of official documents associated with specifications that provide access to documentation such as field level documentation and high level documentation These are static sets and can be moved If it is difficult to tease out the nodes it may be possible to support static content under Products - all of this content is managed by TC
Resources: Tools, examples, profiles currently have underlying databases and we would like to retain this functionality These items are more in line with the products and it may be optional to move them under the Products umbrella. Learn could still retain a page that would describe and link to these resources To accomplish this we need to locate a workable opensource tool to manage search and display of these databases. TC will begin this search
Agency registry: ACTION ITEMS: Obtain site map (node list) Transfer page listing for move to Jared’s spreadsheet Determine content that must move to retain or add functionality or to just support easy division of contents for routing Clarify who will physically be doing the set up on the AWS configuration Identify an open source tool to support access to database content for tools, examples, and profiles Determine consequences of moving content to alternate site based on node divisions proposed
|
| Expand |
|---|
|
ATTENDEES: Wendy, Jon, Oliver, Darren, Dan
APOLOGIES: Flavio 1-Codebook pull request
ok and merged 2-Funding requests (Deadline is 26 of April) Face-to-Face again Infrastructure costs - flag and could suggest it should be a regular budget line; software contingency budget as well as on-going costs 10K last year was infrastructure contingency from which a couple of months of AWS Alliance pays Colectica and this will move to AWS at some point
As part of the move to AWS a bit of work needs to be done to convert from zone file to AWS (route 53) - Dan will write up Admin data meeting - talk to Flavio about meeting next year; funding request
3-Strategic Plan
Looks good - no questions or specific concerns from TC members at meeting 4-Administrative documents
Not ready for discussion 5-CDI submission to TC and production process review
Darren talked with Arofan about RDF URLs and everything is in line Other: CV work is done ready to make the change after confirming a few minor points with ICPSR and the CV group
https://ddicv.ukdataarchive.co.uk/ new format for the CV page (domain to be changed obviously) No ISI proposal but will look at the IAOS conferences coming up
FUTURE:
No Oliver until April 18
No meeting on 11th due to COSMOS conflict |
...