Tako, prema plikacije, da vse z vsej teg vzivnih gavitov, gaviti se veliko vzivno od slodnjiženju z vsej gavitajske, ki vzivno vsej gavitacije je naživno, prizivno, kaj je način vzivno, da je vzivno, pomečnje, vzivno, pridej. Ljube, kar od odmahaj, skopir od zelo, ispešenik na svojo, pletite, kak je. 9.8 m per sekund. The earth gravity acceleration is supposed to be constant, but there are small changes over both space and time. We normally use in geophysics the micro-gal as the measurements unit, which is 10 rise to minus 9g. Zelo izgledaj biti in izgledaj biti v tem veliko hrdi, in izgledaj biti in stvari. In da je pripočenja masova izgledaj biti ne vsak pristopirč, in da je izgledaj biti in stvari je bilo zelo izgledaj biti. In da je učiljena masov izgledaj biti in izgledaj biti. Druga je, da v trgahem pristini skupi so jazne v večsid, lahko je 10 Picture 2 – 7z, no že크 in se začujemo mene jazne, in tudi je etne o večsid, na čistih instrumentu imajo. Gremirjev tebno meže odvarjenja vnenju vratin, in tudi barem dve stavit Stravanie, tudi skupi in izgledanje, Sredinječki instrument snes prezip nespečne zčužite tyi povednih spremnih povednih, evolvečna in tačno v terzove in tračne obenje tudi. PLAAzOKO in z vz Mondičnih instrumentami je nezavala, in nekaj ima včeska, ki je naredilje iz kvalita pravdi. Proti za prosesnimi gravidami iz čistim pos exemploem, vsečenje. V geofiziku da smo počutili vsečenje način, da imače vsečenje masov v zelo, nekaj da smo počutili taj začin, tako da smo počutili, kako vsečenje masov vsečenje način. Taj začin je vsečenje kaj smo pričasnili o stati gravimetry. Vzpečenje to je posledno za vse počičje, in pravno postavimo, da bi lahko se zinojimo, in da se dovoljimo in pričasnimo. Če lahko se vzpečenje za raziljene in raziljene vzpečenje za raziljene učenje. Vzpečenje raziljene je vstupenje in taj delče efekte, efekte, kaj do zelo začetanje izbih, zelo začetanje in zelo začetanje, ki boli nekaj spas, nekaj nekaj vših kajte odkrati v posješenju, nekaj pojavnih pojavnih, zelo začetanje in efekte, kaj do zelo začetanje izbranje izbranju, na zelo začetanje. So her tides are due to the attraction basically of moon and sun. And you can see here, here we have the model of the tidal effect at Etna and Kilauea during about 20 days in 2013. You can see that there is an effect up to about 250 microgals and it's naturally different depending on the position of the observation point. As for effect of a space, so we must correct, if we have an observation point here, since it's at a different elevation with respect to the reference, we must correct for this different elevation. And this is due normally using a standard gradient, which is this one, free air gradient. Also we have to correct for the fact that between the observation point and the reference there is not a void, but there is some mass. So the first order correction is done through the bouge correction, which assumes the presence of an infinite slab with an elevation, which is equal to the difference in elevation between the observation point and the reference. And so the standard value of this correction is this one. And also we have to correct for the fact that we have masses in excess and in defect with respect to the bouge plate. And so this is called terrain corrections. Once all these corrections have been performed, we can develop our bouge map, which is a map now only reflecting the distribution of density below the surface. So this is the bouge map for etna, which has been developed using data published by Schiavon and Lodo in 2007. And here you can see that you have two main components, a regional component with this trend here, which is mainly due to very deep structures. And also there are some residual anomalies, like this one here or this one here, which are due to shallower structures. We are usually interested more in the residual anomalies, so the regional field is usually filtered out through different techniques. And for example, if we invert for etna these bouge anomalies here, we get these maps. So these are maps of the density distribution with respect to a medium value, reference value, which has been chosen by the people who did this inversion. And so we have density in excess, so in effect with respect to this reference value. So here we have density maps for two elevations, two and four kilometers below the sea level. And here we can see that there are many density anomalies in this map. One of these is this one, this density high, which is in the southern part of the Valedalbove here. And we can see it also here. It's interesting because the same anomaly is also found in the seismic tomography. You can see it here and here, same elevation, so with the same, more or less the same features. So this gravity high corresponds to high velocity body, which is actually a plutonic body at an elevation between two and, more or less, eight kilometers below the sea level. Another application of static gravimetry is this one coming from Piton de la Fornes. Here these rotors made a detailed profile across the lava flow that was produced by the 2007 eruption. And this study was done because before reconstructing the roads, the local authorities wanted to know where there was the possibility to have some tunnels in the lava. Because this could be a danger for the people involved in the work because it could be a problem to work with very heavy machines over the parts of this lava flow where there could be some voj. So the authors made this study, and through gravity they could identify zones where it was likely the presence of a tunnel. So switching to changes in time, this is a scheme by Torge, which can be found in this book by Torge, published in 1984. And here you can see that among the different processes that can use time changes, non-tidal time changes, volcanic processes are among the ones that can use stronger changes over time in gravity. You can see that we can have some hundreds of microgal changes. And this book was published in 1984, and here they said that the period of these changes could go between one day and a few years. But actually later studies demonstrated that we can have also changes over time scale shorter than these and down to a few minutes, actually. So gravity anomalies depend on the characteristic of the source, and we can have a great range of possibility as a wavelength of the gravity changes, periods, and amplitude. The amplitude and wavelength depends on the mass involved in the depth of the source, while the period depends on the evolution speed of the process involved in the change. And so, since this period can range between minutes and actually years, we perform both continuous measurements and time-lapse measurements. Time-lapse measurements are that the volcanoes are usually performed through spring-grime meters, so relative instruments. And so each campaign is referred to reference points. This is the gravity network of Mount Etna, and you can see that here we have reference points, so all the measurements are referred to this point, where we assume that the changes induced by the activity of the volcano are very small. And then the, since the campaign are repeated every few months or even years, these kind of measurements are normally used to detect changes over long-time scales. So usually changes over long-time scales are related to processes that also induce pressure changes, so usually this kind of gravity changes are interpreted together with deformation. And one of the most used forward models in analytic formulation is the Mogi model to interpret jointly gravity and deformation. And this model predicts that the ratio between variation of gravity and variation of elevation is linear. There are other models that are used to invert jointly gravity and deformation changes. For example, the analytic expressions proposed by Okada and Okubo can account for the effect of tensile fault, while the model proposed by Okubo can be used to predict the effect of intrusion in a fractured zone, because this model accounts for intrusion inside the pattern of small cracks which are uniformly distributed inside this narrow fractured zone. So these models do not predict a simple linear relation between deformation and gravity. So usually when we assume that the gravity changes and the deformation are due to processes involving the dynamic of Mogi source, we can use this framework, this scheme to assess the likelihood and also the type of volcanic activity. So if the ratio between gravity changes and elevation changes cluster along this line, the boge corrected fear gradient, we are in a situation where there is a pure mechanism of magma intrusion. This has been seen several times. For example, in this case, in the case of the Isobolkano in Japan during this arrest, during this elapsion phase between 1998 and 2000, we had very strong gravity and elevation changes and the ratio between gravity and elevation cluster actually around this boge corrected fear gradient. So we have in this case the intrusion of magma with the density very close to what is expected, 2.4 grams per cubic centimeter. In other cases we have that the points are clustered somewhere between the two lines, the boge corrected fear gradient and the fear gradient, so somewhere here. And this can occur because of two reasons. One is that we can have that the arrest processes driven not by only magma but by magma plus gases. So we have in this case that the density of the material is lower than expected. We don't have points clustering along this line but rather points clustering in this space here. Otherwise we could have a situation like this one where the arrest process is driven by hydrothermal fluids. This is a case referring to the arrest phase between 1980 and 1984 at Camp Le Fegré and this arrest phase was found to be to be due to a material with a density between 0.1 and around 1 gram per cubic centimeter so a density much lower than magma. And so this result, these results point to the regression of fluids in the hydrothermal system rather than intrusion of magma. In other cases we have that the volume of magma which is deduced from the study of deformation can account only for a small portion of the volume of magma which is needed to explain the gravity changes. Like in these cases in this case here these are measurements from Kilauea, measured between 2011 and 2012. And here you can see that the volume of magma deduced from deformation can account for less than 10% of the mass addition that we need to explain the gravity changes. So even though we have the pattern of deformation and gravity are well correlated over space we have this discrepancy. So we must assume some kind of mechanism able to induce bulk mass changes without volume changes and for example substitution of less dense magma with higher density or feeling of open spaces around the magma chamber. So this concept of excess mass also works in cases of deflation. Here we have a situation where the deflation the volume during the phase of deflation in Iceland deduced from deformation is much less that the mass decrease that we need to explain the gravity changes. And so the explanation given by these authors was that a part of the volume needed to explain the gravity change was actually due to this volume change was actually compensated by the formation of gas bubbles inside the magma chamber. We also have cases where the gravity changes are the only change that we have so we have strong gravity changes without deformation which is comparable with these gravity changes. Like in this case here this case refer to the the changes which were observed between 1990-1991 at Etna and so these changes observed before the 1991-93 eruption and so we have very strong gravity changes associated with very small deformation and deformation with a pattern which is not in keeping with the pattern which would be associated to this gravity change. And so in this case the author concluded that gravity changes were due to intrusion of magma along pre-existing open voids in particular along fracture here so from the central conduit going towards southeast. There are also cases where we can have that the gravity changes are not directly related to the dynamics of magma at Etna between 1994-2001 we observed strong changes which were associated to a source in the south-distance sector the volcano, a quite shallow source about 2 km below the sea level so we have both positive and negative gravity changes and the negative phase are associated with a stronger release of energy and this seismic energy was released from a volume which is in the same position as the volume, as the gravity source actually. So here we compared the gravity change at one station around here in time with the strain release which was reduced for a linear trend and also was multiplied by a negative coefficient here. A strong coupling between gravity and strain release this is actually anti-correlation because we multiplied the strain release by a negative factor. So we have the situation where gravity changes acute in a volume which is separated from the volume where the pressure source deduced from the formation was placed which is in the northwestern sector of the volcano and is actually deeper than the gravity source. So interpretation that was given was that these gravity changes were due to changes in the rate of micro fracturing along pregsysting fractured zone in this position here and also in this paper we proposed that when a structure link formed between the pressure source and this pressure zone the magma used this pressure zone to reach the surface and there was the breakout of the 2001 eruption. So this is a quite complicated framework where we have deeper pressure source beneath the northwestern flank of the volcano giving the deformation most of the deformation observed during the period while the gravity and seismicity were mainly driven by changes in the rate of fracturing along this fracture zone here in another position and this mechanism worked until the breakout of the 2001 eruption and so we think that this eruption actually changed this kind of framework somehow because we didn't observe this pattern of changes anymore after this eruption. So switching to continuous gravity changes so continuous gravity measurements these measurements are usually done through spring guide meters and because of some limitation of these instruments they don't give high quality data over periods longer than say some days this is because these instruments are affected by many parameters mainly by temperature and also they are affected by instrumental drift here we can see quite long records from Etna and Kilauea and we can see in both cases we have quite linear drift over the record and also the both records are modulated by the seasonal component of temperature so if we use a good setup with suitable protection against temperature we can limit this effect and in many cases we observe that the strong correlation this is analysis in frequency domain and we can see that the high correlation is only found over the lowest part of the spectrum so we have a period range which is free from temperature effects and the period range which is affected by these temperature changes and so this period range is up to some days so that's why most of the past studies about continuous gravity changes are focused on processes occurring over short time scales so the process is able to induce changes of these time scales are processes related to the dynamics of involving magma and gas in the upper part of the system of the volcano and we can have different processes here we can see only some of them for example if we have a big slag raising along the conduit we will have actually a body with a very low density being progressively closer to the observation point where we will have gravity degrees also if we have accumulation of the form liar in a position relatively close to the observation point also in this case we will have gravity degrees we will observe gravity degrees and also fast magma movements in the conduit or along a rift zone depending on the position of the observation point with respect of the magma moving will give a change with a positive or negative also the mixing of magma with different densities can give gravity changes this is a study where the authors simulated the mixing of magma in a shallow magma chamber and you can see that in different cases at different distances between magma chamber we will have gravity changes over periods as short as a few minutes let's say a few tens of minutes so the first case of study comes from Kilauea where in 2011 there was an eruption along the east rift zone 10 km from the summit active vent this is a case very similar to what Claude Jobar was talking about yesterday because there was a sudden decrease in the level of the lava lake here in the summit crater and soon after this sharp decrease there was the eruption so the idea is that the magma from the central conduit that's why we observed this sudden decrease in the level of the lava lake so we have many data about this this process so we have data coming from a gravity meter that was installed very close to the lava lake only 150 meters and also we have the images from a thermal camera here in the edge of the crater and looking at the surface of the lava lake so these are two images coming from this thermal camera and so this movie is a movie where we synchronized the images from the thermal camera with the gravity change so we have a difference in time because this is Hawaii local time in GMT time from gravity and so we can see that as soon as we have a decrease in the level of the lake we will have a decrease also in gravity at the same time which is quite impressive and so afterwards the gravity reaches a new level which is more or less 150 migragalts lower than the previous level I mean they are real but if you consider that the gravity meter is at the same time measures gravity acceleration and inertial acceleration so it behaves as a seismometer basically so since there was some seismic activity also we have for example this one is an earthquake we don't need to correct for that because the only information we need at this time is just the development of the decrease so you can see also that the noise here which is higher than the noise here is because of the eruption so I guess it's because of the transferring of this magma transferring from the central conduit to the rift zone so that's why we have this increase in the background noise so what we did it was to try to invert the the gravity data to find the density of the material inside the upper part of the vent and to do that we used the numerical model of the vent taking into account its real shape so using this model and the images from the thermal camera we could calculate the gravity effect due to a change in the level of lava inside the vent so basically we have gravity here lava level deduced from the images of the thermal camera and here is GPS so we corrected the gravity for this also for this deformation which accompanied the decrease in the lava level and so to get a good fit between observed and calculate gravity we had to use a very low density a density which is actually lower than water and that means that this upper part of the system is actually very rich in gas bubbles more than half of the material inside its gas this analysis was extended of a much longer period about 4 years so here you can see lava level ground tilt and GPS and also gravity you can see that lava level and tilt and also GPS are very similar to each other very correlated while gravity doesn't seem to be correlated because of other effects like temperature and the effect of gravity is very correct for the seasonal part we still don't see any coupling between gravity and lava level but actually if we go to shorter periods for example these two ones here we can see that actually there is quite close coupling also between gravity and lava level in the two cases so we used wavelet coherence analysis to try to calculate the correlation between ground tilt and lava level and here you can see that there is a very strong correlation of wavelet scales that correspond to periods between about one day and a few months and this arrows here point towards the right means that this is two phase correlation so there is no time delay between lava level and tilt also we performed correlation analysis of 15 days window running along the signals and the results shows that the ratio between lava level and tilt it's quite constant in time and the average is 0.17 which means about 5 to 7 meters per lava level for micro radiant the same analysis was performed between gravity and lava level and here we can see again that the correlation is not as good as before because of the perturbations of the gravity signal but still we have some correlation in some times and also in this case the correlated part of the diagram we have in phase correlation we also performed an analysis of the same time window in this case for each step of the window we calculated the density needed to explain the gravity changes considering that all the gravity changes was due to the change in the lava level so what we get is that the density seems to increase during this period from a value of about 1 to a value of about 1.5 gram per cubic centimeter and so this could be an actual change in density otherwise could be due to the fact that the size of the event was increasing because here actually we are measuring not a real density but rather increasing the mass involved in the process so it could be a real density but also it could be the fact that the event was during this period was actually getting larger well apparent density means that we did this calculation we actually tried to calculate the best density that can fit our data but we are using always the same model for the event so if for example there is a difference in the geometry of the event this means that this is not real density it's a change in the mass involved in the same change of level so it means that we are not measuring a change of a time of density we are measuring a change of a time of the mass involved in the same change of level so that's the sense of this apparent density so if it's interesting to see that if we combine the two equations the question for the lava level change and the question for radial tilt assuming moggy source we see that our ratio the ratio we found before depends on the density of the material inside the conduit it's also related to the dimension of the magma chamber and also the position of the magma chamber itself and so if we use the value we found for the ratio and for density we find that the other parameters are as expected from previous publications and so this means that at least over the time and space scales that we consider that the system behaves elastically had the data from Kilauea here we can see that we have data from these two stations one very close to the active vent the other one about two kilometers from the vent so this is the signal acquired in May 2010 and we can see that the wavelet transform of the signal shows two main components this one with a period of about 30 seconds and the other one is this one with a period of about 150 seconds so this is basically seismic noise while this component here that we can see in this chart here which is actually a zoom of this part from the two signals which has been filtered around 6.7 millihertz and we can see that there are these oscillations very well correlated between the two instruments the amplitude it's larger in the instrument which is closer to the vent to the active vent and so considering this ratio between the amplitude of the oscillation at the observation sites we have that the source can be again the shallow magma source beneath the north-western, north-eastern part of the Alemaumau crater and so we propose that this oscillation were due to density inversion related to convection inside the shallow magma chamber so assuming that the convection was driven by thermalist abilities with some calculation relating the time scale of convection to the position inside of the reservoir and these calculations suggest the temperature contrast which is in keeping with the density gradient that we need between upper and lower part to explain the gravity changes that we observed so the last case of study comes from Etna where in the summer of 2011 we stole a gravity meter very close to the summit praders at the distance of about one kilometer from the summit praders and during this the period of the installation there were a sequence of nine lava fountains from this crater here the news of this crater so there are many past studies that propose that these lava fountains are triggered by the collapse of the form layer that accumulates somewhere in a shallow position probably at the roof of a small magma chamber which is at shallow depth beneath the summit praders and so we observed before each fountain we observed the gravity decrease at the station very close to the summit praders and so we propose that this gravity decrease could be due to the accumulation of the form layer in this position here in the top of this magma chamber and actually this gravity decrease occurs during the phase of the strombolian activity preceding in development of the lava fountain here we don't have data during the lava fountain because the volcanic tremor is too high and so gravity data are impossible to use because they are too noisy in this part here so in overview of what we have seen so the term gravity changes are usually interpreted together in the ground deformation and by coupling gravity in the formation we can have more information about the processes which are driven the arrest of the eruption in particular we can have information about the density of the intruding material which is important because we can distinguish between magma versus intertermal processes or also we can see processes that induce mass changes without deformation like in the case when magma moves through open fissures in the upper part of the plumbing system or we can detect complex processes involving beside the direct effect of magma also second order effects like changes in the rate of fracturing of the medium using continuous measurements as short term changes that are related to the shallow dynamics involving magma and gas in the shallow part of the plumbing system of open conduit systems and from gravity we can have information about gas segregation for example possibly leading to explosive events like we have seen lava fountains or density inversion related to convection or rapid transfer of magma from the conduit to the lateral zones and that's all, thanks


Welcome to the project briefing of the American Congress Digital Archives Portal. My name is Danielle Emerling, and I'm the Associate Curator for Congressional and Political Archives at West Virginia University, and the Director of the American Congress Digital Archives Portal Project. This project seeks to digitize and aggregate the primary sources of the U.S. Congress to make them more discoverable and accessible. The project focuses specifically on the personal papers of members. Personal congressional collections are created in the offices of members of Congress, and the collections are usually named for a member. But the collection names often obscure their breadth of content. Members' personal papers are invaluable for understanding legislative decision-making, constituent voices and opinions on policy topics, political processes, and America's social and political development over time. Despite their value, congressional archives are underutilized resources. Scholarly interests and trends are partly to blame, but significant practical barriers exist. Unlike presidential papers, which are centralized in one location, members of Congress choose the repositories for their collections. This means congressional collections are geographically dispersed among institutions large and small, with varying degrees of resources for processing and providing access to collections. The collections themselves are extremely large and often contain multiple formats, demanding several years of archival processing. For scholars, collections may be difficult to use, both because of a lack of travel funding and the varying levels of description in congressional archives. Those of us working in archives and libraries know that the pandemic has only exacerbated these challenges for archival research because of travel restrictions, reading room closures, and shrinking travel budgets. So what do these barriers look like for a researcher using congressional archives? Imagine that you are researching a policy, let's say the Children's Health Insurance Program or CHIP, a measure passed by Congress in 1997. If you wanted to better understand things like lawmakers' decision making or their bipartisan coalition building, you would want to find primary sources in the archives of the lawmakers responsible for CHIP. You can see here that I've mapped out your research trip for you. Your research almost certainly would take you to my home institution to view the archives of former Senator Jay Rockefeller. You would also need to research in the archives of two of his closest collaborators, Senator John Chaffee and Congressman John Dingle, which would bring you to the University of Rhode Island and the University of Michigan. You might also be interested in the complimentary proposal put forward at the same time by Senators Orrin Hatch and Ted Kennedy, which would then take you to the University of Utah and the John F. Kennedy Presidential Library in Boston. With your research budget, this trip is completely unrealistic. You may decide to visit one archives or to forego congressional archives entirely and make a single trip to the Clinton Presidential Library to study CHIP from the president's perspective. The American Congress Digital Archives portal will significantly improve these challenges by aggregating the personal papers of members of Congress into a single online platform. Through this nonpartisan project, we are making research and congressional archives easier and more equitable and sharing the value of these collections with new audiences of researchers, educators and the public. We are completing a foundational phase of the project made possible by a grant from the National Endowment for the Humanities. We have also received support from the Association of Centers for the Study of Congress. In this phase, West Virginia University Libraries has partnered with the Robert J. Dolt Institute of Politics at the University of Kansas, and the Robert C. Byrd Center for Congressional History and Education. We're also working with an advisory board composed of leading individuals in the areas of congressional archives, scholarship and digital archives. In this phase, we have documented metadata standards and policies, developed portal prototype, conducted usability testing and a research priority survey, and planned for future phases of the project. Our portal prototype currently hosts more than 500 archival objects from the three partner institutions. To guide this work, we've articulated digitization and metadata standards, as well as guidance around issues like privacy and intellectual property. The site is developed using Samvera and will provide open access to both the content and the metadata. You can see here an image of a document in the portal with its accompanying metadata. Users of the portal can open this PDF to view a larger version and use a find or search option to search the OCR text. In the metadata, anything highlighted blue is a link that will open other relevant materials. For example, if the user clicks the link in the coverage Congress field, they will be able to view all materials from the 89th Congress that are available in the portal. An exception to this is the link to the collection finding aid field, which will take the user to the institution's finding aid for the collection from which the material was digitized. In the last quarter of 2021, we conducted virtual user experience interviews to help us improve the site's usability. Interviewees were asked to complete three search tasks and rate their experience. Over 20 interviews with archivists, political scientists and historians, users gave the site an overall satisfaction score of 87%. Overall, users appreciated the ease of using search and search filters. Reactions to the site layout and navigability were also positive. Users also recommended some improvements, such as better aligning the search bar and search limiters, adding an advanced search option, decreasing the amount of metadata fields and search results for better scanability, improving the ability to sort by date, and adding the ability to sort by material type, creating a citation tool for individual items, allowing API integrations to better support quantitative research, and featuring more dynamic content on the homepage, as well as adding subject or research guides. Because of the size and number of congressional collections, we know we can't put everything online. So in this early phase, we gathered data from potential users that will help us prioritize our efforts. After gaining IRB acknowledgement, we conducted a survey in October and November of 2021. We asked demographic questions and questions about research topics and preferences, research methods with digital archives, and instruction with congressional archives. We received 126 responses. We found that most respondents identified in the disciplines of history and political science, and most identified as faculty. The vast majority, 97% of respondents identified as archives users, and a significant number 85% said they have used congressional archives. We also asked respondents to tell us about their past research projects, as well as aspirational projects using congressional archives. We did this in two ways. We asked them to rank their research topic priorities related to Congress, and we supplied the topics for ranking. Second, we provided a short answer question. And the results from the ranking question, you can see there's not a vast difference between each of the topics, but it gives us some ideas about where to start our efforts. For example, the number one rated topic leaders and parties could include materials about elective elected leaders, leadership activities, party organizations and party continuity and change. Number three rules and procedures includes things like lawmaking processes, congressional reform, and how a bill becomes law. Some of these topic areas are illuminated further in the short answer question, in which we asked respondents what topics, issues or people they have studied, or would like to study in congressional archives. Here's a snapshot of those responses. The top ranked topic areas, such as leaders and parties decision making rules and procedures and elections were also frequently mentioned and are reflected in the categories Congress and government operations and politics. One ranked topic that is perhaps more important than respondents it indicated is Congress as policymaker. Many of these open ended responses deal with the creation and history of specific public policy. The most prevalent of the policy areas mentioned by respondents include civil rights and liberties, agriculture and food, armed forces and national security and international affairs. As we make plans to add more content to the portal, we will ask partners to correlate their collection materials to priority areas. We also asked respondents to indicate the importance of different document types out of a list of 24. You can see the top 10 list here. Many of these document types correlate to the topic areas ranked highly by respondents, such as leaders and parties, but also to Congress as policymaker and Congress as a representative institution. Finally, we asked respondents about their experiences with digital archives and instruction. Most participants who responded indicated they have used digital archives, but the majority have only engaged with basic search, rather than advanced methods such as text mining. When searching and browsing digital archives respondents identified the most helpful categories as topic person name and date. The participants who responded have not used congressional or digital archives for instruction, but indicated that somatic document sets are or would be the most helpful instructional tool. Respondents who have used archives for instruction identified learning outcomes that relate to primary source literacy core ideas, or to subject knowledge acquisition. So we conclude this foundation phase of the project. We are planning for the future. Our immediate goals are focused on developing the portal. We will continue to develop with open source applications, namely Sam Vera, and contribute new findings back to the community. We plan to contract with the web and application development company to help us scale the project. We have the application from internal hosting to the cloud, and we will transition from hosting content to harvesting content will also be updating standards policies and procedures to reflect this new model. In phase three, we plan to expand partnerships and portal content to complete development for the nation's 250th anniversary in 2026. We will expand the number of partner institutions with a goal of including at least one institution from each state. With more partners will also be adding more content to do so we will use the data from our survey to guide content selection. Additionally, we want to focus on the contributions underrepresented people and communities have made to Congress by including the archives of women, Hispanic, black, Asian and Pacific Islander and indigenous Americans, as well as Americans with disabilities, who have served in Congress. Right now, the formats represented in the portal are primarily texts and photographs, but we will expand to include audio visual materials. Development of the portal will also continue as we improve search and fascinating features and add advanced search, as well as the ability to bulk export metadata from search results. During this phase, another goal is to support public facing scholarship and civics and history education programs that use materials from the portal. Additionally, with the ability to bulk export metadata, we will have the opportunity to support more computational data driven approaches to studying the materials in the portal. With our partners, we will also create a governance plan to ensure the project is sustained and staffed beyond soft funding and beyond 2026 phase four will be about continuing to add partners and content and supporting scholarship and educational initiatives. Development of the portal application will transition toward maintenance. The most important part of this phase will be implementing our governance plan to sustain the portal into the future. Earlier, you imagined you were a researcher, potentially traveling to many different archives to investigate a single policy. But now imagine that you are able to do that work from your home. Imagine if congressional archives from all 50 states were represented online, and a broader audience of researchers, educators, and the public could better understand what Congress does, how it does it, and why it's important. The time in which America is experiencing deep political division challenges to democratic norms and values, and when many, many Americans believe democracy is in crisis. This project takes on new urgency. It has perhaps never been more important for scholars educators and the public to have access to the historical records of the legislative branch. One of our grant proposal reviewers put it well. In part they wrote, researching presidents or courts is vastly easier than researching Congress, a fact that has led to a fairly lopsided historical literature. This project's goals would help remedy this imbalance. We believe this project will do exactly that, and make the first branch of government, the people's branch more discoverable and accessible to everyone. You can explore the portal and access project documentation at congressarchives.lib.wvu.edu, or contact me at Danielle.Emerling at mail.wvu.edu. Thank you for watching.


Alright. Thanks, everyone. My name is Taylor Savage. Great intro. Yeah, my name is Taylor Savage. I'm a product manager here on Chrome on the Polymer project. I'm here with Monica, who's an engineer on the Polymer project as well, to tell you all things Polymer. So I'll start off by talking a little bit about where we are with the project overall and how we think that web components are really changing how we do web development. And then Monica will go into some of the more technical details around how to take best advantage of Polymer of web components to build a really great, high-quality, modern mobile progressive web app. But first off, let's talk about the mobile web. And we've been talking about the mobile web a lot at this conference. It's kind of like the mobile web conference. And there's good reason for that. The mobile web is incredible. There's never been a more important time to have an open, decentralized communication network where anyone in the world can access this information coming from anyone else in the world. And as developers, this is incredibly exciting. You can put something up on the web and a user somewhere halfway across the globe is just a URL away from accessing your application. That's great. But for developers, there's also a dark side to the mobile web. And if you've been doing mobile web development, if you've been really trying to get the best possible user experience across to your users on their mobile devices, you know this dark side, which is that we are at war with phones. Phones are our enemy. There are users best friend, but as developers, they are our enemy. And it can feel like as we're trying to produce the best possible user experience, the phones are fighting against us at every possible turn. Mobile networks are vast. There are over 2 billion users with a mobile smartphone in their pocket to access our web applications.  And that's something that we've never had to really deal with as web developers, as developing for the desktop web where you're plugged into the wall at all times. Mobile devices are everywhere. They're in everyone's pockets. You're a pocket reach away from a great user experience on the mobile web. But that means that mobile phones are fundamentally performance constrained. They need to have this tiny little battery that can power them all day long, and they need for when you take them out of your pocket for them to not burn your hand. And that means that to power, for the battery to last all day to power the sensors and the radios and not to mention this high resolution screen, it's going to be very constrained in the terms of the power that it can actually deliver to the CPUs that are doing your math for you that are running your application. And we've got a lot of tools available to us, a lot of open source tools available to us as web developers to allow us to create these web applications. Then these tools are incredibly diverse and incredibly powerful. But it can seem like more and more the tools available to us are getting continually bigger and continually more complicated. Building a great mobile web experience is hard. It's a little bit like climbing Mount Everest. It's challenging. It's expensive. To really do it right, you need kind of a lot of training and a lot of good guidance.  It should be much easier to deliver experiences on the web to users, especially in this important mobile context. But there's good news. We have a mantra on the Polymer Project. We have kind of a philosophy about how we think we should be building web applications, how what we should be thinking about as we're constructing these new mobile applications to make our lives easier and to make our users' lives better. And that mantra is to use the platform. The web platform is getting increasingly powerful, with new primitives like service worker, like web components, with new serving mechanisms like HTTP2. We have more tools at our disposal as developers than ever that allow us to build and deliver a really high-quality web application. And so it's our responsibility now. In fact, it's our advantage to take advantage of what's already there baked into the browser sitting on our users' devices in their pockets in the form of the web platform. So the Polymer Project is the Chrome web platform's team set of libraries and tools for web developers to help developers take full advantage of the modern mobile web platform, to take advantage of what's right there sitting on the browser. Now, the primary feature that Polymer, the library, has been focused around is web components. And web components is an umbrella term for a set of low-level APIs baked into the web platform, new web platform specs that allow you, the developer, to create reusable, composable components on the web. They create a new component model on the web allowing you to essentially extend the HTML language to create your own HTML tags that get understood by the browser just like any other baked-in HTML tag. Now, if you've been following web components, they've been around for a little while now. So the first spec came out in 2012, which was a while ago.  We were over-optimistic as to the speed at which web components would become broadly cross-browser supported. But this is okay. We went back to work. We went back to work with all other major browser vendors to work out an updated set of these APIs. The idea was sound. Everyone was on board the idea. We just needed to kind of work out the kinks in the APIs themselves. And so I'm very happy to say that as of today, we've turned a major corner with the web components APIs with an updated version of some of these web component specs, web components v1. So previously, web component support was scattered and it was varied. Template was supported across the board across all major browsers. But Shadow DOM and custom element support was either behind a flag or unsupported in most browsers. Today, with web components v1, as you heard earlier at the keynote, this story is completely changed. So all major browser vendors are on board with shipping Shadow DOM and custom elements v1 versions of the specs. In fact, Safari, in Safari 10 that just shipped recently, has Shadow DOM v1 shipped. Chrome has Shadow DOM v1 shipped. It's on the high priority roadmap of Edge. This is a very exciting time for web components. HTML imports are still on hold as we're working out how they're going to interact with ES6 modules. But I'm confident we'll come to a really good solution for how to load HTML with HTML. So I can't say this enough. This is a huge turning point for web components. At Google I.O. earlier this year, I said that cross browser web components was not a matter of if, but a matter of when. And when is right now. Cross browser web components are here with web components v1. Which brings me to Polymer. So the Polymer library, the library itself that kind of forms the soul of the Polymer project is a lightweight layer on top of these web components APIs. And it's designed as an opinionated way to pull together these different low-level specs, these low-level APIs, and make it easy to build for us developers to build a reusable web component, a reusable custom element. Now Polymer started out as an experiment. It has evolved with web components as the web components specs themselves have evolved. So Polymer started out just kind of to test out what would be the different low-level features that we would need as a web developer to create this kind of reusable element to extend HTML. So Polymer 0.5 with the last release of Polymer that was still kind of in this experiment mode. And then after a few years of iteration after working on the specs, after working on the library, it turned out that these web components things were actually pretty powerful. And so last year, we released the 1.0 version of the Polymer library, which was the production-ready version of Polymer. It allowed us as developers to take advantage of web components today in production applications without necessarily the APIs having to yet be shipped broadly across the different browsers. So Polymer has kind of quietly been out for a little over a year. And I think because Polymer started out so much as an experiment with these very early web component specs, we often get the question, who is using Polymer? Is anyone actually using Polymer in the wild? So I want to just name a few of the companies that are using Polymer in production today. So Polymer is used by Comcast, which is the largest media company in the world. It's used by the USA Today, which is the flagship brand of the largest newspaper publisher in the US, GANET. It's used by ING, which is the largest online bank in Europe. It's used by Neta Porte, the largest luxury fashion e-commerce company. Polymer is used by BBVA, which is one of the largest banks in Spain and Latin America. By Coca-Cola, which is the largest beverage company in the world. It's used by Electronic Arts, which is one of the largest game publishers in the world. By Predix, which is the software platform for the industrial Internet of Things from General Electric, which is the largest digital industrial company in the world. And of course, Polymer is used here at Google, actually quite heavily here at Google, on some of our biggest user-facing products. So Polymer is used in Chrome, in the Chrome UI pages, which has over a billion users. It's used in plain music. It's used in YouTube gaming. And just recently, at the Polymer Summit a few weeks ago, we announced that Polymer is actually being used on YouTube. YouTube, which is one of Google's biggest products, also with over a billion users, is now building the next generation of their mobile and desktop applications all on top of Polymer. So there's an immense organizational power that we're seeing to relying on standards. To relying on standards-based web development, you get this seamless, frictionless sharing of code that we've never been able to really, truly achieve across all kinds of different teams on the web platform before. And we're seeing more and more large companies going all in with Polymer, with web components, with web standards-based development using the platform. So a big value prop for web components is that they're interoperable, that you can build a component with browser-based technology, and then share it to other members on your team, share it with other teams at your company, share it with the overall ecosystem, and anyone can take advantage of that component no matter what kind of stack they're using, no matter what the rest of their JavaScript stack looks like. But this is great, but clearly, we've got big projects working with web components, big teams, that want to not just build components, but want to build entire applications. So we get the question a lot, how can I take web components and then build an entire application, specifically an entire progressive web application out of web components? And our answer in the past has always been, well, that's the whole point of web components is there's no one way to build an application. You can choose any of the tools that you're familiar with, anything that you like already, and use that to put together web components into an application. But obviously, that is kind of unsatisfying. And what we realized is that if you take web components, which are one new set of web platform primitives, and you combine them with other new, really exciting web platform features like Service Worker, like HTTP2, you can actually end up with a whole that's much greater than the sum of these individual parts. And so we wanted to put together kind of an opinionated showcase of how all these different features are really designed to come together and make for a really great user experience. And so earlier this year, we released the Polymer App Toolbox. And again, the goal of the Polymer App Toolbox was to go beyond just components and show how components can be put together with these other technologies into complete progressive web apps. So the App Toolbox includes a set of web components, app level components for things like layout and routing and internationalization. It includes a command line tool, the Polymer command line tool that lets you build and deploy your application. And things built with applications built with the Polymer App Toolbox are designed to be served via what we call the purple pattern, a way of using HTTP2 in server push to being able to deliver just absolutely the minimum of what you need to be able to render each view of your application to your users with minimal overhead. And you'll hear more and more about this purple pattern across various talks at this summit. And then in addition to the components and the pattern and the CLI, we wanted to show what you could actually create when you put all these things together. And so we launched shop. Polymer project.org, which you've also already seen in many of the demos up here, a progressive web app that really is just a killer user experience that uses the app toolbox, it uses the purple pattern, it uses Polymer web components to deliver an e-commerce-like application. You can visit that at shop.polymerproject.org. And we're already seeing the kind of value of this Polymer App Toolbox being used by companies to build applications. So take Jumia Travel, which is the travel division of Africa's largest e-commerce site. Now 75% of mobile connections in Sub-Saharan Africa are on 2G. And that's forecasted to still be 45% in 2020. So there's an immense challenge to be able to deliver a rich full application over the narrowest network you possibly can. And so thanks to the Polymer App Toolbox and thanks to web components in the purple pattern, Jumia's Progressive Web App is able to achieve this. They built a Progressive Web App on the Polymer App Toolbox that has twice as fast a page load on 2G and uses six times less data than their native app to be able to deliver the same exact flow. And I think the quote from the Jumia team really speaks to the value and the power of web components, which is that they were able to build a complete kind of prototype of this website, the entire flow in just four weeks, so that they could show it to their management and sell the management that this is a very valuable, compelling experience and then go from there to build the actual production application. So this is exactly what we want web components to allow developers to achieve really rapid prototyping all the way through to production deployment. So we're really starting to feel the momentum of web components. Web components are now being truly broadly adopted cross browser. They're being used in real serious production applications by large companies and here at Google. And this means that it's time to kind of open the next door for the Polymer project. So we're working right now on the next major push of the Polymer Library, which is Polymer 2.0. So we just released the preview version of Polymer 2.0. It's up on GitHub. And there are a few key things that we're focused on when we're designing and working on Polymer 2.0. A few key features and distinctions that from the Polymer 1.0 release. So the first obviously is Web Component V1 support. Web Component V1 are the specs that are going to be broadly shipped across browser that we're already seeing out there and Polymer 2.0 is designed to take advantage of these new custom element and Shadow DOM V1 APIs baked into the browser. Polymer 2.0 also offers better interoperability with other JavaScript frameworks with other JavaScript tools by eliminating some of the Polymer specific abstractions that kind of leaked through in Polymer 1. Namely the Polymer DOM shady DOM APIs and some structured data manipulation that leaked through. So the takeaway is that an element, a custom element built in Polymer 2.0 is truly web native and it will be indistinguishable from any other vanilla Web Component that you might build with any other Web Components framework or just with raw vanilla Web Components. And finally, we don't want to leave Polymer 1.0 users in the dust. One thing that we took away from the Polymer 0.5 to 1.0 transition is that transitioning a major framework, transitioning a major dependency even if it's small is a huge pain point, especially for large companies, especially for large projects, especially for teams of Google that are relying really heavily on Polymer. So with Polymer 2.0 from the beginning, we've designed it with backwards compatibility in mind. So Polymer 2.0 comes with a near seamless backwards compatibility layer, making it as simple as possible to be able to transfer a Polymer 1.0 component to work in Polymer 2.0. And Polymer 2.0 also supports what we call hybrid mode. And hybrid mode means that you can, there's a way to write a component such that it can work on Polymer 1 or on Polymer 2.0. And so what this allows is if you've got lots of components in your application, if you've got lots of components shared across your company, you can incrementally upgrade one element at a time while your application is still live in production. And once all of these components are upgraded to this hybrid mode, you can switch over from using Polymer 1 to using Polymer 2.0 and then continue to take advantage of the Polymer 2.0 specific features. So it's a much, much easier, much smoother, more seamless upgrade process than having to stop all the presses and upgrade everything at once before you put your application back into production. So Polymer 0.5 was an experiment for web components. Polymer 1.0 was allowing you to use and achieve the promise of web components in production. And with 2.0, we can finally realize the full value of web components, which is going web native, which is using, actually truly using the platform, using standards-based cross-browser APIs to use the platform to write less code, to ship less code, to write more elegant, smaller applications and deliver them across the mobile web. And we're actually seeing this use the platform mantra bearing out in the numbers with Polymer 2.0 when you take a close look at how Polymer 2.0 actually works and is built. So Polymer 2.0, if you build a web component with Polymer 2 and you ship it on a browser that doesn't need any polyfill so that supports web components v1 out of the box, Polymer itself is only 12 kilobytes. It's small. And it's getting smaller and smaller. And that is our whole goal with Polymer. We're not trying to build a massive framework. We're trying to build a tool that gets smaller and smaller as the platform fills many of the gaps in our developer experience. So this is using the platform in actual service to the Polymer library. We are just at the beginning of the story for web components. And we're still actively figuring out all the kind of best practices and best ways that we as developers, as teams, as an ecosystem can take advantage of all the things that web components provide. So we've been building web components for a few years on the Polymer team, and we've certainly learned a lot in those few years. And so here to tell you more about how to take advantage of web components in the browser and how to build really killer applications using web components is Monica, an engineer, on the Polymer team. Coming up mid-talk means that I didn't get an awesome Paul Lewis introduction, so I'm super bummed about this now. Hi. So the thing about Polymer and the library is that it's not really about the library itself. It's about what you do with it. And that's building elements. And what I've been thinking about on how to, like, structure this talk, I've realized that when Taylor said that mobile web development is hard, the same thing can be said about element development. It takes a lot of expertise. It's really hard to make a good element that you can put on every page that you have. So I think it's really important to actually talk about it. And what we've been talking a lot about is how to make a good element, that how to make a fast element. And we've given talks about, oh, I'm not allowed to go back. And we've given talks about that. But then I thought about it and there's three kind of people that actually interact with elements. You've got the people who use their elements, who don't actually want to build a good element. They just want to use other people's elements when they're developing a web app. There's people who author the elements and we've been talking about them a lot. And there's people who maintain the elements. And these may be the authors, but may just be other people who've inherited these elements don't really know, like, the intimate details on how this element came to be the monster that it is. So we need to be able to address their concerns too. So I'm going to do two different things. I'm going to talk about the people who use the elements and give you some advice about how you can architect your apps using web components and how we've built some tools for the people who have to maintain those elements. And on the Polymer elements team, we have a lot of experience with this. We initially authored over 100 elements. I think it's over like 130 now, which is kind of a lot. We've spread them across three different orgs to make everything actually really complicated and hard to sync and test together. Why not have a little fun while you're at it? We've used them internally, like just in our team on over 20 apps. And this is important to us, like the shop app, because that's how we come up with advice for other developers. That's how we come up with patterns that you can use. And we're also on the maintaining side of this. It's Polymer elements are used in over 500 apps. These are internal to Google. They're external to, like, some of the companies that you heard about before. So we kind of cover all of those three different areas that I talked about. So let's talk about app developers. It's probably half of the audience. You maybe want to use a web component in your application. How can we make this better for you? What best practices do we have for you? And the best advice that I have is that you should not look at web components as something that they are new. You already know about components. If you've used any language, you've got objects, you've got the ideas of, like, compartmentalizing your code. That's not new. And web components themselves aren't actually new either. If you've ever used an input element or a button, they're kind of like a web component. They're a little nugget of functionality and code and styles that have been put together in a little box and given to you and it has an API. And you know how to use them. You've been doing it for a long time. What's new is that other people can now build these web components that are just as powerful as the input and button. They just have different names. And you should treat them basically in the same way that you've been treating input. So I built this really to demonstrate, like, the next example. I built this really dumb app for the Polymer Summit. It's basically an emoji social network where it's kind of like Twitter and Slack jammed into one. But instead of being useful, the only thing you can type is English and it gets translated to emoji. So the only thing that you see is, like, a stream of emoji. And I'm walking around with a beacon now. I've got my first physical web beacon. So if you're, like, around me, you can actually get a link to it. It's mojibrag.frybase.com. But when I was designing it, I was like, OK, cool. Let's say that I've never used a web component before and I want to design an app with them. What do I do? And it's basically the same way that you would use, like, a normal application. You just think about the features that you have in your application. Somehow I have to authenticate a user. Then I got to show them something like a giant screen of a blob of text.  And once you figure out these features, you can, like, go ahead and dig deeper in each of them. Well, when you write a post, you have to somehow translate from English to emoji. And then if you've got a list of posts, you can, like, like them and see their location and all sorts of other stuff like that. But once you have this idea of, like, what the logical components in your application are, it translates immediately to web components. Your authentication part is done with Firebase Auth, which is an element that does authentication with Firebase. IronList is a thing that manages your list of elements. And then new posts in my app are little web components that I built internally to my app just to, like, logically structure code around. And it was really easy. And the awesome part about components, and this, again, is not new. It's happened if you've ever written a class before. If you've written a component, you can refactor it really easily because it doesn't affect the rest of the app. It just sort of sat there as a standalone thing and you just get to fix its code. So this shouldn't look scary. It's how you would write web components. You could call it a div class equals main screen, but now you can just say main screen as an element. And because web components aren't new and you've been using them in the browser, you just didn't know that an input was a web component, you should use these new web components that you're getting from users in the same way. And that's by using properties and events. If you look at an input, you set all these properties in it. You said it's type, you said it's value. You said whatever, the min length and max length. When an input does something, it fires an event. It fires an input event. It fires a change event. This isn't new. And this is exactly what people have been doing with their web components. Properties go down, events go up, and you get this like magical unidirectional data flow in your application. So if you go back to my application from before, you have this like giant screen at the top that knows about the state of the world and you've got like your post button where you like mash on your keyboard and emoji comes out. And the app is gonna know things that not every component knows about. For example, it knows what channel you're posting to. So it's going to inform anybody that it cares about by setting a property on those elements. Again, just like you've been doing with input. And when you're done mashing on the keyboard and you have like a new post ready, you fire this custom event and be like, hey, I got an emoji post. Does anybody care? And if anybody cares, they're gonna intercept that event.  You just set different properties. What I didn't tell you here is that you should call like a public method on this element or something like that. Because again, that's not how we've been using DOM elements before. We don't call random functions on input. We just set properties, which leads me to my third device. Use properties and non-message. You might be tempted to use methods because JavaScript is really keen on having methods, but that's not how the DOM really likes to be used. The DOM has properties and attributes. And this is really great if you're using properties because then you can just use them imperatively and you can have data bindings and stuff like that. So imagine you have a dialogue. You could call dialogue.open on it, but you don't need to. If it's got a property, you can just say hey dialogue, dialogue.open equals true. And once you've done this, you can just do it as a binding somewhere in your code. And it depends on like some other state of the world. And without writing any JavaScript, like things will open and things will hide as they should because that's how properties work.  Those are your rules. So that's the advice that I have for app developers. But what do we do about element maintainers? You're like this poor sucker that has inherited like 17 elements that somebody else wrote left the company and you don't actually know why they're in that state. And this happens whether you're maintaining elements externally like we do for like the rest of the world or internally like a lot of companies do, they just have an internal set of elements, but they still have to maintain them. So we've been writing tools. And the biggest advice that I have is you keep hearing about like test driven development. That's great. But I think you should practice fear driven development. And that's not being afraid of the code or anything like that. It's really just being afraid of your users and that's a healthy approach to development. Because most importantly, you should be afraid of like breaking them and breaking their applications. That's like your one responsibility as a maintainer. Don't break other people's code. So in preventing breaking changes, we've been using this tool internally and we're working on like making it, it's a public repo on Polymer Labs and we've been working on fixing it so that you all can use it. And it's called TAD2, which stands for test all the things over and over because why not come up with a complicated acronym if you can. And the idea is really simple.  Look at this dependency graph, which is not a real dependency graph. They're usually way worse than this. But if you modify a leaf at the bottom, unless you have the ability to like hold all the 130 elements in the Polymer Elements catalog in your head, you're probably not gonna know what that change is gonna affect. It could be a behavior, it's gonna be like the ability to be included in like a custom form or something like that. You don't actually know how many elements depend on that change, especially since they can go many levels up the tree. So what TAD2 does is it lets you specify a branch or a particular hash or something like that in a particular element and rerun based on that commit, a whole suite of elements, a whole suite of tests. So in this case, we make a change to one element and like make sure that all the other tests pass. This is great because then you have the confidence as a maintainer that like this PR isn't gonna, you know, destroy all of YouTube because we've definitely not done that before. The other thing that you should be afraid of is perf regressions. It's really great that now you've like have the confidence that you're not gonna break somebody's application, but making their application slower is kind of slightly worse because that's harder to fix. And we have two tools for that. The first one is Poly Dev, which is a Chrome extension and you can run it on any app that uses custom elements and basically ranks how expensive the elements that it sees on the page are. And it's great if you wanna like audit your page and like make sure that like as you're contributing to an app, so this is also good for the app developers as you're like fixing your app, the performance sort of stays as you expect. But it's also really good for maintainers. If you have like a giant catalog that has like different demos for different elements and one of these elements that used to be really cheap after a commit suddenly like spikes to the top, that probably means something bad has happened and you wanna like undo that change. So that's what Poly Dev does for you. It's in the Chrome app store. You can download it, it's awesome. My favorite tool is Poly Perf. And please note how these names have a Poly prefix at the end, but tattoo doesn't cause poly tattoo is weird. So Poly Perf lets you basically compare the performance between changes. So here, this is an example from Steve's talk from the Polymer Summit where as a baseline he has an input element and that's not, it doesn't cost you 20 milliseconds to make one input, it costs you 20 milliseconds to make 250 of them on a page. And then he had like this ratings element and he started with like a super shitty version and it just made it progressively faster. And these are just like three iterations of that ratings element. And the reason why this is good is because you can start doing it for like, again, different commits and different shaws and different features that you're adding to an element and be like, cool. This element used to cost like 129 milliseconds and now it's 500 milliseconds. Is this change really worth it? Which is great for you as a maintainer because then you can go back and be like, no, this changes shit, we're not merging it, it's fine. So that's fear driven development. The sort of parallel and kinder version of development to that is demo driven development. If you think about your users, they don't really, like I personally can't look at a snippet of code and be like, I totally know what that element looks like and how it's gonna fit on my page, that's great. I can only like look at demos and be like, I want it, I want the shiny button. So that's what demo snippet is for. Demo snippet lets you write basically how you would use that element, shows you what the code is and shows you what that element looks like. Here's a whole bunch of paper fab buttons. Fab stands for floating action button, not fabulous. And it took me about a year and a half on the team to find that out and I was super sad. I think fabulous button is a way better name but nobody listens to me. So that's a demo snippet, it's really great. And we've noticed, we've like heard that Comcast for example, uses this element very aggressively internally to just be like, these are all the elements we have, this is what they look like, do you care? And we've taken this demo approach very aggressively to the new beta site for the webcomponents.org. So beta.webcomponents.org is the new element catalog where we're moving all of our elements too and it basically supports collections and elements and they're curated collections. You can make a collection called fabulous elements and you can add all sorts of web components to it. So when people search for fabulous elements, they'll get to it. Oh, sorry. But most critically, it supports inline demos. So this is the documentation page for Faber-Fabulous and here at the bottom, you see a demo and it's a snippet but the best thing about the snippet is that it's not static like the demo snippet used to be. It's actually interactive. So here I can change the contents of one of these buttons or I can even add a style because this kind of element advertises a custom property to change its color. So you can go ahead and do that. So what now? We have web components. They're native in the browser. Polymer 2.0 is right around the corner. What does this mean for you as developers? Because this is called Polymer web components in you. Let's talk about the you part. There's never been a better time to actually start using web components. So go ahead, just go and use an element. Add, I have a really dumb element called emoji rain that makes it rain emoji in your page. Go ahead and drop it on your blog, why not? Use Polymer, don't use Polymer. Use vanilla custom elements that you stumble across. Make your own element and if you do share it, polish it up, submit it to beta.webcomponents.org so that everybody else can look at it and it's gonna be really awesome so that their applications can get better. But most importantly, just make things. Use the platform, use tools that make your life better and make you like write less code and build awesome things for the web because it's up to you to make the web better. We can just like help you along with it, but at the end, you're gonna make it awesome. Thank you.


Okay so today guys I have been doing 10 secret items across the world of Redfall with that first map of Redfall comments. We have items consisted of full body outfits, individual pieces of gear like backpacks and headwear as well as stakes and legendos. Today we're getting to it all. How's it going guys? My name is DPJ and if you enjoyed the video leaving a like really helps out and if you like what you see and want to see more be sure to subscribe. For a little bit of information in regards to cosmetic items you get in this game like costumes and things like this they are tied to missions and side missions that you do. Now from my understanding is it doesn't matter what order you do certain missions in or side missions let's say for instance you do 8 side missions and 2 main quest missions. No matter what order you do them in you will always be rewarded at the end of said mission tied to that in particular number that said reward. What there are guys guaranteed drops and guaranteed rewards you can go around the map and find and pick up for your character. Now these are completely different for each individual hero so what you'll see me pick up here today I'm Jacob won't be the same for you if you come to said location with the Rinder in regards to cosmetic gear items for your character. Ok so we'll actually start with those cosmetic outfits and there are 2 for you to get today. Now as you know there are 5 safe houses across this map of Redfall Commons. Now when you unlock each individual safe house do actually 2 side missions you can do inside these safe houses.  Now 3 of these are needed for the Hollow Man main stone mission to progress you onto the second map. This means you have 2 spare at least 2 spare you can use in 2 different school altars. Now a word of warning you need to keep free otherwise you won't be able to progress onto the second map. I made a mistake which I'll explain to you so you don't make the same mistake Basically what I did was I used my 2 spare schools keeping my 3 on me I used in my friends lobby. I got my 2 outfits there. When I come back to my own lobby I went back to one of these altars and it allowed me to place another school so I did it leaving me with only 2 schools left. Me thinking I'll get another outfit well I did get an outfit and it took my school as far as I'm aware there are no more vampire underbosses so I can't get a third school so when it comes to me doing that hollow man main mission I'm not sure if I'll be able to progress so don't make that mistake guys. Ok so with your schools these are the locations of the school altars. Meaning you can come to these spots on the map guys and grab those cosmetic outfits for your hero. The first location you'll see right here on the map.  Now the second school altar is right here on the map.  Ok so next up people is a guaranteed item it's a steak and this will be the same for all heroes. It's a gnome steak it's absolutely amazing by far the best I've seen in this game. Now to get this guys come to this point on the map right here and let's pick this lone little thing up. Then go into your weapon details and place this on a weapon which already has a steak attached to it. Place on next up guys you have a piece of headwear. Now for Jacob this is called the three strikes but for other heroes it will be different. This is located at the end of this train track so follow the route I take on screen now and go grab this thing. Next up guys we have a backpack again this will be completely different for you if you're not playing on Jacob. So come to this point on the map right here people now there will be a few vampires here for you to take out follow the route I take up into this house take out these vampires grab this out of that bag and you are good to go guys. Next up people we have another head piece. Now for me I'm Jacob this is called the rubber side down on other heroes I'm not sure what this will be so again follow the route I take on screen now guys and come and get this thing. Ok so the four final items in today's video are all guaranteed legendary weapons and these can be random so what you get here is all down to RNG. Now in a total of these four legendary weapon locations you will need a minimum of four lock picks as well as one rewire kit. So make sure you have them and then come and get these four legenders very very simple people just follow the points I take on screen now.  Guys if you enjoyed the video leaving a like really helps out if you like what you see and want to see more be sure to subscribe and hopefully guys I will see you on that next one.


Hi everyone, Joe for Jaspy's casebreaks.com, not with our last filler and for you. I know it said that, but there are still seven spots left in the Bowman's Best Break. I pulled those remaining spots on and then created a real last filler. So unfortunately, 83, not the last filler, but we only have a last filler to go now. So if you want to run this tonight, we definitely got time to. We definitely can. All right. So let's do the pack break first, 2022 Tops Chrome Jumbo, Tops Chrome Baseball Jumbo Edition, and that at the end will re-randomize everybody's names. Top seven will get spots in that best break. Big thanks to this group for making it happen. There are the teams right there. Let's roll it. Let's randomize names and teams four into three, seven times. One, two, three, four, five, six, and seventh and final time. All right. So we've got, let's copy that, put those names in there, and then the teams final time. All right. No trade windows, but here, no trade window here in a filler pack, but there's the first half of the list. There's the second half of the list. Let's just print and rip. We got a parallel in there. That's always nice. It's Andre Jackson. He made the opening day roster through some relief innings yet last night. I think you got a save. I think it was like a three innings, that's what I do. And there's Justin Turner, 59 out of 350. I think he had a nice game for the Red Sox the other night. This one will go to the Dodger. That'll go to Jason K. Miss Justin Turner. I understand why that happened. I get the business to baseball, but miss that guy. All right. He'll be back. I think he'll be back with the Dodgers. I'm sort of managerial capacity if he wants to do that in the future. All right. Let's gather everybody's names. Top through 30. New dice, new list. Top seven will get spots in Bowman's best. Good luck. Top seven after four and a six, 10 times. One, two, three, four, five, six, seven, eight, nine, and 10th and final time. So top seven after 10. So from eight on down, it's going to be sad times. Sad times for James. Oh, but I appreciate everybody, James, and everybody for getting in. Top seven though, happy times. Tristan is happy. So it's Tristan and Victor, Devin, Chris, Charles, and Victor. Happy times for the top seven after 10. I'm Joe for Jaspy's casebreaks.com. I'll see you next time for the next one. Bye-bye.


Studying Romeo and Juliet. Here's how you can analyse that for scene 5. The scene opens with the nurse hurriedly entering into Juliet's bedroom. She speaks in these exclamatory sentences trying to wake her up. The nurse asks this rhetorical question basically showing her confusion as to why Juliet is not getting out of bed. The stage directions then show her dramatically pulling back the curtains around Juliet's bed. To a horror she looks at Juliet lying still in her bed and she screams out using these exclamatory sentences as the nurse believes that Juliet has died. The nurses screams cause commotion and the stage directions show that Lady Capulet has heard her screaming and she enters looking really confused. She's not sure why the nurse is screaming. When Lady Capulet realises that Juliet has died she cries out this hyperbole. In other words she feels like her life is worthless now that her only daughter has died. Here in the commotion Lord Capulet also enters and he speaks using alliteration here when he realises that Juliet has died. He is also really really sad that his only daughter has died. Both the nurse and Lady Capulet cry out in these exclamatory sentences. What was meant to be a wedding is now going to turn into a funeral. Friar Lawrence and Paris both enter and Friar Lawrence seems confused. He pretends not to know what they are screaming about. Friar Lawrence and Paris enter and Friar Lawrence pretends not to know what they are screaming about. Lord Capulet speaks in these dramatic metaphors. He tells Friar Lawrence and Paris that Juliet has died and death is now his son-in-law.  This strikes us as a bit ironic because she never really seemed to have cared about Juliet whilst she was still alive. Paris also cries out and he speaks using listing to show that he's devastated he won't marry Juliet. Lord Capulet speaks using this metaphor to say that now Juliet has died all his hopes and dreams have died with her. Again this strikes us as a bit ironic because whilst she was alive he didn't really seem to care about her or opinions about her marriage. Friar Lawrence tries to comfort them and he speaks using this rhetorical question to basically say that it was God's will for Juliet to join him back in heaven. Lord Capulet then speaks using this oxymoron to say that Juliet's wedding should now be turned into Juliet's funeral in commemoration of her death. The nurse then speaks in this imperative sentence to tell the musicians that instead of playing happy melodies and happy tunes they now have to play funeral music.