Well thank you everyone for coming today. I hope that those of you who are joining us are excited about learning more about our book and to talk more with the case study authors and lead authors that we're working with today. So introduce yourselves in the chat have a good time and I'm going to get started with sort of an introduction to what this book is and why we are talking about it here today with everyone. So first what is the OER start a kit for program managers? Hopefully some of you already know if you're here today but who knows. This book is was created to sort of bring attention to the level and breadth of work involved in building and managing an OER program. It contains 22 chapters and eight case studies so and I saw it 30 which addressed different aspects of open education work broken into seven major sections a quick guide to open ed building a program program management training and professional development supporting OER adoption supporting open textbook creation and collecting and reporting data on your program so sort of going through all of the little bits and pieces that make up doing open education work at a program manager level. For a little bit of a peek behind the scenes this book has been going on for now three years of development in 2019 I think it was fall we first came together with our lead authors to sort of come up with what the idea of this book would be and we collaboratively outlined all the different sections we wanted to be in this book. I'm going to wait a second as she joins the meeting but Stephanie Buck was really one of the lead thought leaders behind this work and without her sort of drive for we need to make sure to include these specific sections I don't think it would have turned out as in depth and as helpful resource as it is today so huge shout out to Stephanie for being amazing. During the 2019 and 2020 years we identified additional authors to develop case studies and put out sort of the first draft of what we would be putting together and then over 2021 and 2022 we did an open call for peer viewers and copy editors to look over the book I think probably the biggest piece of this was the 86 peer viewers some of you in the chat today who were assigned to different aspects of the book to really look it over and give us feedback on what needs to be tweaked here so it was quite a lot of people who had hands in this project and really helped to drive it into where it needed to be I want to also shout out Cheryl Casey who cannot be here today because of other issues but she was a huge huge lift and when it came to copy editing she has a lot of background in that work and even during the peer review process she caught so many little things that otherwise would have fallen through the cracks. So in 2022 during the spring we've been working on final edits importing depressed books working on the final formatting and design work and doing the book cover for the final publication so it's taken a couple of months but we've finally got it all together and here is where we are okay so before we get into more of the fun Q&A discussion bits I want to talk a little bit about how to use the book in your own work so it was primarily developed as a reference source something you can refer to when you're thinking about approaching a new project or practice at your institution there are a few other ways you can use it in your own practice too like supporting training for peers and new hires or communicating what is the scope of your work to an administrator or supervisor who might not understand oh here's a 30 chapter book about the level of work that I'm doing guys this might help you but there's a lot of different ways to potentially use the book in your own work and so what I'd like to ask you all now is what's another way you hope to use this book in your professional practice feel free to raise your hand if you'd rather unmute or to post it in the chat Amanda hi I'm really looking forward to being able to incorporate it into professional development activities for folks who are starting to do this work so I developed a course for KPU that sort of does an introduction to how to support folks who are doing open education work and I would love to add it as a resource to that course to start with a great idea I've heard of folks maybe adding this book to lib guides trying to again orient people who are maybe new to this type of work again it doesn't need to be someone who is a sole program manager but someone who might be involved in these efforts there's a lot of sections on teams in the different departmental roles that help make a OER initiative an OER initiative successful so love that you're already incorporating it into the KPU course and Bahid says they are looking forward to recommending the book or extracts of the book to organizations that want to foster the creation of OER I love that we're thinking beyond the typical college or institution so they are thinking about ministries of education NGOs and so on Jeff is there more that is coming in into the chat that you'd like to highlight well the next one was about so this was from Stephanie Fletcher saying that she's entering the second semester of running a new OER program well welcome and hopes to use this both as a resource for herself but also for the faculty who partner with her to promote OER on campus I think that's a really good point like involving what I would call your champions of which others call advocates etc I think that's really cool also if you're if you're new to the OER programs contact us if you have any questions to them we'd be glad to have getting other ideas to improve the OER initiative yet using it to view OER program through different perspectives neat Paul says shared as a resource in my institution but shared with all participants in an online Caribbean wide course on online learning that's really neat yeah if there are folks you know that are thinking about different ways that they can get invested or interested in ways to support online and distance learning and supporting other kinds of work that's related to open it it might be useful to share a guideline like this or a guidebook like this to help them think about oh this ties directly into OER or the work we're already doing could be partly related to OER as well we could partner with you on making this sort of a broader initiative that supports multiple things like all of you with your great ideas okay so moving on I want to get to the next slide just to give people a little bit of a chance to learn from our chapter in case study authors about what do you most want readers to take away from your contributions to the book so is there something that you think is particularly noteworthy that you'd like them to see or to learn from is there something that a chapter that you contributed to that you're particularly proud of or perhaps for the case study authors a takeaway from your case study that you think oh this is something I really hope that people get out of this when they're reading through it or can think about good morning good afternoon my name is Regina Gong I am the OER and Student Success Librarian at Michigan State and one of the case study authors in this awesome OER so thank you everyone for for attending this launch party so my case study is in the chapter on building an OER program and it's peaks to my experience running an OER program in a community college and now at a land grant R1 University and I think what what I want are readers to not really take away right but to to just understand is the experience of running an OER initiative by librarians that are not really represented in the open space so my perspective as a woman as a woman of color running an OER initiative and also that often not talk about subject of labor most especially invisible labor that comes with doing this this kind of work and so hopefully you know when you when you read this case study and my experience it actually inspires you and also makes you think about even as we run it out of our passion out of our commitment sometimes if the institution is not willing to support the work the work of the most passionate librarian or advocate in this field will not be successful so that's that's all thanks well I did a lot of the data analysis and reporting stuff at the end and I think the big takeaway from it is that you can do it even if you don't have a background in data analysis I sure didn't when I first got started there are some things that you can do to get your OER program started on the on the right foot in collecting that data and being able to answer the big questions that will come at you there it's meant to be absolutely not imposing and shout outs to the peer reviewers who pointed out like the ways in which things could be like configured to be more educational like more process oriented so you'll see step by step stuff in those chapters and the reason why I step by step is that the peer reviewers noticed that I was doing a little bit of it but not enough so I've brought it all together into that framework to make it more of a like entire process step by step thing so yeah it's it's absolutely doable work for sure and yes thank you Regina that is such a cool case study yeah I want to while we're here shout out one person in the chat uh Don Lowe Winstonston who shared I hope people take away that innovation is wonderful and OER is fantastic but to plan when your innovation succeeds her case study three building a roller coaster while writing it is one that really goes into what can happen when things just start running and you have to build as you're going along and make it work and how that can be a major issue that a lot of OER program managers run into as she shares this advice is something I call to mind when thinking of how to start an OER program at the institution I've moved to since writing the case study so that's great to hear about anyone else have anything they'd like to share from their contributions and sections I just want to make this audible from the chat uh Judith Sebesta just shared that the open texas conference is coming up and they are looking for proposals and the theme is the labor of open education so if anyone's interested in that she has the link in the chat so we wrote the chapter the case study on using manifold and we were hoping to give a sense of both what kinds of projects could be possible on a platform or on a platform like manifold what kinds of you know teaching and learning can be supported so we went through a lot of case studies but also what kind of work is involved in supporting this kind of project um from a case study uh from a project manager position and what kinds of pitfalls can can get in the way um because I think yeah if you're prepared for them then they won't get in the way of the cool things that you can do yeah thank you for that uh Christina it was really cool seeing the manifold chapter sort of evolve as that it's for it came together it's a great example of all the different things you can do and with one type of tool and that's built out more throughout the section on publishing and supporting the publication of OER so people can think about what does it take to make a textbook and what are the different options available for making that process work so uh I'll shout out a pro here uh an amazing contribution to that uh of course with her experience uh with the textbook program through the rebus community and Stephanie for all of her work really leading the second half of the books uh sections and making that come together I'm hoping that um at least with the chapters that um I've authored on uh project management folks will walk away with some reassurance that you don't need to have all of the answers right away you don't need to have all of the systems and tools figured out right away but um there's a lot of learning as you go with this work and there is a network and community of support um available to you even if you are the only person trying to bolster these efforts on your campus at your organization in your region um there is a lot of work that you can build off of so you'll see Stephanie um and I point to existing resources and templates that you can adapt and sort of reuse as you need um but there's also um information about um listservs that you can tap into or um ways to build a support network to help you reach your strategic goals and help you um get your program um uh to where you want it to be so that's something I hope you'll walk away with you don't need to know everything right now but use this resource use that particular chapter on project management to to learn and build and I'm wondering Abby would you um mine maybe screen sharing just the book and I know you talked about the seven different parts but we can also show folks who are here and who maybe haven't been part of um building or contributing what's covered in each of the parts what the different case studies um what perspectives those case studies shed light on um and how they can even think about you know switching in and looking at Jeff's sections on collecting reporting data or micro sections on uh cross conversions yeah sounds good can you see it right now or is it stuck in the presenting view okay yeah we can see it I never know with google slides if it's just deciding that it's going to take over the whole screen I'll hang around uh in the second lower section over here and if we have someone speak up I'll hop into theirs I guess okay I've been talking so much but I haven't actually talked about the sections that I wrote so I guess I should say something uh so I wrote a few of the chapters in the beginning of the book about sort of getting started learning more about OER and building out your team and getting started with everything on campus and I think one of the takeaways that I feel like I say this every time I present to someone but the biggest takeaway I have uh that I'd like for people to learn from this is that you should never build something from scratch if you can borrow it from somewhere else so if there are existing templates if there are existing examples that you can build off of and learn from then reach out to people and get their help even if that means it's not someone at your institution it could be someone on an OER listserv it could be someone on social media who you're looking up to as an aspirational person in the space it is always nice to at least reach out and see what they can do for you or if they can share something because you never know if maybe they actually have a whole google folder of templates that they can just send on to you and say do with this what you will it would be nice if that were always the case but it is often the case in the open movement because that is what this is all about is sharing things and learning from one another and building up on what came before so as you're thinking about sort of how you can get started with all of this it's good to think about where people have already done the work and I think that's really well seen in Jeff and I's chapter from that we adapt adapted from the spark open education leadership program their open education primer which I also helped write originally so it's a whole full circle sort of deal but this looks into all the different pieces that can be part of an open education program from workshops and review programs grant programs and all the different little pieces that make up your open education work and then looking at who's done this before how did they make it work and what are the best practices I did want to mention Amy Hopper's case study she's not able to be here today she works for open Oregon educational resources she's the director there she has a case study in the data section that's really cool it's kind of an actionable look at what she's done throughout the state of Oregon and the kind of philosophy behind coming up with an estimate per resource she visualizes the kind of data philosophy stuff and quadrants she's really good at that visual aspect of things you'll see the quadrants there and then you'll see exactly where all of the stuff fits into it and it's really neat and she's very honest about it too she's like here's where I think it's messy but it's supposed to be here's where things can be cleaned up here's what depends on each institution here's something that's more of a global idea so it's really it's a neat one so if you look at my chapters absolutely look at Amy's case study because it's a really awesome take well if we're doing shoutouts I definitely want to shout out Marco Cipherley Valencia who is one of the I guess five editors of this resource hopefully Marco will be able to join for a brief portion of this launch but his chapter on supporting only our conversion building familiarity they're all really excellent and maybe Abby as you're scrolling it's worth noting a few what I think are really interesting features not only about this chapter but the book overall we're really trying to tackle things like misconceptions about this work and as Regina was describing bringing to the surface a lot of the behind the scenes labor that goes into a successful program or a successful project so you'll see Marco talking all about whether it's project management and time but the different stages of course conversion work and different ways in which it can happen at an institution I really appreciated the intentionality with which Marco discussed doing this work equitably not only is it a part of this chapter but it was a key part of our conversations as a project team as we were discussing ideas around the book discussing chapters discussing even workflows and processes so that's something I'm hoping you will be able to find not just in this chapter but throughout the book is a calling to reflect also on how you can make your programs your practices your work more equitable. Yeah I co-authored the building familiarity on campus chapter with Marco and the perspective he brings towards doing things very intentionally on a campus are extremely unique not not something that I would be able to present as someone who does system-wide work so I talk about the environmental skin stuff and how to do it but when it comes to like here are the types of people you will encounter on campus here's what kind of message you can bring to them the OER audiences that's Marco and he does an excellent job there of distinguishing groups that you can't generalize them to the whole talk about assemblage theory and all that stuff but what you can do is start customizing your messages towards those people because like both Abby and Apoorva have said it's about the stuff that's already been done and just kind of building on that we've all encountered various types of audiences and people who are either extremely receptive to the idea of OER they're already doing it which is amazing and then you can get them to do even more and even be leaders and those who may completely reject it too if you're very new to this this may suddenly come as a surprise when you hear these kinds of types of responses but Marco's really set up a nice framework here for how to tell your messaging based on who it is that you're talking to yeah this is a lovely chapter and I do want to point out because we didn't say it before now but if you haven't had a chance to delve into the book there are sections that we made sure to include in every single chapter apart from the case studies which included a conclusion sort of wrapping it up recommended resources which are links out to things that we think might be useful for you if you're interested in the topic of that chapter that might be a book it might be a chapter an article it might be a worksheet or a resource that you can utilize in your own program really depends on the chapter and then key takeaways regarding sort of what's been talked about and what are some things that we want to make sure really resonate with you that you can come back to and look at this chapter in a new light after thinking through what's the big picture here so are there any other case study authors in the field or any other lead authors I know Stephanie you haven't said anything yet we've talked about you a lot but I guess I would say that I hope that the book is useful for somebody who's really new to this and feels like they're doing it alone and that they don't need to do it alone this is a lot of what we put into this book was our experiences so that we suffered so you don't have to kind of thing not quite but you know we we did it because we worked on it and we share our experiences with you so that you can learn from what we did and maybe what we we should not have done so I hope that people will really enjoy using this manual well said yeah I will say I appreciate especially the sustaining OER projects chapter that Stephanie put together it really goes into sort of what it takes to make sure things keep moving forward and how you can continue to support not just the funding but also the overarching making sure things keep moving both for use and reuse of materials making them findable making sure that people are still invested in moving forward and I absolutely adore the technical side of things that maybe are not always at the front of my mind but that Stephanie really brought home throughout the book all right but we'll come back to this little book show and tell in a little bit but for now let's head back to our presentation and the next section which is for you the audience what section of the book were you most excited to find so as we've been looking through it as we've been thinking about the chapters and doing a bit of show and tell or even if you've been reading it in the week up till now is there a specific chapter or piece of content or section that you found particularly exciting to think this exists now Judith says collecting and reporting data yeah Jeff did a wonderful job there I'm excited for all of it building a grant program since that's what we're about to try and put together yeah I'll say it's kind of funny in my side of things because the section I was most excited to see completed and out in the world is one that I wrote but it's in the first chapter about OER talking about remix projects and different kinds of remixes that people can do whether it means you're adapting a piece of work or pulling together multiple things into one new thing because it's a question I see a lot coming up on listservs from people that are new to this and I was excited to just finally have a section I could point to and say there it is I don't have to remember how I explained this last time it's in a book so that was very fun for me Pamela shares I'll show it share the manual and OER presentations with faculty librarians working on affordable learning initiatives thank you and Suzanne notes that they are I'm grateful that the book will serve as a framework for discussions if they're moving from a state funded OER grant to more of a funded grant program that they're going to build and Ryer notes that they like the pieces the very practical pieces of the book on hosting or data collection or project management and marketing yes as we were putting together the outline we noticed that there are so many puzzle pieces to this work that don't often get talked about I know Stephanie and I looked at you know the project management for instructional designers book but there wasn't really one for OER project so we reached out to others we know who had done this work so Anita Waltz shared some of her lessons Eileen Thornton asked us to look at some resources as well and I just you know while folks are thinking and dropping more ideas into the chat I just wanted to flag a note that Marco Cephalia Valenti one of the editors of the book has joined so we'll just pause and give Marco a round of applause for their contributions his contributions to the book as well and welcome Marco oh thank you approval that is too kind can you all hear me right now I'm never know if my yes we can hear you you just missed us talking very excitedly about how much we love all your chapters and how like picking a part our favorite things about your collaboration with Jeff and your own other chapter and all the cool things that you brought that we didn't expect anyone to include sadly but there will be recording so you can read watch it afterwards and see how we talk about you when you're not here and I feel like I just lost your audio Marco try talking for us one more time let's try that now can you hear me there you go okay perfect I I'm one of those folks who's resisted the we lost you again Marco post it in the chat we'll read it out for you healthy notes that they are excited about the building the roller coaster well righty get chapter building the plane while flying it a lot of different metaphors would work to describe the experience and I know Jeff you've been having a conversation with Leo about how perhaps given the roles of a lot of us as contributors and authors of the book we tend to be maybe more focused on the regions in which we work which happens to be US and Canada for the most part but we would definitely love perspectives outside of North America because the education systems in different parts of the world are so different do you want to tell us a little more about that discussion well yeah I mean if you're reading this and you're coming from any other place than the United States you might have a very different take on the price of textbooks and things like that for example I went I once presented to folks in Paris about our program and it's a different kind of message there when they're thinking about open education they want to share their culture they want to share their ideas it's it's helpful for them to help people outside of their region but when it comes to textbook affordability it's not really a big thing that stuff is priced differently there it is subsidized in a different way there so what I usually talk about with data didn't really make much sense so I had to kind of shift it in that way so I think contributions from people who are outside of North America would really help in building and improving instructional resources like this for sure I think that was the one thing that at the end of the process I thought oh I wish we'd done this originally which was an open call for case study chapters and an open call for co-authors but then I feel like we'd have a 56 chapter book so pros and cons but definitely there's room for improvement and even more inclusion and whatever comes next yeah maybe volume two we'll see yeah I think after three years working on this book the lead authors especially could could stand to take a short break from book level projects thank you Cara yeah I've been very used to managing projects where other faculty are writing open textbooks and that's really cool but now authoring chapters of it and going through the peer review process and then revising based on peer review recommendations doing the copy editing like that's stuff we do with the University of North Georgia pressed and being on the other side of that is eye opening like this it takes a lot of time oh yep and yeah Leo's talking about the cost of textbooks has become much bigger issue during the pandemic libraries were needed to oh buy access to ebooks and there was a massive increase in need publishers jacked up the prices oh that's an e-book thing yeah the oh boy thank you Leo for mentioning the e-book SOS issue if you want to talk about it on twitter it is hashtag e-book SOS but there's a lot going on with regard to libraries being asked to purchase e-book collections or unlimited user e-books which are often incredibly expensive compared to their traditional textbook counterparts in order to fulfill a class's needs and in some cases not even having the ability to order them it's another aspect of this whole ecosystem we live in it definitely is and you know I'm going to say as Dr. Epa was asking in the chat you can browse through the different sections of the book online you can also download it in a variety of different formats for you to read but I might segue us maybe to the the next section of our hour together and rely on Judith and Amanda to do that so Judith flagged in the chat that you know for her this book is just so validating and it's proof that many of us are grappling with the same challenges and some creative and innovative solutions to meet these challenges that she's seeing a lot of those ideas in the book throughout so if you have questions if you have challenges now's your time to ask it and Amanda asks in the chat Abby how does it feel to have gone from the OER Starter Kit which is an excellent guide that I would recommend to all of you to the workbook that was co-authored with Stacey Katz who is on the call to this larger iteration for a slightly different audience. Posting link for those who don't know about the original Starter Kit but yeah so it's it's been weird in part because of the difference in coordination across the three so when I did the original OER Starter Kit the idea was to put together a very short easy handbook for faculty that need help getting started with OER but don't have someone like me to help them through it and just need like some sort of structure to figure out what they're doing and so I did it a lot on the weekends by myself over the summer whenever I had free time and it also sort of came together no one else knew I was working on it there was no rush and then doing the workbook with Stacey it was a little bit more structured it was working alongside someone else divvying up who's working on which chapters what we're creating what the purpose is of the worksheets and how to create them in a way that's sustainable for sharing over time and then the Starter Kit for program managers is just that times two where all of a sudden I'm editing this book with all these co-authors and coordinating the assignments of chapters to peer reviewers I put together the I taught myself adobe illustrator so I could make the book cover and did a lot of CSS in the back end of the press book to make sure that the colors lined up across all the different exports but in the end it's a really exciting sort of through line to see what it takes to go from being someone who's just casually interested in doing OER work and what you can get out of it through the Starter Kit to partnering with more people and leveraging really the open movement and open call for peer reviewers and call for copy editors you can do something much bigger and more impactful by asking for help who knew so that's really what the takeaway for me has been well if anyone has other questions for Abby for us for any of the case to the authors or others as they're planning to maybe use this book in in different ways feel free to unmute ask away or post your question in the chat yes I highly recommend asking other people questions I feel like I've gotten too much attention today so far are there any chapters sections or advice on preparing an OER program to sustain after a program manager leaves and I might pass that over to Stephanie to give us some initial thoughts well that's an excellent question and I think a lot of that has to do with planning about where we are or where you are in the process how your program is funded whether it's something that's really depending on one person or whether there's an institutional support for it so we didn't really discuss that specifically I don't think in the in the text but we did talk about sustaining a program and we talk about how you can make sure that your program keeps going so I would say you probably want to think about finding somebody to manage your program even if they're once somebody else leaves just because it's an it's not something that's just going to happen by itself it needs somebody to just need some TLC it needs somebody to to monitor and take care of it but I'm open to other suggestions from other folks who've been in that situation I might also suggest looking at the sections of the book that talk about building the program and specifically Abby's chapter on building your team because I think that can then signal to again the many hands involved in sustaining this work rather than it just being an initiative that runs on the expertise and sweat and all the rest of just one person making sure that this is a sustainable program can also mean again ensuring that there are multiple people involved so one person leaving doesn't cause the whole machine to stop and I've also put in a link to a conversation focused more on what happens when your author leaves what happens when your subject matter expert faculty or instructor who's authored a book leaves the institution so the open education network and DRIPP's community will be exploring that conversation a bit more on Thursday so if you're thinking about well maybe I can solve this problem at the smaller scale of a single project and then work backwards to see how some of those strategies and suggestions could be applied program-wide please jump in Paul it looks like you have a comment or a question hi thank you very much I told my friend to work with me for the comments that your book was one of the greatest things I've seen for the year so I'm looking forward to to using it I welcome the idea of a volume two where you rear their contributions from outside North America and I'm hoping that by that time I'll be able to write about the Caribbean story because we're in the area where OER is still either relatively new or relatively unknown and their pockets everywhere I'm hoping to bring that all together to create a kind of an OER Caribbean movement so I do hope that by the time they get around to or maybe anyone some feedback on your toolkit that I can share our story with you and hopefully that will help to inspire other areas other pockets where OER is new or not as as as popular so I thank you for your effort I think it's a really wonderful work I haven't looked at a lot of it but just looking at the contents of it I am I am thrilled I'm very pleased I commend you all for your work and like I said I hope to provide you some positive feedback on how we applied it in in our area thanks again and thank you for inviting us to participate in your launch today thank you that was wonderful Paul and we look forward to seeing whatever you do next wherever it comes out and if we do decide to put together a call for other people I think if I were involved in something like that I would stay at the editor level and not write anything because I do want to make sure that I'm not the only voice doing a lot of this especially if it's focused on elsewhere but it's an exciting possibility oh boy you guys get me excited about projects I could do when I just finished this one but uh any other very glad to hear that yeah no it sounds wonderful is there any other questions about things whether they're in the book if you're not sure things that you read in the book that you have questions about more general questions Carrie's wondering if there are tips for advocating for full-time or dedicated positions either in or outside of libraries and they know it can vary by institution but it's an important piece of sustainability and it sounds like one of the wonderful amandas in the OER world has a collection of job descriptions going already that has been extremely helpful but is there more in the book that could help Carrie sadly I did not get a chance to build this out too much uh Amanda Larson shout out to you feel free to post your google drive in the chat if you want to that's all the job descriptions you've saved over the years uh but we're covered we covered a little bit in the case studies specifically Cheryl's and Regina's when it comes to what it's like being an OER librarian and OER lead how that can be structured in different institutions and then when talking about building your team we talk a little bit about the different structures that can be built around that whether you're a full-time or part-time person and what that looks like I will uh say the OER of Skalcom which is a Skalcom book coming out soonish we'll find out that's for people learning more about scholarly communication topics in libraries published by ACRL I believe will have a section on OER librarianship and the practice related to that again I think that is there are different sections done by Regina me and Amanda Larson so we're all the same people writing about it again but specifically that you have part-time full-time is not dressed I think in the starter kit itself all right so we've only got a few minutes left oh boy as I say that Leo has something to share if you'd like to look in the chat but there's specifically a survey out about institutional policies supporting open education so if you'd like to help Leo with his research please feel free to fill that out for him so the final thing here is how can you get involved moving forward with the book first is by looking at our page in the rebus community following the book talking the discussion boards there's space for you to sort of meet up with other people who are working off of this and thinking about what's missing and what questions they have and talking with other people in the community you can share your thoughts with us using the feedback form and the book's back matter which will send me an email as soon as someone fills something out so if you see a typo if you see a section that's missing a very key component do let me know and we can get those fixed up and spread the word about the book using hashtag OER starter kit PM if you are still on Twitter since we've planned this book launch things have gotten weird over there but still some of you are still on there I know yeah and you'll see on the book home page that we have an active call there to join what we're calling this community of practice different people are going to be using the book or learning from the book or perhaps have ideas to expand and adapt and remix the book in a number of ways that's all part of practicing the ideas of implementing the suggestions that are in the book so we'd love to hear from you we'd love you to be able to connect with one another as well so you can follow along on that project page or use the discussion board and the threads there in whatever ways you think will serve you best so feel free to whether it's share links to studies that you have ongoing or ask questions to help address challenges that you're facing or to just share milestones of accomplishments that you've been proud of as you've been establishing yourself as a program manager and setting up your initiative all right well we've got five minutes left any closing thoughts from any of the authors case study authors or audience members here today I just wanted to say how much I appreciate working with abby and the team on this book abby did a lot of work to keep us going and it's been a really interesting experience and I encourage everybody to consider contributing to our volume two if we have one or volume three whatever that happens to be because the more the merrier and everybody's got their perspective and and your your experience is important to share because we can all learn from it so I'm hoping that everybody will will participate yeah here here thank you to abby for spearheading this particular project on my end special thanks to Elaine Thornton for recommending me to step in as an author and also the fellow copy editors folks who are involved in this book think abby tried to articulate in the first slide there so thank you and I hope that this is useful in some ways and that you reuse and you let us know how you end up implementing and using either sections of of this resource or info all right well thank you everyone for coming today it's been great to sort of talk with you all about our book and where it's going from here potentially a lot of discussions about the future which is great but we appreciate all of your support and potential adoptions in the future for seeing where this book goes next thanks everybody for being here and thanks a lot thanks so much abby for coordinating all of this


Hobby every EFL teacher needs to try when teaching English abroad, learn about local music. When living abroad in a new culture, it's a great idea to see what local instruments are popular in your new home. Every region of the world has its own unique music and musical instruments that many outsiders don't know about. For example if you find yourself in Africa, you should have a go at playing the kalimba, or when in Japan, you can easily pick up biwa, a pear-shaped lute. Thanks so much for watching. We are ITTT, the leading provider for TEFL and TESOL training courses. If you like this video, please subscribe by clicking that button down here, and click on any of the videos here on the left for more interesting teaching tips for getting certified to teach English abroad and online.


Okay, welcome, welcome amigos to DrupalCon, of course. And we're day two, so I hope everyone's having fun. We've been having fun, so. We're here to talk about migration into Drupal8. Some people say that there's no migration path in Drupal, but that's not true, so we're going to talk about how you can actually get stuff into Drupal8 today, and we will talk about what's coming in the future. So, my name is Ryan Wheel. I work based out of Montreal in Canada, and this is my colleague, Novella. Maybe do you want to say hello on a Spaniard? Hello, my name is Novella, and this presentation, of course, will be about migration. As Ryan said, we work in Montreal, and we are two thirds of the cafe team. We do a lot of migration, and we are very interested in migrations, especially for Drupal8, mostly because it's a lot of fun. Okay, so what is migration? How many people have used migrate in Drupal7? Is this familiar to people? Okay, roughly half, probably, okay. How many people are missing some chunks of hair from this migration experience? And how many people have upgraded Drupal sites in the past, using the upgrade.php page? So, a little bit more, but about half as well. Okay, so migration and upgrade are different things when we're talking about this stuff. Migration is a set of templates that you can use to port your data, and it ports your data by connecting to your old data source. And in this case, we're going to be talking about Drupal6, because that is what is currently in Drupal8 core. There is a plan to get Drupal7 to migrate as well, in addition to other things, so let's talk a bit more about that. In Drupal7, there was a package called migrate Drupal2Drupal, and this was a set of templates for bringing data from Drupal5, Drupal6, and Drupal7 into Drupal7. It was originally done as a proof of concept for maybe doing a new migration path, and it's now been declared the new standard, so that old upgrade.php page is gone, and that one, it used to work that you would take your Drupal6 site, and you would just drop your D7 site on top of it and run upgrade.php. So it's a little bit different now that we're actually connecting to an old site and not changing it at all, but just changing our new site and using that. So a little bit more about the Drupal2Drupal templates is that if you were using them in Drupal7, they are object-oriented, which is great news for many people. Obviously, the Drupal8 system is more object-oriented and they continue to be so in Drupal8. So it's also worth noting this happened later in the development process in Drupal8. It was actually after feature freeze, I believe, that it was decided to put migrate into core, so as a result, some things are still in progress. Now, you may have noticed, I talked about Drupal6 as opposed to Drupal7 as the initial path, we're now able to skip over versions. So this is really great when you're looking at older sites that are now nearing end of life. As many of you know, when Drupal8 gets released, in theory, Drupal6 will be no longer supported for security updates, so there's an urgent need to move Drupal6 sites to something else, and rather than drag people through two versions, which can be very difficult to upgrade, we can skip right over that and just say, okay, we can connect to D6, pull all of the data out, and make a wonderful new Drupal8 site. So there is still a plan to kind of replicate that old upgrade.php page with all of this working magically under the hood, and that is currently flagged for not 8.0.0, but the 8.1.x release. So it may or may not be there in 8.0.0, but before you go and say there's no migrate in core, there is actually two migrate modules in core. The migrate module that runs the migration is there, it's working, it can be used today, and then the migrate underscore Drupal module, which is the equivalent to migrate D2D in the old version, and what that one does is that has all of the mappings in D6 to say a D6UID is going to become a D8UID, and it has mappings for each of the fields so that you don't have to do that. So here's what we're looking at for version support. Currently D6 to D8 is in core right now, and it has been for months. D7 to D8 is in the process of development, and that's happening in a sandbox off of the main migrate path, so what's going to happen there is people are going to build the templates to a point where the quality is really good, and then those will get brought into the migrate underscore Drupal module in D8 core. The templates between D6 and D7 are not very different, so it's probably going to start moving very fast in the near future. If you're interested in helping with that process, we'll give you some information at the end of this presentation on how you can connect to people that will allow you to get in there into the sandbox and work with that. And lastly, D8 to D8, because sometimes you need to rescue projects, and in D7 this became a really popular option when you take on a rescue project and you go, okay, well the data's in that D7 site, but the code in that site may not be what we want to use. So for people that were doing rescue projects, having a path within the same version is very important, and there is also talk about using migrate to do migrations between the different beta versions of D8. I still haven't seen any templates for that yet, but this little rumor has been around, so it's something that's out there. And then lastly, I put an asterisk here that of course D6 support should in theory stop when D8 is released, but there's also been some discussion about extending that temporarily for a period to allow people to do that transition, but there's really an imminent need to move away from D6, because as security updates get applied, there's not as much testing framework in D6 to make sure that that's all stable, so there's always a risk every time we make a change. So in the long term, we would like to see D6 kind of move on. Here's the exciting stuff. Do you want to talk a little bit about this? Yeah, I can talk. As it says, everything that's in D8 core now will be pulled in from D6, even if it was in contrib for D6, but it's in core now, but I don't know, definitely. Configurations is a very important part at least for site builders. One thing that has been very troublesome for D7 was to have to replicate every click manually. For D8, that's not something that you really have to worry about, and that comes over with all of the data that's been put when you migrate. Multilingual is a big aspect of this, as many of you have probably heard today. The new multilingual system in Drupal 8 is, as Gabor describes it, a wonderland. It's so much easier to use than other systems. D7 was well-supporting for multilingual as compared to other content management solutions. D8 goes way further with this, extends it throughout the system, so all aspects of the system can be translated, but in the old system, you needed like 10 modules, 12 modules, 15 modules to make everything translatable. Almost everything's translatable by default now. I can't think of a single thing that isn't. So that stuff was contrib, but because it's now in core, we're actually reaching back into the old system and we're grabbing that contrib data and pulling it in. So. So, pro tip, if you had a contrib module in D6 that is now in core, even if you disabled it and uninstalled it, you think that it went by-by you might not have completely done so. So, for instance, one really big thing that people have run into is the book module.  Now it's in core, so remember to enable it when you go into D8 when you're doing your migrations.  So this is kind of an open bug because what happens here is that in past versions, we always supported moving the data forward. So if you enable the module that's in core now at some point and you have data there, we want to bring it across, but it needs somewhere to go. So if you don't have the target module enabled, you're going to need to enable that. There will be better support for catching those errors in the future, but something to watch out for. A couple other points on this note. Views were initially talked about as being maybe an exception to this, but currently they're not in core as being supported for the migration, but there is work being done on making a migration for views. I guess it's also worth noting that your content types get set up. If you were looking at your D7 migrations and thinking I have to set up all these content types, you don't even need to do that because the idea is that when we do have that replacement for upgrade.php, which we'll talk about in a minute, the idea is that we have the same process. So you should be able to go to a page and click upgrade and bam, everything's there. So this stuff should come through. Another example of areas that are kind of tepid support is migrating your blocks, blocks come across, but if you're not using one of the default themes, we don't really know where to put things.  So something to watch out for as well. There's even more wonderful stuff in Migrate that handles the multilingual stuff because multilingual structures have changed. And the biggest one of these is that in the past, if you had translations, you would have one node for English and one node for Spanish and they would have to know about each other. And sometimes you had to do the node in English before Spanish or in Spanish before English and it always had to be the same process. All of that is gone. It's now one node. So if you have a car in English and an automobile in French, you know that it's one object. So now in Drupalate, they are one object. So during the migration, all of these pieces get merged into one object. So one thing to watch out for them is when you're bringing things over, say you had however many nodes because you had X number of languages, now they will all be one node. So if you don't see them, don't worry. Yeah, you'll see them in the interface and we'll show you an example of that in a minute. Configuration of translations should come through as well. There's more details of that in the config management side of things. So just kind of be aware that that's out there but most importantly, test these things a lot because not everyone has multi-lingual sites. I suspect many people in this room do. So you will want to run some tests on these things while we have the chance now, maybe at the sprint tomorrow, you can come and try running some stuff, try it in your own time, try it on your agency sites and report issues if you find issues with particularly multi-lingual migrations because sometimes these cases don't get covered as I'm sure we all know if we work on multi-lingual sites. So now let's talk a little bit about how this is envisioned to work in the user interface. So first we need to know that we need to enable the migrate and migrate Drupal modules and we mentioned just a second ago that you do need to have all of your target modules enabled so if you were using aggregator, make sure that's enabled. If you're using book, make sure it's enabled. Translation support, make sure it's enabled. Then you're ready to go. One thing that's definitely tripped people up while they're getting things set up was just the PHP and Dresch versions. And I know people are always harping on this and I'll do it again. Make sure that your PHP and Dresch versions are proper for Drupal 8 because they are a bit different from Drupal 7. So yeah, first step, install Drupal 8. Second step, enable all the modules. And then third step is make sure you've enabled migrate and migrate Drupal. And now you're kind of ready to do the basics. We're gonna go one step further though because in this initial part of our presentation we wanna talk about the migrate upgrade module which is the replacement for the upgrade.php page. So migrate upgrade is contrib at the moment. This is the one that will be merged into probably 8.1.x and it replaces upgrade.php with just slash upgrade. Now, we couldn't put .php because then we would have to put a file there. And right now this is just a config page in Drupal so it's great, we can just use this. It's gonna ask us to input our credentials for the D6 site. So it's important that these live on the same host because that way it can run really fast and we don't have to worry about firewalls. You don't have to worry about the wifi stopping. We don't have to worry about any of that stuff. We do need to put in an address where we can access the files. And I believe right now at the moment this interface also uses this to do some text handling. So it may look for this address pattern in your body text and other things like that. But in any case, you do need to have your files somewhere and you can put in a path as well for your private files. So of course in Drupal 6, I think you had the option of public or private and then there was some hacks you could do to do both but they were kind of weird. But it's in core and it has been since D7 so private files can be put into this interface. It's the public files, if it throws an error with the public files address that you stick in there through the interface, you may need to put a snippet of code which you can copy and paste for me in your manifest file which we'll talk about in just a bit. So yeah, so right now we're looking at the UI and it is the most buggy part of the system. So let's just, let's get through the UI and then let's get to the good stuff. So this is what the migrate upgrade page looks like. We put in some database credentials and an address and then we go, we scroll down if you can imagine, we're not doing a live demo here. There's your public files directory and then it just says perform upgrade and then things are gonna run. The configuration is going to import first because we need our node types to be there so that we can put stuff into them. We get the site name, we get like all of those types of settings, we get your like whatever preferences you configured when you first installed Drupal are all gonna come through and be like what you set them to and then there's a hook that runs that you can take advantage of which we'll get into more later and you can use the hook to override what's being done in this if you don't want to, if you want to minimize the amount of code you want to do if ideally you don't have to do any if you're running it this way. And then boom, it's just gonna do a status bar and it's gonna run. In D7, it was discouraged to run stuff in the user interface due to a bug in batch APR that would time out on you and die. It doesn't do that anymore. So because this is what we've always done in Drupal as we've gone to the upgrade PHP page the intention is it will work in this way. So we are working out all the bugs and that is hopefully going to work perfectly. This is a snapshot of kind of an older version of the upgrade process but it's pretty much the same. It's gonna say yay everything worked. It might tell you if something failed here it might say like a couple things failed. Things go into the watchdog now. So if you're like okay where do I find out what happened? You can just go to the watchdog like everything else and that's on the reports page as we all know. So and then I put in this special slide because of what we said earlier I wanna point out we've got three nodes here but as you can see we've got five entries and what this was in the old site this first one was language neutral so that appeared on all languages. So that's node one. The second node had a translation so node two and three on the old site was like a French version and the English version. So we've got links to each of those but they're actually one node under the hood and then we've got a third node that was also translated and again that's showing as two entries in the interface but in reality it's actually one node. So if you hover over those edit links you're gonna see that the node IDs there's actually only three of them there but that's what you want and in D7 this was called entity translation. So if you've used entity translation you're probably gonna be very excited about this. Okay, do you wanna talk a little bit about Drush? Yeah, so maybe you can tell most of my comments are geared toward site builders and this is actually something that I've tried to convince other site builders of but do Drush use it and use it wisely of course but this is one place where you really do want to use it. As you saw in the UI it was very simple you put in your database credentials and you hit go and you just cross your fingers and I've done a lot of test migrations on the Drupal 8 path and I've done it both in the UI and with Drush and one thing I found was that when I did it in the UI if something screwed up everything would stop. With Drush, luckily I can run it but I can make sure that I'm only running one piece at a time and that's really nice and of course that is Drush for the combination of the manifest file which we'll get to in a second. You can do both Drush and the user interface just to see what's really going on behind the scenes but this is basically just a plug for using Drush as site builders. So this is what is if you want to just use Core and not use that contrib module this is the way that people are usually building the migrations and testing them in real life. This is what the developers are using. So as developers this is the most accessible thing to most people. Now there's a few components of what's happening in the background. The first thing is that in order to do this in Drush you're going to need a manifest file and that's just a YAML file, it's just a text file that lists out the names of migrations. There's a bit more detail of that but think of it just as a list of migrations you want to run. There's a hook which we mentioned earlier and you can use that hook to look at each item that you're pulling through as it comes in and if you don't want it you can say bye bye. I don't want this one. I don't want this node type. I don't want this particular node. I don't want this setting to come through because I'm gonna do that myself. This is the type of stuff that's very useful when you're building a site because maybe you want an entirely new site and you just want the blog posts. That's important so you could use the manifest file to specify what migrations to run and then you can do a bit of processing just using a hook. By doing that you can just put things into a .module file and just implement a hook which is something that's very familiar if you're using Drupal 6 or Drupal 7. So that's like the easy way to get into this without having to learn a whole bunch of crazy new things. The thing about the hook is that even if you are using Drush and a manifest file all your fields, for instance, may try to run at the same time. And I know recently I've had a problem with running the image field as opposed to text fields and integer fields and things like that. So I just used a hook to print everything out so I could really narrow it down and see what I needed to exclude in order to make the other fields come through. And that's a really great process for debugging which is certainly necessary now and will probably be necessary even when things are a lot more stable. Now the last thing which is really where Migrate gets really awesome compared to the old version is the plugins. And if you haven't used plugins you should use them because they are awesome. Plugins in Drupal 8 are just files that live in a special directory where they're known to be. So in this case they could go into your custom module under the source folder, under plugin, under Migrate and then further into one of three different folders depending on what type of plugin you're using. And you can go into the Migrate or you could go into the core modules Migrate folder or the Migrate underscore Drupal folder and find examples of these and just copy them into your own module if they don't do what you want. And you can make them do whatever you want. All you need to do is make sure you update the name which appears in the comment and install your module and then you have a new plugin. Plugins can then be referenced in your manifest file as an override. So there's lots of opportunity here to just take something that's close to what you want and either modify it with a hook or just go and create your own implementation. I know with Drupal 7 we had people write migrations for WordPress, for Joomla, for Microsoft SQL Server things, for XML, all sorts of different handlers. So you can go into your Migrate underscore Drupal folder, look at all those implementations and go, hmm, I bet I could write one for some other legacy platform and you can make a module for that just by copying those files, renaming them, changing exactly what the schema of the database needs to be to make it work and registering your own migrations that way. There's also things called process plugins and these are things that you can use to modify things as they go in so you can do things like change all the titles to lowercase and again you can just reference that in the manifest file. So there's lots of cool things that you can do with that. Basically it's all plugin based so you can just remix these things, you can chain them, you can say change all the titles to lowercase and then add three numbers to the end of it and remove all the spaces and you could just chain all these plugins together. So it's very extensible in that way. A manifest file looks like this, kind of ignore the bullet points along the side if you will, but so we put it in the root but it could go anywhere as long as you reference it when you run the drush command and in this case we've just provided a short example but D6 user role, D6 user, D6 filter format, these can go in any order so you don't need to worry about what order they're in, you just put them there, these are the names of the migrations. If you wanted to change the process plugin that was used you could indent underneath one of those and change that by just saying what the process plugin you want to run will be. You could also change the source or the destination if maybe you wanted to turn users into nodes, you could do that but that would be really weird but you could do that. Another good thing about doing it with drush and using a manifest file to declare all these things is that when you run it in drush if you're missing anything in your manifest file it'll just tell you right there and then you just go put it in. Yeah, so it's gonna calculate the dependencies and it's gonna say I can't run nodes until I have users because there's a user field on nodes so I need a user to be there so it's gonna tell you you must run d6 user so this is very helpful. As well you can find out about all of the migrations, I've got a command listed here. If you're using the most recent drush of course it's very important to note actually we didn't have a slide about this. You need to have the latest drush, it needs to be drush seven and you install that with composer so you also need to get composer. And you get that from getcomposer.org I believe. Anyway. It's also the option of using the dripple.org slash tool. I think that is the correct URL. Yeah and Acquia Dev Desktop does have this installed as well and so you could use Acquia Dev Desktop to do your migrations in this way but you will need a bit of customization around the database connect string so we don't have that in the slide but it's instead of local host it would be, we're dumping a head here, it would be 127.0.0 colon 33, it's not 3306, 3307. I have this in a blog post if people need it they can feel free to contact me but in any case you can run drush config dash list and then do grep to narrow it down to only migrate items and this will list out all of the migrations that the system knows about and these are all things that can be put directly into your manifest file and then you can run the command drush migrate dash manifest provide it a database connection string. This should be familiar if you've used other things on the command line that connect to databases. It's a, so I put here d6 user colon d6 password at local host slash database name which in this case is d6 and then the path to the manifest YAML file. That should be enough to get you there. One thing to note is that on the slide although it's two lines, it should be one long line when you do it. Yeah, so that drush manifest, it's legacy dash db dash url all as one so just be mindful that the slides couldn't quite fit that long string in there. So now sometimes you'll need to customize stuff especially if you have a custom module that you yourself have written perhaps you have a custom field type. A good example of something like this that took a while to get support in d7 was the address field. So maybe you're moving address field into something else or maybe you're the author of that module and you want to make a migration path for your users. You can put your plugins into your custom module and then you will need to deal with the fact that this is a custom entity type. So like nodes, those are in every site, those are in core, we're gonna deal with those but if core doesn't know about it then we need to deal with it. Cleanup tasks like Novello was suggesting with like maybe you don't want your image fields to come through or maybe they're broken and you don't care. Cleanup tasks could be done with some customization as well. And then you could actually go as far as making some of your theme, like moving your blocks into the locations in your new theme. You could do some customization for that as well. So these are just some examples of things you may wish to customize. This is just a really rough look at what the hook looks like. So we were just running this before the presentation. It's really awesome if you just want to cycle through those elements and say, if the field name is this, false. We don't want it, we don't want it go away. It's like, we don't need this in the new site. So another thing that's kind of important if you're new to programming in Drupal 8 is that you'll see that instead of, like we have the row variable here and it's prefixed with the row type. Row is a type of object. So it's not an array like it was in D7. You'll have to look at the row method to see what the commands are to dump out all of the data if you are new to working with object oriented stuff. It's a fairly simple thing to do, but just like a fair warning that this is no longer just strictly an array as with many things in the new system. And just another tip, whether you're new or not, that you can run a drush print r with the hooks and that's what really helped us out when we're doing it all afternoon. We're just looking at things as they were coming through. Yeah, drush print r, drush underscore print underscore r and then you put in your variable there will give you stuff dumped out on the command line. It's a tip that works in Drupal 7 as well. So it's worth looking at if you are like, why isn't this working? And then you're like, oh, okay, those three ran and then suddenly that's where it went kaboom. Okay, and then you realize that maybe you have some corrupted data in your old system that maybe you wanna fix. We talked a little bit about plugins already, so sorry for jumping ahead there. One important point with when you do make plugins, you don't need to register them anywhere. You don't need to put them into your info file, nothing. You just need to put it in the folder where it wants to go. So if you went into core modules, migrate underscore Drupal, source plugin, D6, source, no, sorry, almost there. Anyway, you're in the plugin, you're in migrate, you're in source and then you're in D6. For example, you would put it in a like place. You'd put it in the same naming convention in the same folder in your own module. So really the only place then that you'll need to declare the plugin is on a post-it note on your wall so you can actually list those folders out. And if you've never used plugins, there's a really awesome way you can try and that is to make a custom block. Blocks are plugins in D8, so under your source folder, under your plugin folder, you can have a block folder. Go copy an existing block from somewhere you know that's easy to use and you can just put it there and change the name in the comments because comments are now code, weird. So some things that need polish. D6 migrations do have small bugs and that's what trips up the user interface. That's what trips up the migrate underscore upgrade module. So if you're able to go in there and do lots of testing when you're doing migrations for D6, please submit your patches to the core issue queue. If you have to jump over stuff, we've given you some tips on how you may be able to override that or just skip those things if they're not necessary for you. Template development is needed for Drupal 7 to Drupal 8 as well as Drupal 8 to Drupal 8 because that will be a thing at some point whether it's during beta or whether it's post-beta. There will be rescue projects. I'm looking at some smiles in the audience and it's like yeah, there will be, I know there's live Drupal 8 sites right now and those are obviously not on the stable version because there is no stable version. So at some point there will need to be D8 to D8 migrations. A major feature that existed in Drupal 7, well major features I guess I should say, there were things like rollbacks. You can't rollback right now. You just reinstall and start over. So build things in modules that create your site at this point in time and that way you can kind of keep moving with things, build and destroy, build and destroy, use continuous integration. If we're gonna go buzz-worthy, buzz words here. Continuous integration is wonderful for this because it already embraces that build and destroy methodology. There were things called incremental migrations. So you can rerun the migration twice, three times, four times, 400 times, that's fine. It's going to be additive. So if you've added new nodes, more new nodes will come through. But you can't do things yet, limit how many things you wanna import. So in D7, you could say limit 10 and you'd only get 10 nodes. You can't do that yet, but it was put on the roadmap at the end of January, so it's going to be coming very soon. All right, and as a silver lining to the no rollbacks thing yet, you have DrushSI where you can really just site and install one more time and that'll drop your database and do everything for you. And you also have DrushCEX, which is config export. Yeah, config export will let you see all the details. So if you're like, what's happening in D6 user? How did they set that up? How was it configured? You can either go into the module that created it, so migrate Drupal, and under config install that will be there. But if something has changed in the system, maybe you overrided something or maybe you want to override something, you can use config management to dump the config, see what's happening there, and then make some plans to change it. Not an expert in config management. I know there are people in the room who are. So I defer to them for more details on that, but rest assured that you can look at the YAML files that are provided by the system that provide the default implementations of each of these migrations. You can see the details of like this D6UID equals D8UID, D6, whatever the field name was gets changed into this new field name. Those things are all available to you. And of course, we've just said this many times, but it's worth repeating. Expect to re-migrate, expect to reinstall because it's not final yet.  Okay, so how you can get involved? This is kind of important because if you run into trouble, maybe you'll like wanna tap into the community who can give you answers really quick because they're like, oh yeah, we know about that or oh, we should deal with that and other things. And this is how you would also get involved in developing the D7 templates or if you wanted to build templates for other programs, other platforms to bring them into Drupal. So there's this Drupal groups page, imp, so it's short for import. I think it was an acronym at some point, but I don't know what it is. There's an IRC group. There's almost always somebody in this IRC group. It's pound Drupal dash migrate and it's on free node like every other Drupal chat that's in IRC. I believe if you've never used IRC, there's a page on Drupal.org slash IRC. That will give you details on how to do that. And recently we've changed the time of this, but there is a weekly call that you can do on Google Hangouts. It's important to join the IRC group before this call happens because that's how you get the URL. So that happens at 9 p.m. Eastern Standard Time, which I believe is where we are right now, at 9 p.m. So it's difficult to coordinate times. We're dealing with people in every time zone almost. It's just people are scattered throughout the globe and we've got people from Europe to Australia and everywhere in between and other places far flung all over the globe. So 9 p.m. Hope you can make it. It's a great place to get support for creating your own custom plugins and it's a good place to report problems in tests that you've run. If you're running a migration on multilingual data and you run into something that you think is unexpected, it can be good to check in in this group. So report problems, please. If you report the problems, that means it's gonna be automatically resolved for the next person if we're able to put some code in there to fix that. And one really important way that you can get involved come to the sprint tomorrow. Yes.  I can't get it installed. We actually built some virtual machines that we can spin up for you if you're absolutely desperate. I hope not to do a ton of these things, but if you're absolutely, absolutely stuck and you can't get it installed, do come talk to us because we would rather, people are able to get in there and do some work. So we will try to help you out with that. If your machine blows up and you need to use a tablet, we could actually support that, which is sort of ridiculous, but kind of awesome. Okay, so I mentioned this earlier, but drupal.org slash project slash drupal, I was getting mixed up with these issue URLs. Anyway, the core issue queue is where you put your stuff for the D6 migrations. For D7 stuff, if you're interested in that, we're gonna connect you with the sandbox and the stuff lives there for now. I tend to stay away from the sandbox myself because I like to just work with core. So again, just come to the IRC group, say hello, ask people how to connect if you're very interested in D7. And again, test, test, test, you're about to think you will stuff. Okay, we've mentioned this, yes. Very important point. Do you want to mention this last one? No, okay. It's a really big cantaloupe. I've been through the upgrade process many times and for my own blog it was on D5 and I moved it to D7 and I sat down at a cafe where I could make my angry face and someone would bring me coffee. And it took me like about six hours of like, okay, I went from D5 to D6 and there's bugs in the upgrade process and then I resolved the bugs and then I spent an hour looking for the image fields and then I was like, I guess I'll redo it. So I redid it. Where are the image fields? Then I realized there was only five images on the site. So then I upgraded to D7. All of these things sort of introduce like problems because in D5 the way that we error checked and validated things may be different than D6. So sites that have moved between different versions over and over and over, those sites are the riskiest ones to migrate and those are the ones that we need to test the most because we may not know that sometimes user names could be formatted this weird way that we don't allow in D6. But they maybe got through the upgrade process. It would be weird, but it is possible. So if you're planning on some site that was perhaps in Drupal 4.7 and then got upgraded to D5 and then got upgraded to D6 and now you're like, okay, let's skip D7. That's a great opportunity to test that site and contribute feedback because that's the type of site that's gonna have the most unusual data in it. And then of course, when I mentioned those five images, this is another good point. Novella recently did a brochure site for her mom. And it was like new content. There was really nothing to migrate. Copy and paste would work if you're doing a five page site. So it's worth noting, don't kill yourself on doing all this stuff unless you really wanna learn. And if it's a really small site, like there's always these other options, but they're not the most ideal. And if you do wanna learn this stuff for your bigger projects, then investing that time can be very valuable. Well, and just to put a plug in there for copy and paste, it's a really great way to learn the interface for D8. And the interface for D8 is excellent and I was able to actually teach it to my mom in one evening. So let me just say, it's for individuals, it's for businesses, for everybody. And that is a completely legit way to migrate your stuff. Yeah, so if it's a very small site, you may just wanna do this for research purposes.  As Larry mentioned earlier this morning, it's like you can do big or small and all sorts of different types of sites. I mentioned doing continuous integration and we've kind of been working with this on a new site that we're kind of doing a mixed thing. So we're working on our own agency site. We have new content for most of the front end stuff. So we're actually using a module that we built that like sets most of our new settings and creates some of our new content and then we're using a migration for the rest. So these mixed mode kind of things will work with your continuous integration practices. So that's another thing to be mindful of and again, another reason to use Drush if you don't just want to like, boom, like import everything because nobody likes to like migrate and then have to do a whole bunch of little tasks afterward because then you have to remember all those tasks. And then if the project gets put on hold, you have to remember all those tasks and you can't sleep at night because you're remembering all these tasks. So okay, we're like at the end. I've got four links that I've been plugging since I was at Bad Camp and these things are things that you can use to teach yourself Drupal 8. And by teaching yourself Drupal 8, all of the stuff that we covered today will be really, really easy. The first is the developer guide that's on www.drupal.org. That one is edited frequently by people and if it goes out of date, please click edit and update it. But you can, if you're logged into Drupal.org, go to this page, scroll to the bottom, click the printer friendly link because it will render all the sub pages in one long HTML file and then you can just read it like a book and it's fabulous doing that. That will get you through most of the API changes that you need to know about as a developer and that will get you a background on configuration management, which is how all of this stuff, like the manifest files, how those are constructed, all of that stuff is configuration management. So if you read the developer guide, even the first couple chapters, you're gonna have a really good understanding of how you can override all of this stuff really easily. Examples module has been used for years. It's up to date as well. So if you're looking for like, how do I make a block in code? How do I do stuff like that? Go into that module if you're curious about how to do an implementation of something because there is up to date stuff in there and I actually went into the examples module and used those to upgrade the developer guide. Examples module is very up to date so that's very useful. The API docs on api.drupal.org are also up to date but this is the documentation that's generated from the comments in code. So it's useful but that needs to go through code review before it gets in.  Like it's harder to change that stuff because it's not just something you can click edit. And lastly, the most important awesome one on this list, change records. If you're going in and starting to code something for your site if you're doing a continuous integration module or just like, where did this go? I know one time I was trying to use the watchdog command and I was like, watchdog does not exist. Okay, what do I do? What do I do? There's no watchdog. I could know I shouldn't do any crazy things. I should go to the change records page and I just put in the word watchdog or whatever the command I'm trying to run that no longer exists, paste it into the search form and it's gonna give you a change record that says watchdog became this and here's how you use it, the old way and the new way and you can copy and paste that into your code and go home. That's also just a good general resource when you have errors. Sometimes they are just because something may have changed. So list changes, you can't find any issue queue or to search both. List changes is definitely a really great phrase to that. This can also be very useful if you started working on a droop late site and then you got distracted for two weeks and then it's broken for some reason when you updated and you're like, what changed? That's what changed. There will be entries in there that will say, these three things changed since you were here two weeks ago and you can just look at them and go, it's probably that because I'm using that function. Okay, cool. So change records, wonderful. Thanks change record team. And we've got a few minutes for questions. I guess five minutes for four minutes for questions. So Jess, microphone. So I have a correction slash clarification, a recommendation and then an actual question. The clarification, I just wanted to say regarding Drupal 8 to Drupal 8 updates and migrations. We didn't kill update.php, update.php is still in core. What we did kill is that you can't ever, ever, ever, ever use it for upgrading from one version of Drupal, like a major version like Drupal 7 to Drupal 8. So by default, when Drupal 8 ships, you will still be using update.php to upgrade from 8.0.0 to 8.0.1, for example. And also between betas, you'll also be using update.php. The same old, if you're a developer, you've written the module, you'll be writing the same old hook update and for that. But eventually you'd also like to include Drupal 8 source plugins so that you can do those Drupal 8 to Drupal 8 migrations as well. The idea being that when you're running a minor update, you don't necessarily want to create and build out a second site for that. Sometimes you just need to fix one little thing and so an update hook is all you need. So that's just a minor clarification there. So but in soon, update.php is still there, you just can't use it to migrate anymore. Then the recommendation is regarding views migrations. I worked in the views and core team on my Max Jam and I would strongly recommend that you consider just rebuilding your views in the UI after you've migrated the rest of your data. It's great that someone's trying to build a plugin for that but the views API is so complex, the data model is so full of things and not only have we, it's very different under the hood than it was in Drupal 7 but also that last link on Ryan's last slide about change records, we kind of sort of don't really have them. There's like two of them about minor things maybe and but like the major ones that tell you the important things that change aren't there so it's gonna be difficult to write accurate migrations for views for that reason. So you might wanna consider do everything else and then just rebuild the view because honestly it's probably gonna be faster than trying to fix all the bugs with it. And then my question, I don't wanna take up too much time but my question was about the manifest files. So you said that first of all they're not required, right? It's just an optional thing that you can add on, right? They are required if you're running them in Drush. It's the only way, yeah. And then the second thing was you said that it would give you an error message if you for example tried to put a line for importing nodes before users. Not the order but just if you omitted something. Or if you omitted, okay, yeah. So it will actually order them for you if you're not. Yeah, it will. There was a bug during bad camp where one of them was out of line and it was fixed. So I believe it was fixed at least. So it will automatically resolve all the dependencies and order them correctly but if you forgot one it will be like, oh I do need that, please add that. So thanks for those tips, that's wonderful. I'm actually one quick question back to you. Did upgrade PHP get removed and brought back in? No, it didn't, okay, interesting. That's okay. Cool, and yeah, rebuilding views has been something that yeah, we've often redone between versions so that is really important to know. So thank you again for those tips. It's funny. Okay, we'll direct to Novella. Una pregunta en Trupal 6, los pagos se guardaban en M5. Al pasar a Trupal 7 se guardan un hash. ¿Cómo lo hacen en Trupal 8? ¿Sigue la misma política de Trupal 7? Do you want to just repeat that in English? Okay. Bueno, en la versión de Trupal 6, los passwords de los usuarios se guardaban en M5, sí? He's saying that in Trupal 6 user passwords were stored in M5 but in Trupal 7 it is a hash. So, well, I really don't know how is it in Trupal 8 but how are you dealing with that? It's dealt with in the same way it was between the upgrade to Trupal 6 to Trupal 7. I believe it's actually the same code just running in a different place and I believe if I'm not mistaken the format is, I think it's the same between 7 and 8. The hashing strategy is the same. So it's the same idea that it did from Trupal 6 to Trupal 7. It will convert them and it deals with it in a way that's secure. So I don't know the specific details because I haven't dealt with this in D8 but I have looked at the function in D7 and it does a transformation and that code has been brought over. So, yeah. Other questions? Yes. Here. Hi. Yeah, can I speak it in Spanish? Do you think so? Oh, my god. En relación con la migración de Trupal 6 a Trupal 8, ¿verdad? ¿Cómo sería más o menos en la migración de Trupal 7 a Trupal 8? Sé que todavía no está lista pero según su experiencia ¿Cómo creen que va a ser? You mean like what is our experience of trying to do things? No, I'm saying that now it's not ready to migrate a migration process to Trupal 7 to Trupal 8, ¿verdad? But you know how to do it with Trupal 6 to Trupal 8. Now, how do you think that going to be the migration process in the future, of course, about Trupal 7 to Trupal 8? The same strategy, exactly. So we will put a copy of the Drupal 7 templates. The same strategies will apply. If you go to Migrate, Upgrade, User Interface, you just put in the database credential, it will detect that it is Trupal 7, it will know that it understands Trupal 7 and it will run them. So this is why we have Migrate Module and Migrate Drupal Module, so that the Migrate Module is generic and it can run any platform and then Migrate Drupal is just this specific. So, and then on Drush, again, same thing. So you just list the name of migration. In that case, the name of migration will be D7 underscore user. So the naming will be different. I think we've been called for time, so thank you, everyone. Gracias.


Have you ever read a comment on your videos that makes you question yourself and it just makes you feel bad about what you're doing? If you have, let's talk about that. Hey Freedom, what's up? Welcome to Freedom Central, the home of all freedom content.  In this episode, let's talk about why they do what they do and how to stop them from bothering you. So first and foremost, what are trolls? Trolls are people who prey on online people to get them to say something they will regret or they want to ruin someone's day. The size show, however, categorizes trolls as someone who irritates others for the sake of a joke. They also categorize these people as griefers in online gaming. Have you ever encountered someone like that? Let us know in the comments section below. Anywho, you might be wondering why trolls do what they do. Experts and I mean psychologists, they say that these two things are what makes them do what they do. So number one of that is dissociative anonymity. This means that people online are able to hide their identity from the online community, meaning there will be no consequences that will trigger or affect their everyday lives. So in a way, they do this because there will be no repercussions, which in a way is kind of true. Nowadays, people can make a fake account and comment away on Facebook, on Instagram, on YouTube, and other social media sites. Number two is minimal authority to enforce internet etiquette. So unlike in real life, there's a lot of people who will tell you that you are doing something wrong or you're doing something right. And also, there are authorities that can actually arrest you for doing things that deems to be destructive or even harmful to other people. But on social media, Facebook, YouTube, or other social media sites, there are minimal authority figures who can actually reprimand you or even arrest you. So in a way, essentially, there are no repercussions. Now we kind of understand why these trolls do what they do. Let's talk about the type of trolls out there on the internet. These are just some of the types, but actually there's a lot, a lot more. Number one type of troll is the self promoter. Have you ever had a comment on your social media that just promotes other content creators or even worse, their own YouTube channel? They just pop out of nowhere and put self promotion bomb down on your comment section. Number two is the casual perv. These trolls are one of the nastier ones. They will misconstrued everything you say and turn it into a distasteful green joke. Stay clear of these ones for they will make things inappropriate real fast. YouTube takes offense to comments that are perverted and it's your responsibility to clean it up. Number three is the grammar nuts. They will completely make your day go from good to worst in a second or two, not only that they will blatantly tell you what's wrong, they'll also try to make you sound really not smart. Number four is is that all you can say type of troll? Have you ever had an argument or discussion from another person and you're trying just to think of an intelligent answer, then all of a sudden this guy says, is that all you can say? I mean does not that grant your gears every time when that happens, especially in video games where you guys are discussing what happened wrong and what you could have done. It's no different from the grammar they make you feel very little of yourself. Steer clear my friends. Now we know what these trolls are, now let's talk about how we can avoid these comments or maybe we can have a smart approach in answering their questions. Here are some tips you can do to steer clear from their ire and maybe be the better man or woman. Number one is wait. Waiting sometimes gives you the time to think about what you want to say and keep you from making mistakes that you will regret. Be calm, collect your composure then think about what you want to say. In that way you can make less mistakes and be the better person. You can always shoot them with kindness. Remember those bullies in your school where they kind of give up when you try to pacify their attacks against you with kindness. Well you can do that too to defuse attention and make yourself look good.  Number three you can block or report them. Yep sometimes these trolls will get the best of you. Report them to your local authorities or you can simply block them. Sometimes when things get really really alarming and disturbing and you feel that you're not safe, always make sure to keep yourself safe by reporting and blocking them. Number four ignore. You can ignore them if what they said is distasteful. Sometimes there are comments that just needs to be a comment. No need to fan the flames and give attention to people who will just want to ruin your day. So to recap guys, trolls are people who will just say mean things that are sometimes uncalled for.  Now you can always ignore, answer with kindness, block or report or wait so you can come up with a witty answer or an educated one. Do you have any friends who are having trouble with trolls? Share this to your friends so you can help them out. Before I leave you guys, please don't forget to like, subscribe and ring that notification bell icon. This has been Freedom Quick Tips and I'll be seeing you guys on the next episode. Goodbye!


Hey guys, welcome to SS20 Tech Social Decide and today we are going to see about the triggers in the ADF pipeline. So what is the trigger and where we can use it. So basically it is used to execute the pipeline. So in the previous videos we have seen to execute the pipeline for the debug option. So in the debug option we can manually execute the pipeline. But in case of the trigger we can also execute the pipelines with manual option and we can also schedule the pipeline. So that in a specific time period pipeline will be executing. So a pipeline run in the SEO data factory defines an instance of the pipeline execution. Next is the pipeline and triggers are having many to many relationship. So what it mean. So for example if we are having a trigger and a single pipeline. So we can execute a single pipeline with multiple triggers. So for example here we have trigger one trigger two and trigger three. So all these three triggers can execute a single pipeline. Similarly if we are having these three pipeline and we want to execute by using a single trigger. So that we can also do that. So that option is available in case of the triggers. So go to on the browser and we'll see in the practical. So here we are if you have remember in the last videos we have created this pipeline that is copy data. If you haven't watched the video of the copy data activity. So I'll provide the link of that video in the description of this video. So you can watch the video before going forward. So here as you can see in the top side we are having this debug option. So we have used this debug option multiple times. This time we are going to use this add trigger. So while we are going to click on this. So here we can see have the option for the trigger now and new or edit. So while we are going to click on the trigger now. So this will be the manual operation and it will be going to execute only once. So let me click on okay. So this pipeline will be executing. So as you can see it's running. So now it's executed successfully. So for checking this trigger we can go in the monitor tab and we have also discussed about the monitor tab. So here inside the pipeline run here we can see the option for the trigger. Let me click on the trigger. So we have just executed this pipeline. So it is executed successfully in 10 seconds. And here we can see the run start date and run end date. So all the information are available for the trigger execution. So this is the manual execution of the pipeline. We are having the multiple options while going to add the triggers. So let me go to the next slide and we'll see the types of the trigger. So here we can see the three types of the triggers. First is the schedule trigger. Second is the tumbling window trigger and third one is the event based trigger. So these three types of triggers are available inside the area. So while we're talking about the schedule trigger, so a trigger that invoke the pipeline on the wall clock schedule. So what it means? So for example, if we want to execute our pipeline on the daily basis at six o'clock in the morning, so we can schedule that the trigger on that pipeline. So it will be going to execute on the daily basis at six o'clock. So that is the schedule trigger. Second is the tumbling window trigger. So a trigger that operates on the periodic interval while also retain the state. So the tumbling window trigger and schedule triggers almost the same. But we are having some additional feature in the tumbling window trigger. It can be executed on the periodic interval like every 24 hours, we want to execute the trigger and it will be going to start at six o'clock in the morning. So it will be going to execute on the daily basis and it also retain the state. So if you haven't understand about this, so don't worry, I'll create a separate video for the schedule trigger and tumbling window trigger in the event based trigger. So a trigger that responds to an event. So for example, if any file arrives on the blob storage or if any table is created or inserted data, so such type of events is happening then after we just want to execute the trigger. So that option is also available under the event based trigger. So go to on the browser and we'll see about the types of the triggers. So here as we can see we have this option new or edit. So either we can create the trigger from here or we can go in the minus tab and inside the minus tab here we can see the option for the triggers. So we can also create the trigger from here. So let me click on this create. Here we can specify the name of the trigger and after that we can see the type. So first is the schedule trigger. Second is the tumbling window and after that storage event and custom event. So the storage event and custom event is the type of event based trigger. So in the next video we will see how we can create the scheduled based trigger. So thank you so much for watching this video. If you really like this video please subscribe our channel to get many more videos. Don't forget to press the bell icon to get the notification of our newly uploaded videos. See you in the next video.