diff --git "a/macdial/val.json" "b/macdial/val.json" new file mode 100644--- /dev/null +++ "b/macdial/val.json" @@ -0,0 +1,10197 @@ +[ + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 51, + "turns": [ + 215, + 317 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "case", + "speaker": "Project Manager , Marketing" + }, + "summary": "Project Manager asked about the case shape and case material. Marketing said it was double-curved with rubber material.", + "title": "Shape and Material of the Case", + "relevant_turns": [ + [ + 32, + 59 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "high", + "topic": "case", + "speaker": "Project Manager , Marketing" + }, + "summary": "Project Manager asked what the shape of the case was, uncurved flat, single curved, or double-curved, and what case material supplements they were to use. Marketing said it was double-curved and the material was rubber because they were going to have soft buttons.", + "title": "Shape and Material of the Case", + "relevant_turns": [ + [ + 32, + 59 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "buttons", + "speaker": "Project Manager , Marketing , User Interface" + }, + "summary": "Project Manager asked about the buttons to be used and any special color and form. User Interface said they did have a special form.", + "title": "Design and Color of Buttons", + "relevant_turns": [ + [ + 52, + 102 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "buttons", + "speaker": "Project Manager , Marketing , User Interface" + }, + "summary": "Project Manager asked if they had interface pushbuttons and User Interface and Marketing said yes it was there. For the scroll wheel, they said no, and for the button supplement special color and special form, User Interface said yes, they had a special color and they did have a special form.", + "title": "Design and Color of Buttons", + "relevant_turns": [ + [ + 52, + 102 + ] + ] + } + ], + "source": [ + "Project Manager : Now we're gonna talk about financing . {vocalsound}", + "Marketing : Ah , but in my instructions I think it said I was supposed to go to the board and do something .", + "Project Manager : {vocalsound} Well , there is a production evaluation .", + "Marketing : No ?", + "Project Manager : Is that you ?", + "Marketing : Yeah , that's me .", + "Project Manager : But that's after the financing .", + "Marketing : Oh , okay .", + "Project Manager : See ? Fi see ?", + "Marketing : Sorry , sorry . Mm-mm .", + "Project Manager : {vocalsound}", + "User Interface : {vocalsound}", + "Industrial Designer : {vocalsound}", + "Project Manager : Um . {vocalsound} Okay , we had looks and voice recognition . Okay now on the financing we bring up the mm there it is . Okay uh energy source we say that's battery , right ?", + "Industrial Designer : Mm .", + "Marketing : That's right .", + "Project Manager : Okay , now . So we {disfmarker} I guess we use one .", + "User Interface : Yes .", + "Industrial Designer : Yeah .", + "Project Manager : What ? T cell or chart you are trying to change is protected . Well , that's nice . She told me I could just ch change it here and then it would {disfmarker} It doesn't work . Hmm .", + "Marketing : Can you just fill it in in the yellow boxes ? Or {disfmarker}", + "Project Manager : Oh , okay yeah , okay ,", + "Industrial Designer : Yeah .", + "Project Manager : let's see . Okay , one , okay .", + "User Interface : Yes .", + "Project Manager : Oh go away . Um kinetic source so that's {disfmarker} in the energy source that's all we need .", + "Industrial Designer : Mm-hmm .", + "Project Manager : Uh electronics , simple chip on print ? Is that's what we're using ?", + "User Interface : Yes .", + "Industrial Designer : Yeah ,", + "Project Manager : One of those ?", + "Industrial Designer : yeah .", + "Project Manager : Come on . Okay , one . Uh regular chip on print . No . That's all we need , the one", + "Industrial Designer : No . Yeah .", + "Project Manager : {disfmarker} case , uncurved flat , single curved , double curved .", + "Marketing : Well . {vocalsound}", + "Industrial Designer : This is a {disfmarker}", + "User Interface : Single curve ? Mm .", + "Marketing : I guess it's double curved .", + "Project Manager : Double curved ? One of those ?", + "Marketing : Mm-hmm .", + "Project Manager : Case materi s supplements . Plastic we said , right ?", + "User Interface : Plastic .", + "Industrial Designer : Yeah .", + "Project Manager : Uh wood , rubber ?", + "Industrial Designer : Yeah .", + "Marketing : Rubber , because we're gonna have the soft buttons .", + "Project Manager : Uh but , yes but {disfmarker}", + "Industrial Designer : I think uh that is uh f for rubbers that is uh {disfmarker} yeah case material .", + "Project Manager : That's just for the case material ,", + "User Interface : Is this for the case ? Yes .", + "Project Manager : so special colours though , we having that ,", + "Marketing : Oh okay , the mm-hmm , mm' kay .", + "Project Manager : right ?", + "User Interface : Yes .", + "Industrial Designer : Mm-hmm .", + "Marketing : Mm-hmm .", + "Project Manager : And then we have to interface push buttons .", + "User Interface : Yes .", + "Marketing : Mm-hmm .", + "Project Manager : Scroll wheel , no . Integrated scroll wheel , L_C_ display ?", + "User Interface : No .", + "Marketing : No ,", + "Project Manager : Button .", + "Marketing : 'cause we didn't put the clock in it after all , right ?", + "Project Manager : No .", + "Industrial Designer : Yeah .", + "Marketing : Mm-hmm .", + "Project Manager : Uh , button supplement special colour ?", + "User Interface : Speci Yes", + "Project Manager : Special form ?", + "User Interface : Yes d we do have special form .", + "Marketing : Yes .", + "Project Manager : And special material , rubber , wood , yes .", + "Industrial Designer : Yeah .", + "Project Manager : Okay . {vocalsound} Total seven point six whatever that means .", + "Industrial Designer : Uh , I think that's the price .", + "Project Manager : That's the price .", + "User Interface : One two three four five six seven eight nine", + "Project Manager : Mm ?", + "Industrial Designer : Maybe it {disfmarker} is it just {disfmarker} n", + "Project Manager : Eight , eight point two . That's {disfmarker}", + "User Interface : Nine points ,", + "Project Manager : hmm ?", + "User Interface : okay , yes .", + "Project Manager : Eight point two , right ? So , we {disfmarker} looks like we are well within budget .", + "User Interface : Okay .", + "Industrial Designer : Yeah .", + "Marketing : Mm-hmm .", + "Project Manager : Okay . I guess I should save this I suppose , huh ?", + "Marketing : Yeah .", + "Project Manager : Oops . Uh-huh huh huh .", + "User Interface : On the desktop .", + "Project Manager : I just tried that . My documents , computer .", + "Industrial Designer : AMI .", + "Project Manager : My compu Ah oh here it is , yes .", + "Industrial Designer : AMI should for", + "Project Manager : Okay , fine . Save . Okay good , so that's the good news . We gonna be popular .", + "Industrial Designer : Yeah .", + "Marketing : Mm-hmm .", + "User Interface : {vocalsound}", + "Project Manager : {vocalsound} Um . So that uh {disfmarker} I think financing was pretty simple .", + "Marketing : Mm-hmm ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "test", + "file_id": 15, + "turns": [ + 45, + 87 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "value , government , different sectors", + "speaker": "" + }, + "summary": "Kirsty Williams AM said that the policy reforms should never be undertaken that would lead to less equity in the Welsh education system. The government also empowered the teachers to be more flexible in what they taught children of which gave the government an opportunity to deliver more engaging and relevant lessons to schoolchildren.", + "title": "Government Impact on Education System", + "relevant_turns": [ + [ + 1, + 5 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "value , government , different sectors", + "speaker": "" + }, + "summary": "Kirsty Williams AM said the government would never undertake a policy reform that would lead to less equity in the Welsh education system and that it would not proceed with anything that could lead to an exacerbation of an achievement gap adding that empowering the teachers flexibility in what they taught children has given the government an opportunity to deliver more engaging and relevant lessons to schoolchildren.", + "title": "Government Impact on Education System", + "relevant_turns": [ + [ + 1, + 5 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "WISERD research , distinction , schools", + "speaker": "" + }, + "summary": "Kirsty Williams AM said that the WISERD research suggested that what would make the curriculum successful for all the children especially those in danger of being left behind should be the four enabling purposes of curriculum. There should be strong leadership in schools to ensure no segregation with high expectation of all the children and delivers a curriculum that met the children's needs.", + "title": "Four Enabling Purposes of WISERD", + "relevant_turns": [ + 4 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "high", + "topic": "WISERD research , distinction , schools", + "speaker": "" + }, + "summary": "Kirsty Williams AM said that what would make the curriculum successful for all of our children and shall have a bigger impact on children who were in danger of being left behind, would be the four enabling purposes of the curriculum adding that the curriculum on its own could play a part, but it wouldn't only be as good as the four enabling elements that surround it and there was strong leadership in schools that ensured that there wasn't segregation, that had high expectation of all of our children, and delivered a curriculum within that setting that met the needs of the children there.", + "title": "Four Enabling Purposes of WISERD", + "relevant_turns": [ + 4 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "model , Scotland", + "speaker": "" + }, + "summary": "Kirsty Williams AM said that Scotland curriculum spent much time thinking of content with no time on assessment. Also that strong middle tier and the role that the middle tier was playing in Wales, was absent in Scotland so the ability to work in networks to provide support to a network of schools wasn't available in the Scottish system. Steve Davies added that Scotland encouraged schools to go forth and multiply in terms of the materials and ideas and concepts that were coming through.", + "title": "Scotland Education System", + "relevant_turns": [ + [ + 19, + 40 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "high", + "specificity": "normal", + "topic": "model , Scotland", + "speaker": "" + }, + "summary": "Kirsty Williams AM said that Scotland curriculum spent all their time thinking about content and spent no time at all thinking about assessment. Their focus had been in their work about just talking about content and, actually, the assessment arrangements were bolted on at the end of the process. Professional learning, ensured that the profession was properly prepared for the changes, and they would agree that wasn't necessary since they've got local authorities and regions, but whether they were truly engaged in what they were doing. The strong middle tier and the role that the middle tier was playing in Wales was absent in Scotland also the ability to work in networks to provide support to a network of schools wasn't also available in the Scottish system. Steve Davies added that they were very forthright in sharing their learning and one of the critical elements was the extent to which assessment was considered at the outset alongside the curriculum content. One of the findings was that they encouraged schools to go forth and multiply in terms of the materials and ideas and concepts that were coming through and the pioneer movement was to get a smaller group to develop those materials and look to engage through cluster groups.", + "title": "Scotland Education System", + "relevant_turns": [ + [ + 19, + 40 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "welsh education", + "speaker": "Hefin David AM , Kirsty Williams AM" + }, + "summary": "Hefin David AM asked what value the government have placed on the work done by WISERD. Kirsty Williams AM answered that more research was needed into Welsh education and that the papers happened to be very helpful in informing their work. Kirsty Williams AM added that the most important about the piece of work in influencing the Welsh education was the equality and principles of equity to not undertake policy reforms that would lead to less equity in the Welsh education system. Adding that closing the attainment gap was a core element of the national mission for education in Wales.", + "title": "Government Influence on Welsh Education", + "relevant_turns": [ + [ + 1, + 3 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "fully", + "specificity": "normal", + "topic": "welsh education", + "speaker": "Hefin David AM , Kirsty Williams AM" + }, + "summary": "Hefin David AM; what value you place on the work done by the Wales Institute of Social and Economic Research, Data and Methods; Kirsty Williams AM; need more research into Welsh education; find their papers really helpful and help us to inform our work; never undertake a policy reform that; lead to less equity in the Welsh education system.", + "title": "Government Influence on Welsh Education", + "relevant_turns": [ + [ + 1, + 3 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "curriculum", + "speaker": "Hefin David AM , Kirsty Williams AM" + }, + "summary": "Hefin David AM asked for the response of what Dr Nigel Newton said about the curriculum that it could exacerbate segregation within schools between different groups of pupils. Kirsty Williams AM responded that the curriculum was not going to necessarily enhance equity.", + "title": "Introduction of Curriculum in Schools", + "relevant_turns": [ + [ + 3, + 5 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "curriculum", + "speaker": "Hefin David AM , Kirsty Williams AM" + }, + "summary": "Hefin David AM asked for the response to the specific statement that Dr Nigel Newton said about curriculum could exacerbate segregation within schools between different groups of pupils. Kirsty Williams AM said the curriculum in itself was neither going to necessarily on its own hugely enhance equity nor detract from equity, in the sense that the curriculum was what was taught in the schools saying that should make the curriculum success for all the children was the four enabling purposes of the curriculum adding that since the curriculum on its own could play a part, but it wouldn't only be as good as the four enabling elements that surrounded it.", + "title": "Introduction of Curriculum in Schools", + "relevant_turns": [ + [ + 3, + 5 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "cluster", + "speaker": "Steve Davies , Claire Bennett" + }, + "summary": "Steve Davies said that what they learned was to get a smaller group to develop those materials and look to engage through cluster groups. The pioneers worked with clusters to test the development of concept before they were looking for schools to go away and develop a larger amount of content. Claire Bennett agreed that moving forward that kind of cluster approach was still very important and that schools should be doing clusters together when thinking about what they were going to do in school. Schools should emphasize more on this peer-to-peer sharing and support, so people weren't just going off in isolation.", + "title": "The Cluster Approach", + "relevant_turns": [ + [ + 34, + 35 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "high", + "specificity": "normal", + "topic": "cluster", + "speaker": "Steve Davies , Claire Bennett" + }, + "summary": "Steve Davies said that the pioneer movement was to get a smaller group to develop those materials and look to engage through cluster groups and they had pioneers who worked with clusters to test the development of that concept before we were looking for schools to go away and develop a larger amount of content. Claire Bennet also agreed that kind of cluster approach remained really important.", + "title": "The Cluster Approach", + "relevant_turns": [ + [ + 34, + 35 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "assessment", + "speaker": "Kirsty Williams AM , Steve Davies" + }, + "summary": "Kirsty Williams AM said that the particular focus of the year's conference was on the issue of assessment and accountability wondering how children were going to be assessed on the new curriculum. Thinking about assessment methods and how to develop a culture of strong leaders in schools. Kirsty Williams AM also said that some of the challenges the Scottish curriculum also faced were about assessment whereby they spent much time thinking about content and not thinking about assessment which is a crucial part of the process. Steve Davies added that one of the critical elements on Scottish education was the extent to which assessment was considered at the outset alongside the curriculum content.", + "title": "Importance of Assessment in Curriculum", + "relevant_turns": [ + 4, + [ + 20, + 22 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "normal", + "topic": "assessment", + "speaker": "Kirsty Williams AM , Steve Davies" + }, + "summary": "Kirsty Williams AM; focus of this year's conference was on the issue of assessment; how do you assess how children doing in your new curriculum; think about assessment methods and how; develop a culture of strong leaders in our schools; our curriculum is not a copycat of the Scottish curriculum; They spent all their time thinking about content and spent no time at all thinking about assessment; Steve Davies; the critical elements was the extent to which assessment was considered at the outset alongside the curriculum content.", + "title": "Importance of Assessment in Curriculum", + "relevant_turns": [ + 4, + [ + 20, + 22 + ] + ] + } + ], + "source": [ + "Lynne Neagle AM : Okay, thank you very much. We've got some questions now on potential unintended consequences, and other matters relating to that, from Hefin David.", + "Hefin David AM : Can I ask what value you place on the work done by the Wales Institute of Social and Economic Research, Data and Methods and the presentation so far and the paper to be presented by Dr Nigel Newton?", + "Kirsty Williams AM : I always\u2014and Welsh Government are big supporters of WISERD and the work that they do, and, in fact, we need more research into Welsh education, not less. Therefore, I find their papers really helpful and help us to inform our work. I think what's really important in perhaps this piece of work is to say that I hope that, in the time where I've had an influence to influence over Welsh education, either as a backbencher or now as a Minister, equality and principles of equity have always driven what I've tried to achieve. And I would never undertake a policy reform that I thought would lead to less equity in the Welsh education system. Closing the attainment gap is a core element of the national mission for education in Wales and we would not proceed with anything that we thought could lead to an exacerbation of an achievement gap.", + "Hefin David AM : Okay. And how do you respond, then\u2014? I mean, it's a balanced paper, it looks at pros and cons and there's a mixed picture from it. How do you respond to the specific statement that Dr Nigel Newton said that the curriculum could exacerbate segregation within schools between different groups of pupils?", + "Kirsty Williams AM : Well, I think what the paper acknowledges is that there is no evidence that that will happen. These are 'coulds' and 'maybes' and things that we need, as a Government, to take into consideration as we plan this journey. There can't be any empirical research done at the moment because the curriculum isn't being delivered, but I understand, and we need listen to\u2014. If there are concerns out there in the field that these are unintended consequences that we may fall into\u2014that is the value of that piece of research that helps inform us. I have to say, though, the curriculum in itself is neither going to necessarily on its own hugely enhance equity nor detract from equity, in the sense that the curriculum is what's taught in our schools. There is an opportunity, I believe, that empowering teachers to be able to be more flexible in what they teach their children actually gives us an opportunity to deliver lessons that could be much more engaging and much more relevant to some of our schoolchildren than what they have at the moment. What will make the curriculum a success for all of our children, and I believe will have a bigger impact on children who are in danger of being left behind, are the four enabling purposes of the curriculum. So, the curriculum on its own can play a part, but it will only be as good as the four enabling elements that surround it. And that is strong leadership of our schools that ensures that there is no segregation, that has high expectation of all of our children, and delivers a curriculum within that setting that meets the needs of the children there. Secondly: excellent teaching. In the end, no education system, whatever its curriculum, can exceed the quality of the people who stand in front of our children day in, day out. So, the curriculum can be the most exciting, wonderful\u2014and I think it is exciting and I think it's wonderful\u2014it can be the most exciting, wonderful thing in the world, but if teachers can't teach it effectively, if their pedagogy is not excellent, then the content itself\u2014it won't work. Then we've got issues around assessment and accountability. So, how do you assess how children are doing in your new curriculum? How do you understand how that pupil, who has, you know\u2014who could be vulnerable for a whole host of reasons, usually reasons outside of the school\u2014? That pupil is vulnerable. How can you assess how that pupil is and move their learning along in an appropriate fashion? And then, finally, the well-being of the child. People sometimes say, 'Oh, you're going soft\u2014typical, going soft'. But what we know is that we cannot expect children to learn unless we address issues around their well-being. But we also know that poor achievement is also detrimental to a child's well-being. There's been lots and lots of research done, not in a Welsh context but in other systems, where children are kept behind for a year. That has a massive impact on their well-being. So, good achievement leads to good well-being, but good well-being also leads to good achievement, and you can't separate the two. So, the curriculum on its own will not be enough. It is the four enabling objectives that sit around it, and we have to be cognisant of the WISERD's research, of course we do, to ensure that, as we're doing our professional learning, as we're planning well-being for our children, as we think about assessment methods and how we develop a culture of strong leaders in our schools\u2014and we have some, we have many, but we need to do more to support them\u2014it is that that will make the biggest difference, not just the content of the curriculum on its own. Although I do believe the flexibility that we're allowing people will, I think, lead to a curriculum and more meaningful lessons for some children in schools who are in danger of disengaging because they don't understand why they're being asked to learn what they're learning, they don't see the relevance of what they're learning to what they may want to do or how their lives are, or they don't see themselves reflected. So, for some of our communities, they don't see themselves reflected in the curriculum that we're teaching at the moment. And, again, international research would suggest that, if you want a child to thrive, they have to see themselves and their community reflected in what they're learning in schools.", + "Hefin David AM : What the WISERD research suggests is that the senior management teams\u2014the management teams\u2014would certainly buy into what you've just said, but the classroom teachers would be a little bit more sceptical.", + "Kirsty Williams AM : As I said, classroom teachers are absolutely crucial to this, which is why, first of all, we've taken the difficult step to delay the implementation of the curriculum to give us the time that we need to make sure that it's not just school leaders but it is individual classroom practitioners who have the skills that they need to make the most of the opportunity that the curriculum allows them.", + "Hefin David AM : So, if we look at some of the statements that were in the presentation by WISERD at the seminar two comments jump out: 'We'll end up'\u2014this is from classroom teachers\u2014 'We'll end up with a different accountability framework to the aims and objectives of the new curriculum.' and 'there will be no consistency'. And consistency is the one I'd particularly like to focus on: 'there will be no consistency across all schools in how the new curriculum is delivered which could affect outcomes'.", + "Kirsty Williams AM : Well, first of all, we've just talked, haven't we, about trying to ensure that there is greater consistency and that's why we're changing our approach to the legislation around the Bill. So, in terms of progression steps, there will be a statutory framework to ensure that progression is the same wherever you are in Wales. So, as I said, we're using this report, we're using this feedback, to inform decisions going forward. In terms of\u2014. Read the first bit again. Was it\u2014[Interruption.] Accountability, yes.", + "Hefin David AM : Yes: 'different accountability framework to the aims and objectives of the new curriculum.'", + "Kirsty Williams AM : Okay. So, as always, in education, teachers\u2014understandably, because this is the regime that they have been a part of\u2014immediately don't think about their pedagogy, they think about, 'How are judgments going to be made upon me as an individual?' And what we're trying to do is ensure that we are developing another accountability regime that is indeed in line with the purposes of the curriculum and doesn't work against the purposes of the curriculum. So, I understand why teachers are concerned. They spend a lot of time thinking about accountability and how they're going to be held accountable for their practice, but, again, what we want to do is provide reassurance that we are devising an accountability regime for our system that is in line with the purposes of the curriculum and puts us in line with the mainstream thought and reform process across the world of progressive education systems.", + "Hefin David AM : It was the segregation bit I was particularly interested in and the response with regard to disadvantaged pupils and pupils of lower attainment.", + "Kirsty Williams AM : I don't\u2014. I do not believe that any changes\u2014and I would not pursue any changes that\u2014would lead to a segregation.", + "Hefin David AM : Okay. And with regard to the connection between Welsh Government and local government and the concerns that the Welsh Local Government Association and the Association of Directors of Education Wales raised, what progress\u00a0has been made on bridging the gap between\u2014? Whether it's a perception gap or a practice gap, what progress has been made on that?", + "Kirsty Williams AM : Well, I think the last time we had this conversation in the committee I said that I think the comments that the WLGA and ADEW had made were reflective of an old piece of work and were not current and up to date, and I think progress had been made in that time, and I'm pleased to report the significant progress that's been made\u2014", + "Hefin David AM : Bridges have been built.", + "Kirsty Williams AM : Bridges have been\u2014. Well, from my perspective, the bridges were always there. But we've got renewed, energetic engagement from the WLGA and ADEW in all the arrangements that we have for the development of the curriculum and my understanding is that they have said publicly and in writing that they're very supportive of what's going on.", + "Hefin David AM : I'm sure they're watching and nodding vigorously now on Senedd.tv.", + "Kirsty Williams AM : And I will be with them tomorrow night and Friday morning and I'm sure if they've got any other views they'll let me know.", + "Hefin David AM : And the final question: there is a process, a model for this, which is Scotland. What kind of lessons are being learned from the introduction of their curriculum?", + "Kirsty Williams AM : Okay. So, I think the first thing to realise is that our curriculum is not a copycat of the Scottish curriculum, but it is always useful to reflect on how other systems have undertaken curriculum reform in their nation and to learn from any issues that have arisen. So, I think it's fair to say\u2014and I spent time with some delegates from Scotland just this weekend at the Atlantic Rim Collaboratory conference that Wales hosted this year. Unfortunately, Minister Swinney was not able to attend at the very last minute because of Brexit preparedness work that he was involved in, but certainly their teaching union and their equivalent of the EWC in Scotland joined us as well as representatives from the Scottish Government, although not John himself, and they were very frank about some of the challenges that they had faced in introducing their curriculum. Part of that is about assessment and they had not really thought\u2014. They spent all their time thinking about content and spent no time at all thinking about assessment. Assessment has been a crucial part of the process that we have been involved in. Professional learning, ensuring that the profession was properly prepared for the changes, I think they would agree that that wasn't necessarily\u2014. The middle tier, which they don't have to the\u2014. Well, they've got local authorities and regions, but whether they were truly engaged in what they were doing. So, I think we've learned\u2014. Although our curriculum isn't a copycat, as I said, we have been able to learn from, and we've had people who have been deeply involved in the Scottish experience as part of some of our curriculum and assessment groups and some of the advice that we've had in terms of developing coherence. But, Steve, I don't know if\u2014. You speak to your Scottish colleagues quite a lot.", + "Steve Davies : As I said, they're very forthright in sharing their learning and I think one of the critical elements was the extent to which assessment was considered at the outset alongside the curriculum content. So, that was critical, but we've embraced experts who were involved in that process who were part of our curriculum assessment group. So, they feed in throughout\u2014not 'don't do this because Scotland has done it', but they feed some of that learning into the system. As the Minister said, we had seven other countries from across the world giving us feedback and input over four days as to where we can continue to look at what we're doing but also checks and balances against some of their experiences with this area of reform.", + "Kirsty Williams AM : The particular focus of this year's conference was on the issue of assessment and we were joined by colleagues from Scotland, from Ireland, from Iceland, from Finland, from Saskatchewan, from Nova Scotia and from Uruguay.", + "Hefin David AM : When did that take place?", + "Kirsty Williams AM : Where?", + "Hefin David AM : When.", + "Kirsty Williams AM : The weekend just gone.", + "Hefin David AM : Right.", + "Lynne Neagle AM : Okay, thank you. Suzy. You've got a whole section on assessment, I don't know\u2014", + "Suzy Davies AM : This isn't about assessment.", + "Lynne Neagle AM : Oh, okay. Go on, then.", + "Suzy Davies AM : So, on the basis that this is not about assessment, you mentioned that one of the lessons learned from Scotland is that they said they spent too much time on curriculum content rather than assessment. Can you tell me a little bit about what you've learned about how they quality control the content, even though the content, of course, will be completely different in Wales?", + "Kirsty Williams AM : Yes, the content would be completely different. When I said they spent too much time, I said that the focus had been in their work about just talking about content and, actually, the assessment arrangements were bolted on at the end of the process. So, the curriculum was all designed and developed, it was sent out to schools, and then the question was raised: 'Oh, actually, what assessment methods\u2014? How are going to assess how children are getting on?' But, Steve, you would have more details of their exact experience of quality control of the content\u2014", + "Suzy Davies AM : Of the content, because every school is going to be very different at this.", + "Steve Davies : In terms of developing the guidance and the curriculum going out in January is concerned, I think\u2014again, I don't want to be overly critical, but one of the findings was that they encouraged schools to go forth and multiply in terms of the materials and ideas and concepts that were coming through. What we learnt was to actually\u2014the pioneer movement was to get a smaller group to develop those materials and look to engage through cluster groups. So, we had pioneers who worked with clusters to test the development of that concept before we were looking for schools to go away and develop a larger amount of content. So, in terms of the staging and measuring of bringing together the curriculum and the associated guidance, I think the time we've taken to actually get there and the strategy of using pioneer schools, external experts, back to pioneer schools, back to regions, or engaging regions in that, has been more measured and planned against a planned timescale, where everyone from the outset\u2014with the exception of the extension of the one year\u2014was clear on when we were going to be producing materials that would allow the profession to then take it and use it. I think\u2014. Claire, do you want to add to that, or\u2014?", + "Claire Bennett : I think, as we move forward, that kind of cluster approach remains really important. So, it's, as schools then think about, 'What am I going to do in my school?', that they're doing that in clusters together. When colleagues from the regional consortia were sharing their thinking with the curriculum assessment group last week, they were talking about the very specific and differentiated, I suppose, professional learning support that they would be offering to schools that have already done quite a lot of thinking and are quite far down this journey and then the kind of different sorts of approaches they would offer schools that are just starting out. Their emphasis was very much on this peer-to-peer sharing and support, so people aren't just going off in isolation. The other thing that will also help in that process will be the national network. So, there'll continue to be a focus for each area of learning and experience, bringing together the professional learning and the ongoing curriculum development, bringing together practitioners and experts and colleagues across the middle tier to give a bit of strategic direction and to be able to identify if there are areas where more support is needed. So, I think that a huge amount of thinking, particularly in the regions, has gone on into the practical support that can be given to schools, not just in engaging with the curriculum now, but then how they take it and think about then developing it in their schools. It feels like\u2014I think Graham Donaldson was calling it a 'slow-burn process'. You don't start in 2022\u2014people are already doing it and there's a lot of thought going into how to support continued sharing through the next two years.", + "Kirsty Williams AM : And I think that's another difference, you see\u2014that strong middle tier and the role that the middle tier is playing in Wales, which was absent in Scotland. So, this ability to work in networks to provide support to a network of schools, that wasn't available in the Scottish system and I think that makes\u2014I think that helps us in the way that they just simply didn't have a structure that allowed them to do that. It's not a criticism of them; it's just that we have got a structure that we can utilise to do that support so that schools are not completely left on their own and they can be working with other schools, with their regional consortia, going forward.", + "Suzy Davies AM : Can I just have a quick\u2014?", + "Lynne Neagle AM : Very quickly, because I want to move on to implementation.", + "Suzy Davies AM : Yes, sorry, I completely understand. Was one of the things that Scotland did\u2014I don't want to use the word 'assess'\u2014to monitor the pupil response to the curriculum as one of the means of deciding whether curricula in particular schools were working well enough?", + "Kirsty Williams AM : I don't know if they\u2014. I don't know if they did, but one of the interesting things that we were reflecting on over the weekend is that, certainly some of the Canadian systems, in particular, which we were interested in, used pupil surveys as part of their accountability regime\u2014so, actually taking the time to ask students how they felt, not just about the content of the new curriculum, but actually how they felt their school was doing. And so we're interested in looking, as I said, at some of the practices that other countries use to include pupil voice to find out what's happening.", + "Suzy Davies AM : Okay, that's interesting. Okay, thank you.", + "Kirsty Williams AM : Yes. I mean, it's early thoughts, because we've only just heard about it ourselves. But that's the beauty of working with other countries. They found that particular useful and successful, and we're keen to see if we could do something similar." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 66, + "turns": [ + 250, + 280 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "cost", + "speaker": "Industrial Designer , Marketing , User Interface" + }, + "summary": "Industrial Designer said that if the cost of the LCD screen was received it should be posted in the project's mail. Marketing said that they should get costs of everything and User Interface suggested they had a backup plan.", + "title": "Discussion on Cost of LCD", + "relevant_turns": [ + [ + 0, + 30 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "fully", + "specificity": "normal", + "topic": "cost", + "speaker": "Industrial Designer , Marketing , User Interface" + }, + "summary": "Industrial Designer; I think that they will send you some information about the cost of LCD screens; if you receive an email about that, can you post it in the or shouldn't we post that in our projects mail folder; Marketing; if it costs gets too much, too expensive, then yeah, we should be sticking to rubber buttons; User Interface; perhaps we should have a backup plan that we would use buttons if it's too expensive.", + "title": "Discussion on Cost of LCD", + "relevant_turns": [ + [ + 0, + 30 + ] + ] + } + ], + "source": [ + "Project Manager : Okay , so L_C_D_ it is ?", + "User Interface : An Yes .", + "Project Manager : Okay .", + "Industrial Designer : Mm . It's treasure .", + "Project Manager : And what else ?", + "Industrial Designer : I hope we uh h and let's hope to reach those uh those sales .", + "Marketing : Yeah , i i if it {disfmarker} Yeah , if it costs {disfmarker} gets too much , too expensive , then yeah , we should be sticking to rubber buttons .", + "Project Manager : {vocalsound}", + "User Interface : Yeah .", + "Industrial Designer : Yeah , can you um uh s I think that that they will send you some information about uh the cost of L_C_D_ uh screens .", + "User Interface : Yeah . {vocalsound}", + "Marketing : N nothing , no costs at all .", + "User Interface : But perhaps later ,", + "Industrial Designer : Uh so if you uh {disfmarker}", + "User Interface : so uh {disfmarker}", + "Industrial Designer : Yeah , so if you uh you receive an email about that , uh can you post it in the {disfmarker} or shouldn't we post that in uh our projects mail uh folder .", + "Marketing : Yeah , in {disfmarker}", + "User Interface : Yeah .", + "Marketing : I think that should yeah {disfmarker} I think we all get the costs of everything .", + "User Interface : I don't {disfmarker}", + "Industrial Designer : Because you are the the Marketing uh Expert .", + "Marketing : Yeah , okay , I'll I'll post it .", + "Industrial Designer : I uh {disfmarker} {vocalsound}", + "User Interface : Well perhaps we should have a backup plan that we would use buttons if it's uh {vocalsound} too expensive .", + "Industrial Designer : Yeah sure , sure .", + "Marketing : Yeah .", + "Project Manager : Yeah , okay . But for now it's L_C_D_ . Okay .", + "Marketing : Okay , L_C_D_ , yeah .", + "User Interface : Yeah .", + "Marketing : Then you have the seventy five percent of users find it r ugly .", + "Industrial Designer : {vocalsound}" + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 32, + "turns": [ + 1156, + 1534 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "amount of time , project evaluation", + "speaker": "Project Manager" + }, + "summary": "Project Manager discussed the amount of time they got to make the project evaluation.", + "title": "Amount of Time for the Project Evaluation", + "relevant_turns": [ + [ + 44, + 46 + ], + 126, + 218, + 223, + 228, + 232, + 310, + 323 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "amount of time , project evaluation", + "speaker": "Project Manager" + }, + "summary": "Project Manager discussed with users the amount of time available they had to finish the task. Some of them argued that they could have done better if they had more for the project evaluation.", + "title": "Amount of Time for the Project Evaluation", + "relevant_turns": [ + [ + 44, + 46 + ], + 126, + 218, + 223, + 228, + 232, + 310, + 323 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "information , presentation", + "speaker": "User Interface , Industrial Designer , Marketing" + }, + "summary": "User Interface said the presentation was not ready, and stated having different information than Marketing. Marketing said they had some information that was the same. Industrial Designer mentioned that sometimes the information was late, and didn't have the time for a qualitative presentation. Marketing agreed on the information being late and expressed the importance of getting on time the information.", + "title": "Having Information on Time", + "relevant_turns": [ + 48, + [ + 57, + 63 + ], + [ + 126, + 128 + ], + [ + 214, + 216 + ], + 250, + [ + 272, + 278 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "normal", + "topic": "information , presentation", + "speaker": "User Interface , Industrial Designer , Marketing" + }, + "summary": "User Interface didn't have the presentation ready, and said Marketing had different information. Industrial Designer said the information was too late, and didn't have the time for a qualitative presentation. Marketing stated the need of having information on time.", + "title": "Having All the Information", + "relevant_turns": [ + 48, + [ + 57, + 63 + ], + [ + 126, + 128 + ], + [ + 214, + 216 + ], + 250, + [ + 272, + 278 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "technology , board", + "speaker": "Industrial Designer , User Interface" + }, + "summary": "Industrial Designer said the technology on the board was fantastic. User Interface stated not liking the board, because it didn't work great, but it was handy.", + "title": "Industrial Designer and User Interface's View on the Board", + "relevant_turns": [ + [ + 93, + 96 + ], + [ + 100, + 101 + ], + 109, + [ + 133, + 136 + ], + [ + 142, + 145 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "fully", + "specificity": "high", + "topic": "technology , board", + "speaker": "Industrial Designer , User Interface" + }, + "summary": "User Interface, technology was fantastic, does work, sometimes it doesn't erase, quite handy, did work pretty well. Industrial Designer, the board, work now, easier to get one of those, digital pens, don't think, the SMARTboard, really useful, used it; the means, discussed the smart board.", + "title": "Industrial Designer and User Interface's View on the Board", + "relevant_turns": [ + [ + 93, + 96 + ], + [ + 100, + 101 + ], + 109, + [ + 133, + 136 + ], + [ + 142, + 145 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "work together", + "speaker": "Marketing" + }, + "summary": "The team discussed to work together as a group. Marketing thought working together, even as much as five minutes sessions, would be better for the project.", + "title": "Teamwork", + "relevant_turns": [ + 52, + 55, + 63, + 70, + 73, + 75, + 78, + [ + 83, + 84 + ], + 88, + [ + 96, + 97 + ], + 100, + 116, + 142, + 148, + 169, + 171, + 176, + 265, + 303, + 307, + 310, + 316, + 323 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "normal", + "topic": "work together", + "speaker": "Marketing" + }, + "summary": "Marketing, would be better if, worked a little bit together, through each other; presentation, don't think, the best way to work, for such project; communicate during, session of five minutes together, then work separate, work together too by mail, by, chat; about the teamwork, worked through, past each other.", + "title": "Teamwork", + "relevant_turns": [ + 52, + 55, + 63, + 70, + 73, + 75, + 78, + [ + 83, + 84 + ], + 88, + [ + 96, + 97 + ], + 100, + 116, + 142, + 148, + 169, + 171, + 176, + 265, + 303, + 307, + 310 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "lcd screen , laptop", + "speaker": "Industrial Designer , User Interface" + }, + "summary": "Industrial Designer brought up the possibility of an LCD screen. User Interface said it was possible to make an LCD screen but not mic, or vice versa; then suggested less heavy laptops as other points of improvement of the whole process. Industrial Designer complemented, mentioning the possibility of faster laptops.", + "title": "LCD Screen and Laptops Improvement", + "relevant_turns": [ + [ + 279, + 303 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "normal", + "topic": "lcd screen , laptop", + "speaker": "Industrial Designer , User Interface" + }, + "summary": "Industrial Designer, didn't think, able to make an LCD screen, only costs four units; pop up screen. User Interface, could make an LCD screen but no mic; less heavy laptops.", + "title": "LCD Screen and Laptops Improvement", + "relevant_turns": [ + [ + 279, + 303 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "digital pen", + "speaker": "Industrial Designer , Project Manager" + }, + "summary": "Industrial Designer proposed the use of a digital pen, Project Manager asked about it, and found out that there were some problems with the way it worked, because it was not as precise as expected, so it might write different that it was supposed to. Industrial Designer said it was useful to make designs but not so good to write, mainly because of its size and shape.", + "title": "The Digital Pen", + "relevant_turns": [ + [ + 101, + 104 + ], + [ + 118, + 121 + ], + 125, + 133, + [ + 148, + 160 + ], + 163 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "high", + "topic": "digital pen", + "speaker": "Industrial Designer , Project Manager" + }, + "summary": "Project Manager talked about the usage and functionally of the digital pen. It was found a little difficult to use and not precise. Industrial Designer said it was good to make designs, but not to write, it was too big and too fat.", + "title": "The Digital Pen", + "relevant_turns": [ + [ + 101, + 104 + ], + [ + 118, + 121 + ], + 125, + 133, + [ + 148, + 160 + ], + 163 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "email", + "speaker": "Marketing , User Interface" + }, + "summary": "Marketing brought the topic of email reception. Sometimes it was fast, but most times it was slow. Because of the reason that User Interface hadn't looked, proceed to ask where that email was, and wondered if the team had gotten another one, because maybe they had to fill another questionnaire as they had done before.", + "title": "Email Reception", + "relevant_turns": [ + [ + 218, + 222 + ], + [ + 232, + 244 + ], + [ + 348, + 358 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "email", + "speaker": "Marketing" + }, + "summary": "Marketing discussed the amount of time for emails to arrive. User Interface asked about the received emails.", + "title": "Email Reception", + "relevant_turns": [ + [ + 218, + 222 + ], + [ + 232, + 244 + ], + [ + 348, + 358 + ] + ] + } + ], + "source": [ + "Marketing : And erase the mic .", + "User Interface : Yeah , goodbye mic .", + "Industrial Designer : All I need is no mic . {vocalsound}", + "User Interface : {vocalsound}", + "Marketing : {vocalsound}", + "Industrial Designer : {vocalsound}", + "Project Manager : Let's see , we can save this now .", + "User Interface : Oh , I already erased half of the line .", + "Industrial Designer : {vocalsound} Bon chance {vocalsound}", + "Project Manager : And move back to here .", + "User Interface : Too bad , oh .", + "Project Manager : {vocalsound}", + "Industrial Designer : {vocalsound}", + "Marketing : {vocalsound}", + "User Interface : Like this ?", + "Project Manager : Mm-hmm .", + "User Interface : Still looks nice .", + "Project Manager : And then all green . Okay , well thank you .", + "User Interface : Oh , that's erase .", + "Marketing : Looks like a iPod .", + "Project Manager : Oh , no {gap} .", + "Industrial Designer : No ,", + "Project Manager : Hey , but you can erase that .", + "Industrial Designer : add {gap} {disfmarker}", + "User Interface : Yeah , that's a bit weird .", + "Industrial Designer : Yeah .", + "Project Manager : Uh-oh .", + "User Interface : Oh , now I'm {gap} line .", + "Industrial Designer : S Difference between lines and text and the pen .", + "User Interface : Yeah .", + "Project Manager : Right . {vocalsound}", + "Marketing : Oh . All I need is {gap} mic . {vocalsound}", + "Project Manager : And you can't erase this ?", + "Marketing : {vocalsound}", + "Project Manager : Hmm , strange .", + "User Interface : No ,", + "Project Manager : Okay , well uh", + "User Interface : it's weird . {vocalsound}", + "Industrial Designer : {vocalsound}", + "Marketing : {vocalsound}", + "Project Manager : just leave it at this and quickly save .", + "Marketing : Station page .", + "Project Manager : Um and then we are going to the project or product evaluation .", + "Industrial Designer : Huh , looks fucking boring now . {vocalsound}", + "Project Manager : We just did {gap} our project evaluation . Um well , I think I can sit for that since it's almost my final slide . Um what did you think about uh the process ? How satisfied are we ?", + "Industrial Designer : Deadlines were sometimes very short .", + "User Interface : Yeah .", + "Project Manager : Mm-hmm .", + "User Interface : Bu but stressful . You think , no , my presentation isn't ready .", + "Industrial Designer : But {disfmarker}", + "Project Manager : Yeah .", + "Industrial Designer : And stressful .", + "Marketing : I think we {disfmarker} it should be b it would be better if we worked a little bit together .", + "User Interface : Yeah .", + "Project Manager : Yeah .", + "Marketing : Now we worked through each other ,", + "Project Manager : And you could ask things .", + "User Interface : Yeah , you had information I didn't have", + "Marketing : something he said {disfmarker}", + "User Interface : and then uh {disfmarker}", + "Marketing : yeah , and you had information I also had ,", + "User Interface : Oh right . {vocalsound}", + "Industrial Designer : Yeah .", + "Marketing : so some some things I had in my presentation , they already told ,", + "Industrial Designer : Yeah .", + "Project Manager : And for me it sometimes was a surprise who was going to present what , huh ?", + "User Interface : Yeah .", + "Marketing : so {disfmarker}", + "Project Manager : And uh {disfmarker}", + "User Interface : {vocalsound} Yeah .", + "Marketing : So yeah , that {disfmarker} I don't think that is the best way to work at {disfmarker} for such project .", + "Project Manager : Yeah .", + "User Interface : No .", + "Project Manager : So you would say uh communicate during our individual uh work .", + "Industrial Designer : {vocalsound}", + "Marketing : {vocalsound} Yeah , no , or maybe session of five minutes together or something , and then work separate .", + "Industrial Designer : Yeah ,", + "Project Manager : Yeah .", + "Industrial Designer : but but why not work here together , for example ?", + "User Interface : Yeah , you could {disfmarker}", + "Industrial Designer : Why should we be separated from each other in those difference {disfmarker} uh different rooms ?", + "User Interface : Yeah .", + "Marketing : Yeah . Yeah .", + "Project Manager : Mm-hmm . Well , probably to simulate the whole working uh process ,", + "User Interface : I think so too . Yeah , but then you can work together too", + "Industrial Designer : Yeah .", + "Project Manager : huh , th {gap} you can't have a meeting uh for several weeks .", + "User Interface : when {disfmarker}", + "Marketing : Yeah m yeah , like she told . Then you can work together too by mail or by , I dunno , chat , something ,", + "Project Manager : No .", + "User Interface : A chat would also be uh {disfmarker}", + "Industrial Designer : Huh , oh right .", + "Marketing : but now we're completely separated from each other . I don't think that was the best way , but {disfmarker}", + "Industrial Designer : But the technology was uh fantastic . {gap}", + "User Interface : Well ,", + "Marketing : Yeah , the technology's okay .", + "User Interface : I I don't really like the board , it doesn't really work great . Sometimes I think {vocalsound} .", + "Industrial Designer : Work now ?", + "Marketing : Yeah okay , but I don I do I think becau that's because {disfmarker}", + "Industrial Designer : Perhaps it is e", + "User Interface : It does work , but sometimes it doesn't erase or it doesn't uh {disfmarker}", + "Industrial Designer : Yeah , perhaps it is easier to get one of those uh dig digital pens or so and to uh {disfmarker} and lay it next to that keyboard over there .", + "Marketing : Yeah .", + "User Interface : Yeah .", + "Industrial Designer : So you can draw uh {disfmarker} see it over th on the screen .", + "Marketing : Yeah , like the f like a plotters or something ,", + "User Interface : Yeah .", + "Industrial Designer : Yeah .", + "Marketing : yeah . Yep yep yep yep yep .", + "Project Manager : So you don't think the SMARTboard is is really useful", + "User Interface : But {disfmarker}", + "Project Manager : or {disfmarker}", + "User Interface : Well", + "Industrial Designer : {vocalsound} It's useful , but not m", + "User Interface : it is useful ,", + "Marketing : Yeah , it is useful , but {disfmarker}", + "User Interface : but it doesn't really work all the time .", + "Marketing : No .", + "User Interface : Th the pen doesn't {disfmarker}", + "Industrial Designer : Because when you put this pen on the screen uh uh for exam and line is d being drawn at at two or three centimetres uh below .", + "User Interface : The line is a bit off .", + "Project Manager : Yeah , so it's maybe a bit unnatural also .", + "User Interface : Yeah ,", + "Industrial Designer : Alright .", + "Marketing : Yep .", + "User Interface : you can point to where you want the line to be . But {disfmarker}", + "Industrial Designer : The project uh {disfmarker} because of the deadlines you didn't had the time to uh {disfmarker} have , you didn't have time to uh {disfmarker} to make a very uh qualitati qualitative uh presentation .", + "User Interface : Yeah .", + "Industrial Designer : So you used uh this uh the different PowerPoint presentations uh in which you put your uh material in the {disfmarker} Oh .", + "User Interface : {vocalsound}", + "Project Manager : That wasn't me . Uh {vocalsound} so um", + "User Interface : {vocalsound} Yeah .", + "Industrial Designer : {vocalsound} Wasn't me .", + "Project Manager : the means , we discussed the smart board , and what about uh this digital pen ?", + "User Interface : I {disfmarker} {vocalsound} I I used it ,", + "Marketing : I didn't use it at all . {vocalsound}", + "User Interface : it it was {disfmarker} you can use it , it's quite handy I think .", + "Project Manager : Yeah , well", + "Industrial Designer : But I didn't {disfmarker} I uh {disfmarker}", + "Project Manager : I use it as a a normal pen and and and only you use it to uh get it on the computer ,", + "User Interface : Yeah , I used it to y to {disfmarker}", + "Project Manager : huh ?", + "User Interface : Yeah , it did work pretty well .", + "Industrial Designer : I used it too , but {disfmarker} oh well .", + "User Interface : I don't think why you would want to use it actually ,", + "Industrial Designer : Yeah .", + "Marketing : I didn't use .", + "Industrial Designer : Yeah ,", + "User Interface : but it it does work . {vocalsound}", + "Industrial Designer : because it shou", + "Marketing : No {disfmarker} yeah .", + "Project Manager : Yeah .", + "Industrial Designer : To make some designs ,", + "Marketing : It is it is {disfmarker}", + "Industrial Designer : it is very easy .", + "Marketing : yeah , it is easy for {disfmarker} to design something and then load it in your computer .", + "Industrial Designer : Yeah .", + "User Interface : Yeah , and then you can show it to everybody .", + "Industrial Designer : But to write it th yeah .", + "Marketing : Yeah .", + "User Interface : It doesn't really write normally .", + "Marketing : Yeah . It's b bi little bit too big to write .", + "User Interface : It's a bit {disfmarker} {vocalsound}", + "Industrial Designer : Yeah , it's too big , it's too fat .", + "User Interface : {vocalsound} Yeah .", + "Marketing : {vocalsound} Yeah .", + "Project Manager : Yeah .", + "Marketing : Fat document , those .", + "Industrial Designer : {vocalsound}", + "Project Manager : Okay , um and what about the teamwork ?", + "User Interface : I think it was great ,", + "Marketing : Team work was okay .", + "Project Manager : Yeah , well I think so too .", + "User Interface : yeah .", + "Industrial Designer : Yeah .", + "Project Manager : {gap} we {disfmarker}", + "Marketing : Only thing that we worked through , past each other .", + "Project Manager : Yeah ,", + "Industrial Designer : Right .", + "Project Manager : but that was {disfmarker} it was our assignment ,", + "Marketing : With some things that was only problem ,", + "User Interface : Yeah , but it was because we didn't uh {disfmarker}", + "Marketing : but {disfmarker}", + "Project Manager : huh ?", + "User Interface : Yeah .", + "Marketing : Yeah yeah yeah ,", + "Project Manager : Okay ,", + "Marketing : but furthermore better .", + "Project Manager : and maybe I should walk out of the room when you discuss uh this point , the leadership . {vocalsound}", + "User Interface : {vocalsound}", + "Marketing : That's {disfmarker} {vocalsound}", + "User Interface : {vocalsound} I thought it was good , but uh {disfmarker} Yeah .", + "Industrial Designer : Yeah .", + "Marketing : yeah , no prob . Ah .", + "Project Manager : Yeah well , okay .", + "User Interface : {vocalsound} Yeah .", + "Industrial Designer : Not too much , not too too too too {gap} .", + "Marketing : Yeah .", + "User Interface : Yeah .", + "Marketing : Okay .", + "Project Manager : And creativity ? Well , when we look at this I'd say we have been creative ,", + "User Interface : {vocalsound}", + "Industrial Designer : {vocalsound}", + "Project Manager : huh ? But {disfmarker}", + "User Interface : Well .", + "Industrial Designer : Yeah , or the room for {disfmarker}", + "Project Manager : There was room for {disfmarker}", + "Industrial Designer : it was the idea to be creative , so {disfmarker}", + "User Interface : Yeah .", + "Industrial Designer : You got some standard ideas in your head {vocalsound} and this what came out .", + "Marketing : Mm-hmm .", + "User Interface : And you get get stuff from the from the computer ,", + "Industrial Designer : Yeah .", + "User Interface : but {disfmarker}", + "Industrial Designer : The information uh was sometimes uh a little bit too late", + "Marketing : Little bit uh lo yeah . Too late {disfmarker}", + "User Interface : Yeah .", + "Industrial Designer : or {disfmarker}", + "Marketing : it it it took a lot of time before you got your ema", + "User Interface : You just sit there for ten minutes . Yeah , {gap}", + "Industrial Designer : Yeah .", + "Marketing : yeah .", + "User Interface : where is that email ?", + "Marketing : I played I think seven times Solitaire something .", + "User Interface : {vocalsound}", + "Project Manager : You did ? Well ,", + "User Interface : {vocalsound} Oh", + "Industrial Designer : {vocalsound}", + "Project Manager : I didn't have time for that .", + "User Interface : did you ? Is it on there ? {vocalsound} Is it on there ?", + "Marketing : Wha", + "User Interface : I didn't find the {disfmarker} didn't look but uh {disfmarker} {vocalsound} {vocalsound} {gap}", + "Project Manager : At some times I {disfmarker} Sometimes I received like like five emails at at one moment ,", + "Industrial Designer : {vocalsound} Was searching and searching .", + "Marketing : Oh right ,", + "User Interface : I didn't look ,", + "Marketing : it is there .", + "User Interface : but {disfmarker}", + "Project Manager : and then {disfmarker}", + "Marketing : No , I I never got that .", + "Industrial Designer : {gap}", + "Project Manager : {vocalsound}", + "Marketing : I always {disfmarker}", + "User Interface : I got like one email after ten minutes or something .", + "Project Manager : I even got spam . {vocalsound} Or something like that . {vocalsound}", + "Marketing : N yeah .", + "User Interface : {vocalsound}", + "Industrial Designer : {vocalsound}", + "Marketing : {vocalsound} {vocalsound}", + "User Interface : That's what we said . {vocalsound}", + "Marketing : So does this {disfmarker} I think lik oh and information was a bit low I think , sometimes ,", + "User Interface : And it {disfmarker} not a lot uh {disfmarker}", + "Marketing : in in in in the beginning I didn't understand what what to do .", + "User Interface : No , the first one .", + "Industrial Designer : No , w I didn't know {disfmarker}", + "User Interface : I didn't know uh {disfmarker}", + "Marketing : Yeah , like I {disfmarker} with with the remote {gap} and I never new we have t we had to uh {disfmarker} yeah made a made a rec a remote control .", + "Industrial Designer : Make a r", + "User Interface : nee .", + "Industrial Designer : yeah .", + "User Interface : And I didn't know what to do for the first ten minutes before we got here ,", + "Marketing : Yeah , so {disfmarker}", + "User Interface : so I went , right . {vocalsound}", + "Industrial Designer : Yeah . No stepping on the table and then looking at the internet page .", + "User Interface : Yeah . {vocalsound}", + "Project Manager : And I was working and working and work {vocalsound}", + "User Interface : Just looking at the screen and uh {disfmarker} {vocalsound}", + "Industrial Designer : {vocalsound} {vocalsound} No .", + "Project Manager : Okay , well um", + "Marketing : So , yeah .", + "Project Manager : {disfmarker} but after all we can say uh we are satisfied , but it it could've been uh better .", + "Marketing : Yeah .", + "Project Manager : When we get uh {disfmarker} when we have {disfmarker} we would have gotten uh more information .", + "User Interface : Yeah , an", + "Industrial Designer : Yeah ,", + "Marketing : Mm-hmm . Faster .", + "Industrial Designer : more information about the costs .", + "User Interface : Yeah , that will be handy .", + "Marketing : Yeah .", + "Industrial Designer : First of all I didn't think uh that we were able to make an L_C_D_ screen uh {disfmarker} first point ,", + "User Interface : {vocalsound} Yeah .", + "Industrial Designer : but uh it was possible uh {disfmarker} uh , yeah .", + "Marketing : Yeah , it only costs four units . Uh {vocalsound} yeah .", + "Project Manager : Yeah .", + "User Interface : Yea uh so tha actually you could make an L_C_D_ screen but no mic , or it could make mic but no L_C_D_ screen , when you look at that .", + "Project Manager : Yeah , that was a bit mean to put it in the end .", + "Industrial Designer : Yeah .", + "User Interface : Yeah . {vocalsound}", + "Project Manager : And uh what were the other points to to improve this whole process ?", + "Marketing : {vocalsound}", + "User Interface : Uh , I dunno .", + "Marketing : Um {disfmarker} Yeah .", + "User Interface : Think that's about it .", + "Marketing : Nothing .", + "User Interface : Hmm .", + "Marketing : I think we got it already .", + "User Interface : Heavier um {disfmarker} less heavy laptops .", + "Project Manager : Yeah , they're pretty heavy .", + "Industrial Designer : Uh . Faster laptop .", + "Marketing : Yeah . {vocalsound}", + "User Interface : {vocalsound} Yeah .", + "Industrial Designer : Uh . They were they were just fine .", + "User Interface : But that's not really uh {disfmarker}", + "Marketing : And furthermore the the the network was okay .", + "User Interface : Yeah .", + "Industrial Designer : Uh .", + "Marketing : Everything you loaded was also", + "User Interface : Yeah , everything worked .", + "Marketing : av available there .", + "Industrial Designer : Right .", + "Project Manager : And so more time uh w might have improved the the quality of work ,", + "Marketing : So {disfmarker}", + "Project Manager : is what you say .", + "Industrial Designer : Yeah .", + "Project Manager : Okay .", + "Marketing : Yeah . Yeah , but that {disfmarker} It's now half past four {disfmarker} half past three , so {disfmarker}", + "User Interface : Yeah , but it's just the the off hours between that you will work alone .", + "Marketing : Yeah , okay . Yeah , okay .", + "User Interface : Then it pops up {disfmarker} pop up screen came . Five minutes in the meeting .", + "Marketing : Mm-hm . Mm .", + "User Interface : No . {vocalsound}", + "Industrial Designer : Mm .", + "Marketing : Yeah .", + "Project Manager : Okay , so more time during the individual work phases . Um okay well uh", + "User Interface : Huh .", + "Project Manager : I just got my warning for the last five minutes , so I'll move on to I guess my last slide ,", + "User Interface : You did ? Well {disfmarker}", + "Marketing : {vocalsound} {vocalsound}", + "Project Manager : yes , which is the closing . Well uh , we managed , but we did it very quickly . I don't know if that's the best way to {disfmarker} when it isn't {disfmarker} is it {disfmarker} when it is too expensive to quickly re-arrange it and say , okay , this is it ,", + "User Interface : Oh , right .", + "Project Manager : but we had to do it ,", + "User Interface : Well {disfmarker}", + "Project Manager : huh , because we have to have a design , and that is within the budget . And we evaluated . Maybe we should re-evaluate uh the product , but we did that before , and we also evaluated the project . And I think uh everybody's uh very happy . At least I am , with the results ,", + "User Interface : {vocalsound}", + "Project Manager : so uh celebration , well , for the three of you ,", + "User Interface : {vocalsound} Yeah .", + "Marketing : Yeah .", + "Project Manager : because uh I have to write the final report now .", + "User Interface : Champagne . {vocalsound} {vocalsound} Yeah .", + "Marketing : {vocalsound}", + "Project Manager : But uh {vocalsound} well , thank you very much for your co-operation ,", + "Marketing : {vocalsound}", + "Project Manager : and I had a very nice day so far . {vocalsound}", + "Industrial Designer : Yeah , sure .", + "Marketing : No prob .", + "Industrial Designer : Oh thank you .", + "Marketing : Mm-hmm .", + "Project Manager : Okay .", + "User Interface : Do we get another email ? {vocalsound}", + "Industrial Designer : Bling . {vocalsound} You're fired .", + "Project Manager : {vocalsound} Um {disfmarker}", + "Marketing : I think you do .", + "User Interface : I I think we have to fill in a questionnaire again ,", + "Project Manager : Yeah I have t", + "User Interface : but {disfmarker}", + "Project Manager : I think we also have to go to our own rooms again , but um {disfmarker} well", + "User Interface : We do ?", + "Industrial Designer : Mm .", + "Project Manager : I at least . But maybe you can try uh to make a screen shot of this , so I can try to include it in the final report .", + "User Interface : Yeah . Uh th that that one ?", + "Industrial Designer : You cannot {disfmarker}", + "Project Manager : Yeah , maybe .", + "User Interface : You can just {disfmarker}", + "Industrial Designer : you can save it .", + "Project Manager : {gap} wants to , but at least this one .", + "User Interface : Yeah , but it's {disfmarker} it isn't a picture or , well , is it ?", + "Project Manager : I know , we should remove this ,", + "Industrial Designer : You s uh file save as the J_ PEG J_ PEG .", + "Project Manager : but it won't h Okay . And uh please put it in the project folder then , huh .", + "Marketing : Can you find it as a J_ PEG ?", + "User Interface : No ,", + "Industrial Designer : No . {vocalsound}", + "User Interface : isn't possible . But you can make a screen shot , I think .", + "Project Manager : Okay , well I uh {disfmarker}", + "User Interface : {gap}", + "Marketing : No .", + "User Interface : {gap}", + "Industrial Designer : No .", + "Project Manager : I hereby officially close the meeting and uh I hope to see you uh soon . {vocalsound}" + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 4, + "turns": [ + 861, + 984 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "prosody", + "speaker": "PhD E" + }, + "summary": "PhD E mentioned that they were previously working with segments that were all synchronous and that caused a lot of problems. PhD E also mentioned that they had sent an abstract that got accepted for a conference, ISCA workshop. The good news was that there would be European experts in prosody, who are a different crowd, and that would be interesting.", + "title": "Discussion on Prosody", + "relevant_turns": [ + [ + 91, + 102 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "prosody", + "speaker": "PhD E" + }, + "summary": "PhD E mentioned that a submitted abstract got accepted for an ISCA workshop in New Jersey, and they would have European experts in prosody.", + "title": "Meeting Other Experts in Prosody", + "relevant_turns": [ + [ + 91, + 102 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "speech transcription", + "speaker": "Grad F" + }, + "summary": "Professor B asked the others to update their status reports to allow the formulation of the annual report, and feel free to reach out if anything important was left out. Grad F told Professor B that Don would be helping out with the demos. Grad F mentioned they had to work on the status of speech transcription especially, automatic transcription but were kind of running late and needed to go.", + "title": "Discussion On Speech Transcription Status", + "relevant_turns": [ + [ + 7, + 22 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "fully", + "specificity": "high", + "topic": "speech transcription", + "speaker": "Grad F" + }, + "summary": "Grad F agreed on updating their status reports, then said that Don would help out with the demos. Grad F mentioned they had to work on the status of speech transcription and automatic transcription.", + "title": "Speech Transcription Progress", + "relevant_turns": [ + [ + 7, + 22 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "status reports", + "speaker": "Professor B" + }, + "summary": "Professor B told the others that they should get together and talk about the status of things, that there was a meeting coming up and there would also be an annual report. So Professor B would be putting together an annual report using the others' papers and status reports. Professor B said that clarification would be sought from relevant parties if needed. Professor B mentioned that from the meetings, it was quite clear what everyone had been working on. If important information was never included in the status reports, the relevant people should reach out in good time. Professor B asked Grad F the demo work was still being worked on.", + "title": "Status Reports For Annual Report", + "relevant_turns": [ + [ + 0, + 9 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "status reports", + "speaker": "Professor B" + }, + "summary": "Professor B would put together an annual report for the fiscal year, using the others' papers and status reports, clarification would be sought from relevant parties if needed. Professor B asked if the demo work was still being worked on.", + "title": "Information Required for Fiscal Annual Report", + "relevant_turns": [ + [ + 0, + 9 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "workshop", + "speaker": "PhD E" + }, + "summary": "PhD E said that the next step was trying automatic alignments, and that was a sort of stage-two of the same kinds of alignments with tighter boundaries. PhD E then announced that an abstract that was sent out got accepted for ISCA workshop. PhD E also mentioned that they were hoping to have a paper for the same as well, which would be in August. PhD E said the good news was that there would be some sort of European experts in the prosody of a different crowd, and so that would be interesting. PhD E stated that the workshop was called ISCA Workshop on Prosody in Speech Recognition and Understanding.", + "title": "ISCA Workshop on Prosody in Speech Recognition and Understanding", + "relevant_turns": [ + [ + 86, + 104 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "workshop", + "speaker": "PhD E" + }, + "summary": "PhD E said that the next step was trying automatic alignments, and announced that an abstract got accepted for ISCA workshop. PhD E also mentioned they were hoping to have a paper for the same as well, which would be in August. PhD E said that there would be European experts in the prosody of a different crowd, and stated that the workshop was called ISCA Workshop on Prosody in Speech Recognition and Understanding.", + "title": "Workshop to Discuss Prosody in Speech Recognition", + "relevant_turns": [ + [ + 86, + 104 + ] + ] + } + ], + "source": [ + "Professor B : We 're supposed to {vocalsound} get together and talk about , uh , where we are on things . Uh , there 's this meeting coming up , uh , and there 's also an annual report . Now , I never actually {disfmarker} I {disfmarker} I was asking about this . I don't really quite understand this . She was re she was referring to it as {disfmarker} I think this actually {pause} didn't just come from her , but this is {pause} what , uh , DARPA had asked for . Um , she 's referring to it as the an annual report for the fiscal year . But of course the fiscal year starts in October , so I don't quite understand w w why we do an annual report that we 're writing in July .", + "PhD C : She 's either really late or really early .", + "Grad F : Huh . Or she 's getting a good early start .", + "Professor B : Uh , I think basically it it 's none of those . It 's that the meeting is in July so they {disfmarker} so DARPA just said do an annual report . So . So . So anyway , I 'll be putting together stuff . I 'll do it , uh , you know , as much as I can without bothering people , just by looking at {disfmarker} at papers and status reports . I mean , the status reports you do are very helpful .", + "PhD H : Hmm .", + "Professor B : Uh , so I can grab stuff there . And if , uh {disfmarker} if I have some questions I 'll {disfmarker}", + "Grad F : When we remember to fill them out .", + "Professor B : Yeah . If {pause} people could do it as soon as {disfmarker} as you can , if you haven't done one si recently . Uh . {vocalsound} Uh , but , you know , I 'm {disfmarker} I 'm sure before {pause} it 's all done , I 'll end up bugging people for {disfmarker} for more clarification about stuff . Um . {vocalsound} But , um , I don't know , I guess {disfmarker} I guess I know pretty much what people have been doing . We have these meetings and {disfmarker} and there 's the status reports . Uh . But , um . Um . Yeah . So that wasn't a long one . Just to tell you that . And if something {vocalsound} hasn't , uh {disfmarker} I 'll be talking to her late tomorrow afternoon , and if something hasn't been in a status report and you think it 's important thing to mention on {vocalsound} this kind of thing , uh , uh , just pop me a one - liner and {disfmarker} and {disfmarker} and I 'll {disfmarker} I 'll have it in front of me for the phone conversation .", + "PhD H : OK .", + "Professor B : Uh . I guess , uh , you you 're still pecking away at the {pause} demos and all that , probably .", + "Grad F : Yep . And Don is {pause} gonna be helping out with that .", + "Professor B : Oh , that 's right .", + "Grad F : So .", + "Professor B : OK .", + "Grad F : Did you wanna talk about that this afternoon ?", + "Grad D : Um .", + "Grad F : Not here , but later today ?", + "Grad D : We should probably talk off - line about when we 're gonna talk off - line .", + "Grad F : OK . OK .", + "Professor B : OK . Yeah , I might want to get updated about it in about a week cuz , um , I 'm actually gonna have a {disfmarker} {vocalsound} a few days off the following week , a after the {disfmarker} after the picnic . So .", + "Grad F : Oh , OK .", + "Professor B : That 's all I had .", + "Grad F : So we were gonna do sort of status of speech transcription {disfmarker} automatic transcription , but we 're kind of running late . So .", + "PhD E : How long does it take you to save the data ?", + "Grad F : Fifteen minutes .", + "PhD E : Yeah .", + "Grad F : So . If you wanna do a quick", + "PhD E : Yeah .", + "Grad F : ten minute {disfmarker}", + "PhD E : Guess we should stop , like , twenty of at the latest .", + "Professor B : Uh {disfmarker}", + "PhD E : We {disfmarker} we have another meeting coming in that they wanna record .", + "Professor B : And there 's the digits to do .", + "PhD E : So .", + "Professor B : So maybe {disfmarker} may maybe {disfmarker} maybe {disfmarker}", + "Grad F : Yeah . Well , we can skip the digits .", + "Professor B : We could . Fi - five minute report or something .", + "PhD E : It 's up to you . I don't {disfmarker}", + "Professor B : Yeah , yeah .", + "Grad F : Whatever you want .", + "Professor B : Well , I would love to hear about it ,", + "Grad F : What do you have to say ?", + "Professor B : especially since {disfmarker}", + "Grad F : I 'm interested , so {disfmarker}", + "Professor B : Yeah . Well , I 'm gonna be on the phone tomorrow , so this is just a {pause} good example of {pause} the sort of thing I 'd like to {pause} hear about .", + "PhD E : Wait . Why is everybody looking at me ?", + "PhD C : I don't know .", + "Grad F : Sorry .", + "Professor B : Cuz he looked at you", + "PhD H : What ?", + "Professor B : and says you 're sketching .", + "PhD E : Uh . I 'm not sure what you were referring to .", + "PhD H : I {disfmarker} I {disfmarker} I {disfmarker} I 'm not {disfmarker} actually , I 'm not sure what {disfmarker} ? Are we supposed to have done something ?", + "Grad F : No . We were just talking before about alternating the subject of the meeting .", + "PhD H : Oh .", + "PhD E : Uh - huh .", + "Grad F : And this week we were gonna try to do {pause} t automatic transcription {pause} status .", + "PhD H : Alternating .", + "PhD E : I wasn't here last week . Sorry .", + "PhD H : Oh !", + "PhD E : Oh .", + "Grad F : But we sort of failed .", + "PhD H : We did that last week . Right ?", + "PhD E : Hhh .", + "Grad F : No .", + "Professor B : I thought we did .", + "Grad F : Did we ? OK .", + "PhD H : Yeah . We did .", + "Grad F : OK . So now {disfmarker} now we have the schedule . So next week we 'll do automatic transcription status , plus anything that 's real timely .", + "PhD H : OK .", + "PhD E : Oh . OK .", + "Postdoc A : OK .", + "Professor B : OK . Whew !", + "PhD C : Good update .", + "Grad F : Whew !", + "Professor B : That was {disfmarker}", + "Grad F : Dodged that bullet .", + "Professor B : Yeah . Nicely done , Liz .", + "Postdoc A : A woman of few words .", + "Professor B : But {disfmarker} but lots of prosody . OK . {vocalsound} OK .", + "Grad F : Th", + "PhD H : Uh , I mean , we {disfmarker} we really haven't done anything .", + "Grad F : Excuse me ?", + "PhD H : Sorry .", + "Postdoc A : Well , since last week .", + "PhD E : Yeah , we 're {disfmarker}", + "PhD H : I mean , the {disfmarker} the next thing on our agenda is to go back and look at the , um {disfmarker} {vocalsound} the automatic alignments because , uh , I got some {disfmarker} I {disfmarker} I {disfmarker} I learned from Thilo what data we can use as a benchmark to see how well we 're doing on automatic alignments of the background speech {disfmarker} or , of the foreground speech with background speech .", + "Grad F : Yeah .", + "PhD H : So .", + "PhD E : And then , uh , I guess , the new data that Don will start to process {disfmarker}", + "PhD H : But , we haven't actually {disfmarker}", + "PhD E : the , um {disfmarker} when he can get these {disfmarker} You know , before we were working with these segments that were all synchronous and that caused a lot of problems", + "PhD H : Mmm .", + "PhD E : because you have timed sp at {disfmarker} on either side .", + "Grad F : Oh . Right , right . Mm - hmm .", + "PhD E : And so that 's sort of a stage - two of trying the same kinds of alignments with the tighter boundaries with them is really the next step .", + "Grad F : Right .", + "Postdoc A : I 'll be interested .", + "PhD E : We did get our , um {disfmarker} I guess , good news . We got our abstract accepted for this conference , um {disfmarker} workshop , ISCA workshop , in , um , uh , New Jersey . And we sent in a very poor abstract , but they {disfmarker} very poor , very quick . Um , but we 're hoping to have a paper for that as well , which should be an interesting {disfmarker}", + "Grad F : When 's it due ?", + "PhD E : The t paper isn't due until August . The abstracts were already due . So it 's that kind of workshop .", + "Grad F : Mm - hmm .", + "PhD E : But , I mean , the good news is that that will have sort of the European experts in prosody {disfmarker} sort of a different crowd , and I think we 're the only people working on prosody in meetings so far , so that should be interesting .", + "Postdoc A : What 's the name of the meeting ?", + "PhD E : Uh , it 's ISCA Workshop on Prosody in Speech Recognition and Understanding , or something like that {disfmarker}", + "PhD H : It 's called Prosody to {disfmarker}", + "Grad F : Mm - hmm .", + "Postdoc A : Good .", + "PhD E : some generic {disfmarker} Uh , so it 's focused on using prosody in automatic systems and there 's a {disfmarker} um , a web page for it .", + "Professor B : Y you going to , uh , Eurospeech ? Yeah .", + "Grad F : I don't have a paper", + "PhD H : Yeah .", + "Grad F : but I 'd kinda like to go , if I could . Is that alright ?", + "Professor B : We 'll discuss it .", + "Grad F : OK . {vocalsound} I guess that 's \" no \" .", + "Professor B : My {disfmarker} my {disfmarker} my car {disfmarker} my car needs a good wash , by the way .", + "Grad F : OK . Well , that th Hey , if that 's what it takes , that 's fine with me .", + "Professor B : Um .", + "Grad F : I 'll pick up your dry - cleaning , too . Should we do digits ?", + "Professor B : Yeah .", + "Grad F : Uh .", + "PhD H : Can I go next ? Because I have to leave , actually .", + "Grad F : Yep . Go for it . Hmm ! Thanks . Thank you .", + "Professor B : So you get to be the one who has all the paper rustling . Right ?" + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "test", + "file_id": 11, + "turns": [ + 10, + 97 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "Animal Characteristics", + "speaker": "" + }, + "summary": "The Project Manager used the idea of drawing their favorite animal and use that animal's characteristics to help them with the remote control project. The User Interface Designer drew a dolphin because it is a smart, cute and a graceful swimmer. The Industrial Designer drew a cat because it sleeps all day and is easy to draw. The Marketing Manager drew a horse, because it is pretty, environment friendly, sturdy and a nice animal. Finally, the Project Manager drew a pig. While explaining the characteristics they enjoyed on their respective animals, they agreed on using some of those animals\u00b4characteristics into the remote control's characteristics, such as being water-resistant, strong and ... furry.", + "title": "Favorite Animal Characteristics", + "relevant_turns": [ + 0, + 17, + [ + 26, + 63 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "Animal Characteristics", + "speaker": "" + }, + "summary": "The Project Manager used the idea of drawing their favorite animal and use that animal's characteristics to help them with the remote control project. The User Interface Designer drew a dolphin, the Industrial Designer drew a cat and the Marketing Manager drew a horse. Finally, the Project Manager drew a pig. While explaining the characteristics they enjoyed on their respective animals, they agreed on using some of those animals\u00b4characteristics into the remote control's characteristics.", + "title": "Favorite Animal Characteristics", + "relevant_turns": [ + 0, + 17, + [ + 26, + 63 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "Project Plan , Target Revenue", + "speaker": "" + }, + "summary": "The Project manager informed the selling price was twenty-five Euro and the profit aim was fifty million Euro. After some fast calculus, they reach the conclusion that to reach that target they would need to sell four million units.", + "title": "Project Plan and Target Revenue", + "relevant_turns": [ + [ + 74, + 87 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "fully", + "specificity": "high", + "topic": "Project Plan and Target Revenue", + "speaker": "" + }, + "summary": "The Project Manager informed the selling price goal was twenty-five Euro and profit aim was fifty million Euro. To reach those targets with a profit for each of twelve fifty, that represented four million. For such, they hoped to sell internationally.", + "title": "Target Revenue", + "relevant_turns": [ + 74, + 80 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "The Furry Characteristic", + "speaker": "User Interface" + }, + "summary": "The Project Manager expressed his wish for the furry characteristic. The User Interface Designer immediately converted the furry characteristic into a soft textile tactile characteristic.", + "title": "The Furry Characteristic", + "relevant_turns": [ + [ + 66, + 70 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "high", + "specificity": "high", + "topic": "The Furry Characteristic", + "speaker": "User Interface" + }, + "summary": "The Project Manager expressed the idea for a remote control that's water-resistant, strong and furry. Although surprised at first, the User Interface Designer converted the idea of the furry characteristic into a soft textile touch.", + "title": "The Furry Characteristic", + "relevant_turns": [ + [ + 66, + 70 + ] + ] + } + ], + "source": [ + "Project Manager : Okay . Um so f here's our agenda for today . Um we're gonna do some tool training , project plan and discuss then close . {vocalsound} Um so . So our aim is to produce a remote control that is original , trendy and user friendly . And to do this , we have to {disfmarker} um there's certain things we have to consider about functional aspects and conceptual design of the thing . So . We'll get to that . Oh there it is . Right . Functional design , conceptual design and detailed design . So throughout our next couple of meetings we'll we'll be covering these things . Um {vocalsound} so we're gonna try out our white board . If we'll all draw our favourite animal , to sum up the characteristics of that animal . Okay .", + "User Interface : So you want us to draw it and then talk about it ? Or just draw it ?", + "Project Manager : {vocalsound}", + "Marketing : I think both . {vocalsound}", + "Project Manager : Yeah . Both . Yeah {vocalsound} .", + "User Interface : Okay . Why don't we do both . Right .", + "Marketing : Who starts ? We ought to decide who starts and {vocalsound} all that . No ?", + "Project Manager : Any volunteers ?", + "Marketing : Uh-huh .", + "Project Manager : Does anyone know what they wanna draw ? {vocalsound}", + "Industrial Designer : {vocalsound}", + "User Interface : Mm , I gotta think about it for a second like . Uh {disfmarker} Does it have to be {vocalsound} functional , trendy and user friendly ? {vocalsound}", + "Project Manager : {vocalsound} I don't think so .", + "Industrial Designer : {vocalsound}", + "User Interface : Um . Okay , I'll draw . I'll draw one .", + "Project Manager : {gap}", + "User Interface : Make sure {gap} my things here . Uh-oh . Right . Okay , my favourite animal is {disfmarker} see . {vocalsound} Oops .", + "Project Manager : A dolphin .", + "User Interface : Yeah , it's {vocalsound} {disfmarker}", + "Industrial Designer : {vocalsound}", + "Project Manager : {vocalsound} 'S like playing Pictionary .", + "User Interface : {vocalsound} Yeah , I guess it has a fin on top too , yeah . {vocalsound} It's my dolphin .", + "Project Manager : {vocalsound} So what characteristics do you like about your animal ? {vocalsound}", + "Industrial Designer : {vocalsound}", + "User Interface : I like its tail .", + "Industrial Designer : {vocalsound}", + "User Interface : {vocalsound} Um , no , I think dolphins are really uh {disfmarker} I dunno , they're smart and they they're cute and they like swimming and that's cool , like {disfmarker}", + "Project Manager : {vocalsound} They're graceful .", + "User Interface : they're graceful yeah , and they're so {disfmarker}", + "Project Manager : Sleek {vocalsound} .", + "User Interface : {vocalsound} Yeah they're sleek", + "Industrial Designer : {vocalsound}", + "User Interface : and they look intelligent and I don't know , they're {disfmarker} I guess it's the whole like binocular vision thing .", + "Project Manager : I don't know how intelligent that one looks {vocalsound} .", + "Industrial Designer : {vocalsound}", + "User Interface : Yeah he he doesn't look that smart {vocalsound} . He's a {disfmarker} {vocalsound} I dunno um they're {disfmarker} I think it's cool the the um {vocalsound} the interaction that or the th things that {disfmarker} the reasons people seem to like you know {disfmarker} you get ex you know people are sitting on the beach and p they're like oh look there's dolphins and it's kinda like {vocalsound} {disfmarker} but they're you know they jump around in the water and they're happy and they're mammals , but they swim . {gap} {vocalsound}", + "Project Manager : Yes . {vocalsound} Does anybody else wanna draw their animal ?", + "Industrial Designer : Suppose I can draw an animal , yeah .", + "Project Manager : {vocalsound} {vocalsound} .", + "User Interface : {vocalsound}", + "Project Manager : Uh-oh there goes the ten .", + "Industrial Designer : {vocalsound} Yeah .", + "Project Manager : {vocalsound} It's a cat . {vocalsound}", + "User Interface : {vocalsound}", + "Industrial Designer : I don't know . They sleep all day , {vocalsound} they're easy to draw {vocalsound} .", + "Project Manager : {vocalsound} Do you wanna {gap} anything ?", + "Marketing : Uh yeah .", + "Project Manager : I dunno if the the {disfmarker}", + "Industrial Designer : I think the pen is running out of {disfmarker}", + "Marketing : Well I had the cat as well , but uh I've got a spare one .", + "Project Manager : ah .", + "User Interface : {vocalsound}", + "Industrial Designer : {vocalsound}", + "Marketing : So I'll use the spare one . Um but it's harder to draw {gap} um .", + "User Interface : And the pen's dying {vocalsound} .", + "Marketing : Um .", + "Project Manager : A horse .", + "User Interface : Horse .", + "Marketing : Uh . Um I don't {vocalsound} really know how the legs go ,", + "Industrial Designer : {vocalsound}", + "Project Manager : That's very good .", + "Industrial Designer : {vocalsound}", + "Marketing : but anyway I will do that . Um , and the main reason is they're pretty . I think they're very pretty and they go well with the environment , and I like the way they run and I used to do horse riding and they're just very sort of sturdy and nice animals . And I like the way um they feel , sort of under under the hand , I think that's pretty much it . Um {disfmarker}", + "Project Manager : {gap} Yeah . This cord's {disfmarker} {gap} Uh . Right . Actually I haven't thought of anything yet {vocalsound} . Uh {disfmarker} It's a pig .", + "Industrial Designer : {vocalsound}", + "Marketing : {vocalsound}", + "Project Manager : {vocalsound} So I'm thinking we should design a remote control that's water resistant , strong and furry . What do you think , yeah ? This is {disfmarker}", + "User Interface : And furry .", + "Project Manager : yeah , well like a cat , you know , soft yeah .", + "Industrial Designer : {vocalsound}", + "User Interface : Textile {disfmarker} tactile , {vocalsound} tactile remote control .", + "Marketing : {vocalsound}", + "Project Manager : {vocalsound} Although {disfmarker} uh I'll just put there . Right .", + "User Interface : You're dragging a {disfmarker} you have a tail {vocalsound} .", + "Project Manager : {gap} Oh my gosh , this is disastrous . Sorry about that . {vocalsound} Okay . {vocalsound} So moving on . Our selling price goal is twenty five Euro and profit aim is fifty million Euro . So I'm guessing that we're not actually in Scotland , we're in some European country {vocalsound} . Um , and we will hope to sell this internationally .", + "User Interface : Sorry can you just say that {disfmarker} what's the {disfmarker} what are our price goals again ?", + "Project Manager : Um selling price is twenty five Euro . Profit aim fifty million Euro .", + "User Interface : Okay .", + "Marketing : How many should we sell then ? {vocalsound} Um , a lot ,", + "Project Manager : Anyone a mathematician ? {vocalsound}", + "Marketing : two two two million , {gap} two mi no , more f four million .", + "Industrial Designer : Two million .", + "Marketing : Four million . And it {disfmarker}", + "Industrial Designer : {vocalsound}", + "Marketing : well it's the profit so if a profit for each is twelve fifty , that'll do four million .", + "Industrial Designer : Oh , yeah .", + "Marketing : {vocalsound} It is a lot . Uh .", + "Project Manager : So f that's a fifty percent um uh . Um , I don't know what these mean because I didn't actually make the slide-show . Experience with remote control . So I guess we have to reflect on our experiences with remote controls to decide what um we would like to see in a convenient , practical , nice remote control . Um so do we have any initial ideas for uh how this remote control should be designed or formatted or the the buttons it should have ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "test", + "file_id": 25, + "turns": [ + 452, + 529 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "user requirements", + "speaker": "" + }, + "summary": "Marketing proposed a short analysis of the remote control market, and the fashion in general, to meet the user's requirements. Users wanted a fancy look and feel, without caring a lot about the functional matter, but still wanted it to be technologically innovative, and easy to use. Once it was established that the fancy look and feel were the most important characteristics for the user, it was suggested to use a natural design inspired in fruits and vegetables, as fashion in general was inspired by those, and to have a spongy touch, which people said they wanted.", + "title": "Designing Remote Control From User's Requirements", + "relevant_turns": [ + 3, + 5, + 8, + 12, + 16, + 20 + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "user requirements", + "speaker": "" + }, + "summary": "It was stated that users wanted a fancy look and feel in the first place, and also wanted the remote control to be technologically innovative, and easy to use.", + "title": "User's Requirements for Remote Control", + "relevant_turns": [ + 3, + 5, + 8, + 12, + 16, + 20 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "problem , fashion", + "speaker": "Marketing" + }, + "summary": "Marketing analysed fashion and the remote control market, concluding that people wanted a fancy look and feel, the designed should be inspired by fruits and vegetables, and has a spongy touch.", + "title": "Fashion in Remote Control Design", + "relevant_turns": [ + 3, + 5, + 12, + 14, + 16, + 18, + 20, + 28, + 66, + [ + 70, + 71 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "high", + "topic": "problem , fashion", + "speaker": "Marketing" + }, + "summary": "Marketing did an analysis of the remote control market and fashion in general, and considered that people wanted a fancy look and feel. Marketing stated that the trend was inspiration by fruits and vegetables, so that would be taken into account for the design, as well as a spongy touch, to give people what they wanted, that would be a fancy look and feel combined with fashion from Milan and Paris. Materials like plastic, rubber and wood were discussed, keeping fashion as priority.", + "title": "Fashion in Remote Control Design", + "relevant_turns": [ + 3, + 5, + 12, + 14, + 16, + 18, + 20, + 28, + 66, + [ + 70, + 71 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "decision , fulfilling user requirements", + "speaker": "" + }, + "summary": "The user's requirements were a fancy look and feel, technology and innovation, and a device easy to use. To fulfill the main requirement, everyone agreed to a device made of wood and rubber, with a natural design inspired by fruits or vegetables, and a spongy touch.", + "title": "Fulfilling User's Requirements With Fashion", + "relevant_turns": [ + 0, + 3, + 5, + 8, + 12, + 16, + 20, + 25, + 28, + 53, + [ + 57, + 74 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "decision , fulfilling user requirements", + "speaker": "" + }, + "summary": "Discussing the user requirements, it was found that the users wanted a fancy look and feel, above the functional features, users also wanted the remote control to be technologically innovative, and easy to use; in that order of ranking. So it was decided to focus first on the fashion aspect of look and feel, suggesting a natural design inspired in fruits and vegetables, because that was the trend in general fashion, also, as users wanted a spongy touch, several materials such as plastic-like, rubber, and wood were discussed, concluding that it could be part of wood and some rubber for the buttons, being a little spongy, fashion and ecol.", + "title": "Fulfilling User's Requirements With Fashion", + "relevant_turns": [ + 0, + 3, + 5, + 8, + 12, + 16, + 20, + 25, + 28, + 53, + [ + 57, + 74 + ] + ] + } + ], + "source": [ + "Project Manager : Participant four ? Functional requirements ?", + "Marketing : Uh no , trend watching . {vocalsound} The other one . {vocalsound}", + "Project Manager : This one ?", + "Marketing : Yeah . Uh , I think so , just {disfmarker} Yeah , so just to meet the user requirements I would just do a s short anal analysis of the remote control market and to kind of um have a better overview of what's the fashion in general I've checked more than only the remote control market , so next .", + "Project Manager : {vocalsound}", + "Marketing : So again , it's pretty much similar to what I've said in the previous meeting . Um user really really want a fancy look and feel . They're not so so interested in uh functional look and feel , okay . Like the one you've shown , David , with all the buttons and {disfmarker} I mean {vocalsound} i i it sounds good technically", + "User Interface : Mm .", + "Industrial Designer : Mm .", + "Marketing : but it's it's not what they want and uh {disfmarker} So , second point is they still want it it to be technologically innovative , so maybe it's sort of related to what you've said with the speech recognition and so on .", + "Project Manager : Okay .", + "Marketing : At the same time , it's important that it's easy to use . So that were the three first points from the remote control uh analysis .", + "Industrial Designer : {gap}", + "Marketing : Now i if we look at fashion in general um {disfmarker} Okay . Wha what we really see this year is that uh everything from clothes to shoes and furniture is is inspired by fruits and vegetables ,", + "Industrial Designer : Ah yes .", + "Marketing : okay , so I think we really have to take this into account for the design of the the thing .", + "Industrial Designer : Yeah , yeah . Okay , yeah .", + "Marketing : 'Cause it's it's really what people want . Even if it's in general fashion , we want it to be in the remote control . And then uh if if we take the ordering or the ranking of all the points , fancy look and feel has , on a score of seven would have six as importance . Uh the remote control has to be technologically innovative , it's three . Then easy to use uh it's not so important actually with respect to other y other ones .", + "Industrial Designer : Okay .", + "Marketing : So we see fancy look an look and feel is the most important one , and then if we combine this with the fashion uh from Milan and Paris", + "Industrial Designer : And fruit and vegetables yeah .", + "Marketing : we go to the fruits and vede vegetables . And the other point I haven't mention is people wan want to have a spongy touch ,", + "Industrial Designer : {vocalsound} Spongy {vocalsound} 'Kay .", + "Marketing : okay so this is this maybe doesn't really fit with the wooden design .", + "Industrial Designer : Okay , yeah , yeah .", + "Marketing : I dunno .", + "Industrial Designer : Yeah , but the problem is which kind of material do you need to to be spongy ?", + "Marketing : Yeah thi this is this would be like um", + "Industrial Designer : Pla S", + "Marketing : plastic-like , but rubber , mayb maybe , you know , rubber-like uh", + "Industrial Designer : Very stuff {disfmarker} Okay , rubber rubber desi okay , yeah . Yeah .", + "Marketing : device , so um", + "Industrial Designer : Yeah .", + "Marketing : Okay , tha tha that was the main point , I think , from the trend in fashion .", + "Industrial Designer : Okay .", + "Project Manager : So you think {gap} case . Something spongy . {vocalsound} Someth no wood .", + "Industrial Designer : {vocalsound}", + "User Interface : {vocalsound}", + "Marketing : {vocalsound}", + "Industrial Designer : {vocalsound} No wood but {disfmarker} Plastic ?", + "Marketing : Maybe not no wood , but I mean ma maybe not the part you touching you know .", + "Industrial Designer : Would some {disfmarker}", + "User Interface : Pla", + "Project Manager : Maybe you {disfmarker}", + "Industrial Designer : I think we can have wood for example in the bottom and , you know . It depends on the design we want ,", + "Marketing : Yeah , maybe the base .", + "Industrial Designer : so .", + "Project Manager : It's it's natural .", + "Marketing : But still y", + "Project Manager : Th The feeling is natural ,", + "Industrial Designer : Yeah , it's natural", + "Marketing : Yeah .", + "Industrial Designer : and i", + "Project Manager : so maybe we can stay with wood .", + "Industrial Designer : And it can be correlated to energy , solar energy , so for the marketing aspect , you know , saying that it's ecol", + "Marketing : Yeah , I mean it's not exactly right for the spongy point of view .", + "Industrial Designer : Mm , yeah , it's not right , so .", + "Project Manager : But it's still fashion .", + "Marketing : But we could maybe have both like part of wood and some rubber for the buttons ,", + "Industrial Designer : Okay .", + "Marketing : or", + "Project Manager : Yeah ,", + "Marketing : I dunno .", + "Project Manager : something that you can {vocalsound} into it .", + "Marketing : Yeah ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 54, + "turns": [ + 715, + 766 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "SpeechCorders", + "speaker": "PhD F , Professor A" + }, + "summary": "PhD F asked what was the idea behind SpeechCorders. Professor A said that they did analysis-by-synthesis by trying every possible excitation they had in their codebook and found the best matches.", + "title": "The Function of SpeechCorders", + "relevant_turns": [ + [ + 12, + 28 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "high", + "specificity": "normal", + "topic": "SpeechCorders", + "speaker": "PhD F , Professor A" + }, + "summary": "PhD F asked what was the idea behind SpeechCorders because they didn't even have to detect voiced speech. Professor A said the modern ones didn't do a simple switch and they worked on the codebook excitation whereby they did analysis-by-synthesis and tried every possible excitation they had in their codebook and found the one that matched best.", + "title": "The Function of SpeechCorders", + "relevant_turns": [ + [ + 12, + 28 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "digit", + "speaker": "PhD B , Professor A" + }, + "summary": "PhD B said that there were no sequences of two-long or three-long digit strings in any of the Aurora training data while the language model allowed for the production of infinitely long sequences of digits so it was odd that there were no two or three long digits. Professor A suggested looking at the testing data that had two or three.", + "title": "Digit Strings in Training Data", + "relevant_turns": [ + [ + 24, + 51 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "high", + "topic": "digit", + "speaker": "PhD B , Professor A" + }, + "summary": "PhD B; looking at the language model that's used in the HTK recognizer, which is basically just a big loop; That model would allow for the production of infinitely long sequences of digits, And the interesting thing was it turns out that there are no sequences of two-long or three-long digit strings in any of the Aurora training data; there was a one-long path and there was a four-long and a five-long; I tried that and it got way worse. There were lots of deletions; Professor A; what about the testing data; there's some testing data that has two or three; we're gonna read some more digit strings I guess.", + "title": "Digit Strings in Training Data", + "relevant_turns": [ + [ + 24, + 51 + ] + ] + } + ], + "source": [ + "Professor A : Yeah . Well back twenty years ago when I did this voiced - unvoiced stuff , we were getting more like {vocalsound} ninety - seven or ninety - eight percent correct in voicing . But that was {vocalsound} speaker - dependent {vocalsound} actually . We were doing training {vocalsound} on a particular announcer", + "PhD F : Mm - hmm .", + "Professor A : and {disfmarker} and getting a {vocalsound} very good handle on the features .", + "PhD F : Mm - hmm .", + "Professor A : And we did this complex feature selection thing where we looked at all the different possible features one could have for voicing and {disfmarker} {vocalsound} and {disfmarker} and uh {disfmarker} and exhaustively searched {vocalsound} all size subsets and {disfmarker} and uh {disfmarker} for {disfmarker} for that particular speaker and you 'd find you know the five or six features which really did well on them .", + "PhD B : Wow !", + "PhD F : Mm - hmm .", + "Professor A : And then doing {disfmarker} doing all of that we could get down to two or three percent error . But that , again , was speaker - dependent with {vocalsound} lots of feature selection", + "PhD F : Mm - hmm .", + "Professor A : and a very complex sort of thing .", + "PhD F : Mmm .", + "Professor A : So I would {disfmarker} I would believe {vocalsound} that uh it was quite likely that um looking at envelope only , that we 'd be {vocalsound} significantly worse than that .", + "PhD F : Mm - hmm .", + "Professor A : Uh .", + "PhD F : And the {disfmarker} all the {disfmarker} the SpeechCorders ? what 's the idea behind ? Cuz they {disfmarker} they have to {disfmarker} Oh , they don't even have to detect voiced spe speech ?", + "Professor A : The modern ones don't do a {disfmarker} {vocalsound} a simple switch .", + "PhD F : They just work on the code book", + "Professor A : They work on the code book excitation .", + "PhD F : and find out the best excitation .", + "Professor A : Yeah they do {vocalsound} analysis - by - synthesis . They try {disfmarker} they {disfmarker} they try every {disfmarker} every possible excitation they have in their code book and find the one that matches best .", + "PhD F : Yeah . Mmm . Alright . Yeah . So it would not help .", + "Professor A : Yeah .", + "Grad E : Hmm .", + "Professor A : Uh . O K .", + "PhD B : Can I just mention one other interesting thing ?", + "Professor A : Yeah .", + "PhD B : Um . One of the ideas that we {pause} had come up with last week for things to try to {vocalsound} improve the system {disfmarker} Um . Actually I {disfmarker} I s we didn't {disfmarker} I guess I wrote this in after the meeting b but {vocalsound} the thought I had was um looking at the language model that 's used in the HTK recognizer , which is basically just a big {vocalsound} loop ,", + "Grad E : Mm - hmm .", + "PhD B : right ? So you {disfmarker} it goes \" digit \"", + "PhD D : Mm - hmm .", + "PhD B : and then that can be {disfmarker} either go to silence or go to another digit , which {disfmarker} That model would allow for the production of {vocalsound} infinitely long sequences of digits , right ?", + "Professor A : Right .", + "PhD B : So . I thought \" well I 'm gonna just look at the {disfmarker} what actual digit strings do occur in the training data . \"", + "Professor A : Right .", + "PhD B : And the interesting thing was it turns out that there are no sequences of two - long or three - long digit strings {pause} in any of the Aurora training data . So it 's either one , four , five , six , uh up to eleven , and then it skips and then there 's some at sixteen .", + "Professor A : But what about the testing data ?", + "PhD B : Um . I don't know . I didn't look at the test data yet .", + "Professor A : Yeah . I mean if there 's some testing data that has {disfmarker} has {disfmarker} {vocalsound} has two or three {disfmarker}", + "PhD B : So . Yeah . But I just thought that was a little odd , that there were no two or three long {disfmarker} Sorry . So I {disfmarker} I {disfmarker} just for the heck of it , I made a little grammar which um , you know , had it 's separate path {pause} for each length digit string you could get . So there was a one - long path and there was a four - long and a five - long", + "Professor A : Mm - hmm .", + "PhD B : and I tried that and it got way worse . There were lots of deletions .", + "Professor A : Mm - hmm .", + "PhD B : So it was {disfmarker} {vocalsound} you know , I {disfmarker} I didn't have any weights of these paths or {disfmarker} I didn't have anything like that .", + "Professor A : Mm - hmm .", + "PhD B : And I played with tweaking the {vocalsound} word transition penalties a bunch , but I couldn't go anywhere .", + "Professor A : Hmm .", + "PhD B : But um . I thought \" well if I only allow {disfmarker} \" Yeah , I guess I should have looked at {disfmarker} to see how often there was a mistake where a two - long or a three - long path was actually put out as a hypothesis . Um . But .", + "Professor A : Hmm .", + "PhD B : So to do that right you 'd probably want to have {disfmarker} {vocalsound} allow for them all but then have weightings and things . So . I just thought that was a interesting {vocalsound} thing about the data .", + "Professor A : OK . So we 're gonna read some more digit strings I guess ?", + "PhD B : Yeah . You want to go ahead , Morgan ?", + "Professor A : Sure ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "test", + "file_id": 22, + "turns": [ + 57, + 481 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "user interface design , remote control", + "speaker": "" + }, + "summary": "Regarding the user interface design, User Interface found two types of remote controls, the multi-function control, and the ease-of-use control. User Interface thought the buttons felt good in the simpler control. Project Manager thought that not all functions in a multi-function were being used. Industrial Designer agreed to use the simpler control.", + "title": "Discussion About User Interface Design of Remote Control", + "relevant_turns": [ + [ + 6, + 249 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "normal", + "topic": "user interface design , remote control", + "speaker": "" + }, + "summary": "On the matter of the user interface design, User Interface found two different kinds of remote controls, the multi-function control, with many possibilities, and the ease-of-use control, with fewer possibilities but a great feeling in touching the buttons. User Interface mentioned that the new goal was for younger people, and thought that the ease-of-use controller was the best possibility. Project Manager said that not all extra features were used very often. Marketing shared the three most used functions, channel selection, volume, and teletext. User Interface said they could make a nice design when there were not many buttons in it. Industrial Designer said that they could have saved costs by not adding too many functions and that the savings could be used for a nice design.", + "title": "Discussion About User Interface Design of Remote Control", + "relevant_turns": [ + [ + 6, + 249 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "ten digits , interface design , remote control", + "speaker": "Industrial Designer" + }, + "summary": "Industrial Designer wasn't sure about using the ten digits and thought it was not relevant because, for a regular TV user who just watched Duch television networks, the ten-digit buttons weren't needed. Industrial Designer thought the ten buttons looked a bit dull and that something specific should be done with them to make them look fancier. Industrial Designer suggested playing with the shape, size, and color of the buttons.", + "title": "Industrial Designer's Thoughts on Ten-Digit Buttons", + "relevant_turns": [ + [ + 348, + 354 + ], + [ + 357, + 382 + ], + [ + 390, + 392 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "fully", + "specificity": "high", + "topic": "ten digits , interface design , remote control", + "speaker": "Industrial Designer" + }, + "summary": "Ten digits; Industrial Designer, imagine, have a satellite decoder and, about six hundred channels, you want this; but if you're a regular TV user, just want to watch the Dutch television networks, use about ten buttons, enough; how often do you watch all these channels? Targeting at the younger audience, more channels than the older people; probably right. Industrial Designer, ten buttons look a bit dull, the design, should, be done something specific with it; experiment, with shape or with size or with colour, that kind of thing.", + "title": "Industrial Designer's Thoughts on Ten-digit Buttons", + "relevant_turns": [ + [ + 348, + 354 + ], + [ + 357, + 382 + ], + [ + 390, + 392 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "interface design , remote control", + "speaker": "User Interface" + }, + "summary": "User Interface thought that for the interface design, instead of a stick, they should have used a round button that could have been pushed in four directions. User Interface suggested a button similar to a split mode, where you could watch two channels on the same screen and change from one channel to the other. User Interface was in favor of using the ten-digit buttons. User Interface would not have bought the remote control if it had not had a ten-digit button.", + "title": "User Interface's Thoughts on Interface Design", + "relevant_turns": [ + [ + 276, + 290 + ], + 318, + [ + 349, + 377 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "interface design , remote control", + "speaker": "User Interface" + }, + "summary": "User Interface suggested a round button for the interface design, that could be pushed in four directions, also proposed a button to change between two channels shown on the screen, and supported the use of the ten-digit buttons.", + "title": "User Interface's Thoughts on Interface Design", + "relevant_turns": [ + [ + 276, + 290 + ], + 318, + [ + 349, + 377 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "stick , round button", + "speaker": "Industrial Designer , User Interface , Marketing" + }, + "summary": "Industrial Designer suggested a stick with lights to signal the button pushed. User Interface recommended a round button because the stick might break. Marketing said it could have attracted young and old people.", + "title": "Discussion on the Use of Sticks in Remote Control", + "relevant_turns": [ + [ + 266, + 289 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "normal", + "topic": "stick , round button", + "speaker": "Industrial Designer , User Interface , Marketing" + }, + "summary": "Industrial Designer was thinking about a more elaborate way of controlling by using sticks. Industrial Designer suggested using light so when the stick was moved, people would have known when they pushed the button. User Interface suggested instead a round button because a stick was vulnerable when falling down. Industrial Designer agreed and mentioned it would have looked fancier. Marketing mentioned it could have attracted younger people because it was new, and it might have attracted older people because it was easy to use.", + "title": "Discussion on the Use of Sticks in Remote Control", + "relevant_turns": [ + [ + 266, + 289 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "advanced features , user-friendliness , functions", + "speaker": "User Interface , Project Manager" + }, + "summary": "Project Manager wanted a balance between advanced features and user-friendliness, so asked for the functions. Volume, program selecting, teletext, split mode, and voice recognition were mentioned. User Interface proposed a button like a split mode.", + "title": "Advanced Features and User-Friendliness", + "relevant_turns": [ + [ + 303, + 322 + ], + 393 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "advanced features , user-friendliness , functions", + "speaker": "User Interface , Project Manager" + }, + "summary": "Project Manager wanted to find a balance between the advanced features and the user-friendliness. User Interface did not think it was necessary to discuss that. But, Project Manager said they had to decide in that meeting. Project Manager asked for kinds of functions and gave an example that the most important were volume and program selecting. User Interface suggested a button similar to a split mode, where you could switch to two channels, for example, channel four, and change to channel six.", + "title": "Advanced Features and User-Friendliness", + "relevant_turns": [ + [ + 303, + 322 + ], + 393 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "ten-digit , button , channels", + "speaker": "Industrial Designer , User Interface , Marketing" + }, + "summary": "User Interface believed they should include the ten-digit button, to which Marketing agreed and gave an example, wanting to go to channel ninety and have that possibility. Industrial Designer, did not think it was relevant to have it but saw the reason when you have more than six hundred channels. However, Industrial Designer thought that for a regular TV user it was not necessary. Marketing pointed out that younger people would have liked the button since they watched more channels than older people. Industrial Designer agreed.", + "title": "Discussion About Ten-Digit Buttons", + "relevant_turns": [ + [ + 348, + 391 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "ten-digit , button , channels", + "speaker": "Industrial Designer , User Interface , Marketing" + }, + "summary": "User Interface believed they should include the ten-digit button. Marketing agreed. Industrial Designer did not think it was relevant for a regular TV user. Marketing pointed out younger people watched more channels. Industrial Designer agreed.", + "title": "Discussion About Ten-Digit Buttons", + "relevant_turns": [ + [ + 348, + 391 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "speech recognition , younger people", + "speaker": "Industrial Designer , Project Manager , Marketing" + }, + "summary": "Marketing mentioned younger people liked speech recognition. Industrial Designer thought it could be costly. Project Manager suggested removing the ten-digit button to add speech recognition.", + "title": "Discussion on Speech Recognition", + "relevant_turns": [ + [ + 393, + 424 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "normal", + "topic": "speech recognition , younger people", + "speaker": "Industrial Designer , Project Manager , Marketing" + }, + "summary": "Marketing mentioned younger people would like speech recognition. However, Marketing thought it might be expensive and hard to implement. Industrial Designer thought it could be combined with the find the remote control and mentioned speech recognition made it easy to change the channel. Project Manager suggested removing the ten-digit button to add speech recognition. Industrial Designer mentioned it had the advantage of making it easy to implement, but the disadvantage of less long life to the batteries.", + "title": "Discussion on Speech Recognition", + "relevant_turns": [ + [ + 393, + 424 + ] + ] + } + ], + "source": [ + "User Interface : Yeah , I'll start .", + "Project Manager : Uh uh yeah . Okay ,", + "Industrial Designer : Yes .", + "Project Manager : great .", + "User Interface : Um {disfmarker} Oh , how can I uh {disfmarker} Geez , and sli and show . Um {disfmarker} Just uh press it .", + "Project Manager : {vocalsound}", + "User Interface : Uh yes . Alright . Um well w we uh we had discussed this already in the fin in the previous uh discussion . {vocalsound} Uh the method of the remote control is just {disfmarker} the function of remote control is basically to send messages to the television set . So that was the main uh important thing what a remote control should do .", + "Project Manager : Yeah .", + "User Interface : Then I found uh two different kind of remote controls , the multi-function uh remote control with many possibilities , but um the lack of the feeling I already mentioned uh in the previous uh discussion .", + "Project Manager : Mm-hmm .", + "User Interface : And the ease-of-use remote control with uh the less p possibilities but a great feeling in in touching the buttons .", + "Project Manager : Yeah .", + "User Interface : {vocalsound} Um but um {disfmarker} yeah . My personal preferences were ease of uh {disfmarker} the easy to use remote control , because uh the user-friendliness and uh {disfmarker} it can be more trendy in in user design . But um your new goal f was for uh people than {disfmarker} less than forty years old .", + "Project Manager : Uh-huh .", + "User Interface : So maybe um the multi-function can be implemented in uh in our design . But it should b I think it should be a combination , but teletext buttons are not uh in our design . So it should uh take out , well , eight buttons or so . But my {disfmarker} in {gap} my opinion , the the easy to use R_C_ is uh the best uh possi possibility for us .", + "Project Manager : Okay . Uh Ruud , did you get that ?", + "User Interface : Yeah .", + "Marketing : Yeah , uh b uh most .", + "Project Manager : Okay , so", + "Marketing : {vocalsound}", + "Project Manager : the important thing here is {disfmarker}", + "User Interface : {vocalsound} And it's also i indeed uh uh Ruud's uh insight in the in the topic .", + "Marketing : Oh , user-friendly .", + "Project Manager : In the market , yeah .", + "User Interface : Yeah , what what does the market want ? I I don't know .", + "Project Manager : Yeah , okay , w we will s we all uh {disfmarker}", + "User Interface : Just for uh for user desi uh user uh friendliness I uh should choose for the the ease of use remote control .", + "Project Manager : Yeah . Okay . Sebastian .", + "User Interface : And just about uh the user interface , I came up with um {vocalsound} an easy remote control and an advanced remote control .", + "Project Manager : Yeah .", + "User Interface : What should we choose in in design ?", + "Project Manager : Yeah . Well , um according to Ruud , um people do not use um all the extra features very very often .", + "User Interface : Well , the extra functions .", + "Project Manager : So {disfmarker}", + "Marketing : I have the numbers r I have the numbers right here .", + "Project Manager : Okay .", + "Marketing : Well , t uh we won't support teletext which which was the third-most {disfmarker} the second-most used function .", + "User Interface : Used option .", + "Project Manager : Okay . {vocalsound}", + "Industrial Designer : {vocalsound} Okay . {vocalsound}", + "Project Manager : Well , we we do have a wise board , so I'm not questioning that . {vocalsound}", + "Marketing : {vocalsound}", + "User Interface : {vocalsound}", + "Marketing : Uh well {disfmarker} yeah , channel selection is obviously the most important .", + "Project Manager : Yeah . Okay , so on the relevance scale uh the channel selection , the volume selection and the teletext .", + "Marketing : So {disfmarker} Yeah . Yeah .", + "Project Manager : Well , we skip that .", + "Marketing : So {disfmarker}", + "Project Manager : Okay .", + "User Interface : Well , so it just th the basic functions . And we don't have to use it for D_V_D_ players uh and all kind of stuff .", + "Industrial Designer : No , no .", + "Project Manager : No .", + "User Interface : So {disfmarker} {vocalsound}", + "Marketing : Nope .", + "Industrial Designer : So that's out of the question .", + "Project Manager : Yeah .", + "User Interface : Yeah . Just through uh the easy uh design . We can make uh a nice design when when there's not mu uh much buttons in it .", + "Industrial Designer : So {disfmarker}", + "Project Manager : Uh uh uh I think we should go for the easier one .", + "Industrial Designer : I think also . Yes . Well ,", + "Project Manager : No .", + "User Interface : So {disfmarker}", + "Industrial Designer : we should save costs uh by not implementing a lot of functions and uh the money that we can save from that we should use for uh having a nice design and uh thinking about the user interface", + "Project Manager : Yeah . Okay ,", + "Industrial Designer : and {disfmarker}", + "Project Manager : Ruud , how do you feel about that ? Uh do you agree , do you think the market would would respond to uh a simple {disfmarker}", + "Marketing : Uh well if we um include other uh innovative functions {disfmarker} {vocalsound} uh then they uh might ,", + "Project Manager : Mm-hmm .", + "Marketing : 'cause young people uh like new features .", + "Project Manager : Mm yeah .", + "Marketing : So {disfmarker}", + "Industrial Designer : Yeah , that's right .", + "Project Manager : Okay , so this is is kind of uh {disfmarker}", + "Industrial Designer : Mm .", + "User Interface : Uh just a few buttons , trendy design , nice lightning effects wh and the sound .", + "Industrial Designer : Okay . Well , is it {disfmarker} maybe there's another possibility . You can make it look like an easy s piece of equipment , but it's quite elaborated , uh because it has many functions .", + "Project Manager : Yeah .", + "Industrial Designer : Maybe it's more important to make the {disfmarker} make it look like a very uh friendly , easy to catch piece of equipment , but um nevertheless {disfmarker}", + "Project Manager : But but are we not in in the in the manual uh {disfmarker} I mean if you have few buttons , no display , um I mean uh I guess it's l it's working with with a shift functions and um one button can uh", + "Industrial Designer : Mm-hmm . Mm-hmm . Ok like that . Well , I was more thinking about a more elaborate way of controlling , by by these kinds of sticks or something like that . I don't know if if it's user-friendly . That's your field of expertise .", + "Project Manager : But but how does how does the remote uh report uh r uh give back to the user w in what state it is ?", + "User Interface : Yeah , I don't know yet . {vocalsound}", + "Project Manager : Because we do not implement uh a user history .", + "Industrial Designer : Mm-hmm . There's {disfmarker} no , but there's no way to do that , because we cannot implement that kind of the system .", + "Project Manager : I know , but but if we use uh like a stick , for example , um {disfmarker}", + "Industrial Designer : W Mm-hmm . Well , maybe we can use a light for that . When you move the stick to a to a position , maybe uh a light next to it can lit up . So you know I've just uh pushed the button , or I changed the channel or t uh turned up the volume . Something like that .", + "Marketing : And if you use that stick for volume control and channel uh selection , you have the m two most important functions in one uh button .", + "Project Manager : Yeah . Uh and we could have other buttons for the for the advanced uh functions .", + "Industrial Designer : Yes .", + "User Interface : But does it {disfmarker} uh I then should n just use uh i instead of the stick , uh like many cell phones , just a round m well ,", + "Project Manager : Yeah , draw draw it on the board .", + "User Interface : should we just use a {disfmarker} Um it's already uh {disfmarker} oh , we have a blank . Oh .", + "Industrial Designer : yeah , something like that . Oh", + "User Interface : It's just an easy uh way of of a round button what {disfmarker} which can be pushed in four directions . Instead of a stick .", + "Industrial Designer : It's not really a stick , but {disfmarker} Yes . Yes .", + "User Interface : A stick is v vulnerab vulnerable when it's falling down", + "Project Manager : Yeah , it can break down .", + "Industrial Designer : Hmm .", + "User Interface : or uh", + "Industrial Designer : Yes , yes .", + "User Interface : just a round uh button should be the trick , I think .", + "Marketing : Yeah .", + "Industrial Designer : And {disfmarker} Yes , and this also looks more fancy , I think .", + "User Interface : Yeah .", + "Industrial Designer : I think it it will attract uh more uh uh public , I think .", + "Marketing : A younger uh {disfmarker} Huh .", + "Industrial Designer : But you're the marketing man .", + "Marketing : And it's also quite easy to use , so it'll {disfmarker} it {disfmarker} uh attract younger people because well new , and it might attract older people because it's easy to use .", + "User Interface : Geez . Well , volume and something uh like that . {vocalsound}", + "Project Manager : Uh-huh . {vocalsound}", + "User Interface : The programme up and down . {vocalsound}", + "Industrial Designer : {vocalsound}", + "Marketing : {vocalsound}", + "Project Manager : Okay , yeah .", + "User Interface : And the vol yeah , the pen doesn't uh really does what I want .", + "Industrial Designer : Okay , that's good .", + "Project Manager : Okay , but w we still {vocalsound} we're still in the question of uh um uh putting in advanced options . Um Ruud just told us um the market is interested in some advanced uh new techniques . Um however , uh keeping it simple is is important for the costs and all all those kind of things . We need to find a balance between uh the advanced techniques and and the user-friendliness .", + "Industrial Designer : Mm-hmm .", + "User Interface : But I think our our next step to look at is just that . So I don't think it's {disfmarker} um we have something to do . Uh we can't discuss it right now , because n no one of us have {disfmarker} has the information to discuss about that , I think .", + "Project Manager : Um well , for {disfmarker} we do have to uh decide this this meeting . Yeah .", + "User Interface : Yes ?", + "Project Manager : We need to um have the uh the user function {disfmarker} uh the functions decided and um {vocalsound} uh our target audience .", + "User Interface : Mm-hmm .", + "Industrial Designer : {vocalsound} Okay .", + "User Interface : but teletext is so uh is just scrapped . 'Kay ,", + "Industrial Designer : Okay . Do do you want a list of functions ? Do you want an explicit list ? Uh which uh incorporates all function available on the device ?", + "Project Manager : Um well , I do not want a full uh {disfmarker} it's not necessary to to have a full list , but I want um the kind of functions , for example uh th the most important are volume and uh programme selecting .", + "Industrial Designer : Okay . Okay .", + "User Interface : The ten digits .", + "Industrial Designer : Mm-hmm .", + "Project Manager : Well , for example , that that's what we should think about . {gap} l how is the remote going to look ? Not not in the user interface , but {disfmarker}", + "User Interface : Oh , and just one function . The the the the programme to programme button , the switch to uh two channels , when you have uh something on channel four and something on channel six , just one button which which can uh change", + "Industrial Designer : Mm-hmm . Yes .", + "Project Manager : Yeah . A bit of a split mode .", + "Industrial Designer : Change .", + "Project Manager : Uh l like {disfmarker} Yeah .", + "User Interface : {disfmarker} yeah .", + "Industrial Designer : Yes , yes .", + "Project Manager : Dual channel watch .", + "Industrial Designer : Yes .", + "Project Manager : Okay , well um", + "User Interface : Yeah .", + "Project Manager : m maybe I should write that down . {vocalsound}", + "Industrial Designer : {vocalsound} Well {disfmarker} {vocalsound}", + "User Interface : {vocalsound}", + "Industrial Designer : you're the secretary . {vocalsound}", + "Project Manager : Uh Ruud , um what's your last name ?", + "Marketing : Mielsen .", + "Project Manager : Mielsen , because I I was writing it down in the last uh {disfmarker} Mielsen . Right . Um I put all the minutes I make into the shared folder . So if you want to have a look at it , you know where to find it . Um {disfmarker}", + "Industrial Designer : Mm okay ,", + "User Interface : Alright .", + "Industrial Designer : but make a s make a sub-folder for it , because it's starting to fill up already . {vocalsound}", + "Project Manager : Yeah , that's that's {disfmarker}", + "Marketing : Yeah .", + "Project Manager : if you want to do it , Sebastian . {vocalsound}", + "User Interface : {vocalsound} Our B_S_C_ uh W_ uh {disfmarker}", + "Industrial Designer : {vocalsound} Sure . {vocalsound} {gap} . {vocalsound}", + "Project Manager : Okay , um {disfmarker} {vocalsound} Okay , so so um {disfmarker} {vocalsound} uh {disfmarker}", + "User Interface : {vocalsound} {gap} {disfmarker}", + "Project Manager : Volume . Programme . Uh dual channel . Uh {disfmarker}", + "Industrial Designer : Yes , that's important .", + "Project Manager : And and do we want um the ten digits ?", + "User Interface : The ten digits ? Yeah , I believe so .", + "Industrial Designer : Well , are are you sure ?", + "Marketing : Well , if you want to go to channel ninety and you have th that button .", + "Industrial Designer : I'm not so sure .", + "User Interface : Yeah .", + "Industrial Designer : Well , that's complicated ,", + "Project Manager : Yeah .", + "Industrial Designer : but is that so relevant ? Because I don't think {disfmarker} but you should uh shou you should know that . If it were so .", + "User Interface : I wouldn't buy it personally . A remote control without the ten digits .", + "Industrial Designer : Okay ,", + "User Interface : Uh and I think the most {disfmarker}", + "Industrial Designer : I can imagine when", + "Project Manager : I agree actually . {vocalsound}", + "User Interface : Just elder elder people would would buy it ,", + "Industrial Designer : I can imagine when you're {disfmarker} when you have a satellite decoder and and you have , well , about six hundred channels , I can imagine you want this .", + "Marketing : Well {disfmarker}", + "User Interface : but {disfmarker}", + "Industrial Designer : But if you're uh a regular T_V_ user , and you just want uh to watch the the Dutch television networks , well , you can uh {disfmarker} {gap} {disfmarker} you can use uh about ten buttons . That's enough .", + "Project Manager : But we do have thirteen different Dutch channels .", + "Marketing : But {disfmarker}", + "User Interface : Yep . The older people only use five of them .", + "Industrial Designer : Well ,", + "Marketing : Yeah ,", + "Industrial Designer : but how how often do you watch all these channels ?", + "Marketing : and if if we {disfmarker} And if we are targeting at the younger audience , they will probably watch more channels than the older people .", + "Project Manager : Often .", + "Industrial Designer : No , you're probably right .", + "Marketing : So {disfmarker}", + "User Interface : Yeah .", + "Industrial Designer : Okay . But I think these uh ten uh buttons look a bit dull . Don't you think ?", + "Project Manager : Well , it depends on the on the on the looks , on the on the {disfmarker}", + "Industrial Designer : The design .", + "User Interface : On the design .", + "Industrial Designer : Okay . Well , y then there should be {disfmarker} should done {disfmarker} be done something specific with it .", + "Marketing : Well {disfmarker}", + "Project Manager : You c {vocalsound} you can d make them very fancy", + "Marketing : And {disfmarker}", + "Project Manager : by um {disfmarker} {vocalsound} I mean Nokia , they have ten digits on their phones and it still looks very fancy .", + "Industrial Designer : Mm-hmm .", + "Project Manager : So I'm I'm {disfmarker} I do not agree {disfmarker}", + "User Interface : Yeah .", + "Industrial Designer : Okay , so you can experiment by {disfmarker} uh with with shape or with size or with colour , that kind of thing .", + "Project Manager : Exactly , exactly .", + "Industrial Designer : Okay .", + "Marketing : And um there are some numbers about uh speech recognition here that uh younger people would like it . Uh it might be expensive and uh hard to implement , but it would be a solution uh for {disfmarker}", + "Project Manager : Okay , speech .", + "Industrial Designer : Well , maybe it can be combined with the find the remote control .", + "User Interface : Yeah .", + "Industrial Designer : So um when you add uh speech recognition to your remote control , uh it's very easy to change uh the channel . That's one thing .", + "Project Manager : Yeah .", + "Industrial Designer : And it's very easy uh to find your remote control .", + "Project Manager : To find {disfmarker} yeah .", + "Industrial Designer : So maybe that's a possibility , but I'm afraid it will be a bit costly .", + "Marketing : Yeah .", + "Project Manager : Uh {disfmarker} If if we would um drop the ten digits", + "Industrial Designer : But maybe when we uh {disfmarker}", + "Project Manager : but keep the programme and the volume ,", + "Industrial Designer : Mm-hmm .", + "Project Manager : because maybe people do not always want to use their voice , um {disfmarker}", + "Industrial Designer : Okay . Okay , okay .", + "Marketing : Especially elder people uh don't like voice recognition . So then we should implement such a but", + "Project Manager : Yeah . But we do focus on younger people . We d it it's a board uh decision .", + "Industrial Designer : Okay .", + "Marketing : Yes .", + "Industrial Designer : Well . I I think it should uh should work , it sh we should manage that .", + "User Interface : So", + "Project Manager : Okay .", + "User Interface : we have to i to make um a decision between the ten digits or the voice recognition .", + "Industrial Designer : Yes . Well , the voice recognition has the main adva has another advantage . It's mas it makes it very easy for us to implement the find uh find the remote control button {disfmarker} uh remote control function .", + "User Interface : Mm-hmm .", + "Project Manager : Okay .", + "Industrial Designer : So that's that's a big advantage , I think .", + "Project Manager : Okay , g good .", + "User Interface : {vocalsound}", + "Project Manager : Okay .", + "Industrial Designer : There's only one disadvantage uh by implementing this . Um the power saving power saving will be a bit more difficult . So we can expect that there will be a less longer life to the batteries ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "test", + "file_id": 11, + "turns": [ + 97, + 236 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "clip , remote control", + "speaker": "Project Manager" + }, + "summary": "Adding something to the remote control was considered so that sweaty hands would be not an issue. In response, the Project Manager suggested adding an attachable clip to the remote control.", + "title": "Project Manager's Suggestion for a Clip on the Remote Control", + "relevant_turns": [ + [ + 126, + 139 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "high", + "specificity": "normal", + "topic": "clip , remote control", + "speaker": "Project Manager" + }, + "summary": "Project Manager suggested adding a clip on the rmote control. Then it didn't make hands sweat lot.", + "title": "Project Manager's Suggestion for a Clip on the Remote Control", + "relevant_turns": [ + [ + 126, + 139 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "Telly , robust , water", + "speaker": "Marketing" + }, + "summary": "Marketing\u00b4s opinion was to have a telly screen on the device with the possibility to add a programming function. The other thing was about water resistant and good feel.", + "title": "Marketing's Suggestion to Remote Design", + "relevant_turns": [ + [ + 92, + 98 + ], + [ + 122, + 131 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "normal", + "topic": "Telly", + "speaker": "Marketing" + }, + "summary": "Marketing provided his opinion regarding the telly as the telly was already a screen, it would be less expensive to add a programming function with arrows up and down on the remote. Marketing recalled the control should be good tactile feel and water-resistant.", + "title": "Marketing's Suggestion to Remote Design", + "relevant_turns": [ + [ + 92, + 98 + ], + [ + 122, + 131 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "experience", + "speaker": "Project Manager" + }, + "summary": "Project Manager wanted the team to decide what they would like to reflect on their experiences with remote controls.", + "title": "Experience with Remote Control", + "relevant_turns": [ + 0 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "experience", + "speaker": "Marketing" + }, + "summary": "Project Manager mentioned experience with remote controls, and asked the group if they had initial ideas for how this convenient , practical , nice remote control should be designed or formatted or the buttons it should have.", + "title": "Experience with Remote Control", + "relevant_turns": [ + 0 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "house", + "speaker": "User Interface" + }, + "summary": "The User Interface Designer made a reference to some houses seen on celebrity cribs. All was so connected, the use of a master control with a screen was required.", + "title": "User Interface Designer's Reference to Connected Houses", + "relevant_turns": [ + 107 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "house", + "speaker": "User Interface" + }, + "summary": "The User Interface Designer referred some houses were so electronically connected, a master hand held control with a screen was needed.", + "title": "User Interface Designer's Reference to Connected Houses", + "relevant_turns": [ + 107 + ] + } + ], + "source": [ + "Project Manager : So f that's a fifty percent um uh . Um , I don't know what these mean because I didn't actually make the slide-show . Experience with remote control . So I guess we have to reflect on our experiences with remote controls to decide what um we would like to see in a convenient , practical , nice remote control . Um so do we have any initial ideas for uh how this remote control should be designed or formatted or the the buttons it should have .", + "Marketing : Um , I think one thing is that it should be easy to find", + "Industrial Designer : {vocalsound}", + "User Interface : I was thinking that too .", + "Marketing : bec yeah {vocalsound} bec", + "Project Manager : Yeah .", + "User Interface : I think we should design something that has like a {disfmarker} so you can {disfmarker} like somehow like you {disfmarker} I mean you always know where your T_V_ is , so just have a call button ,", + "Industrial Designer : {vocalsound}", + "User Interface : I've always wanted that ,", + "Project Manager : Yeah .", + "User Interface : so like {vocalsound} you can push a button on your T_V_ {disfmarker}", + "Marketing : Yeah , yeah yeah yeah yeah .", + "Project Manager : I mean you have it for the portable phone , so why not {disfmarker} yeah .", + "User Interface : Yeah , yeah yeah yeah , so you should have a call button on your television to be able to find your remote control .", + "Marketing : Yeah . And even I think a little light . Um or even a {disfmarker} maybe a vib a vibrating thing . I dunno but someth because it's usually under the sofa .", + "Industrial Designer : {vocalsound}", + "User Interface : Yeah . Yeah .", + "Marketing : In which case you're going to be l but if it has a sort of signal which isn't any sound {disfmarker}", + "User Interface : Yeah .", + "Marketing : I don't know if it's expensive maybe to {disfmarker}", + "User Interface : I don't {disfmarker} yeah I mean it {disfmarker} but like I mean {disfmarker}", + "Marketing : Maybe call is enough . But yeah .", + "User Interface : just I mean like your phone even just has so {disfmarker} like it can vibrate , it can light up and make noise and I dunno {vocalsound}", + "Marketing : Yeah yeah yeah . Yeah .", + "Project Manager : What if it had something like um just like a magnet on the back of it and you could {disfmarker} I mean j just to have some place to put it besides like a base . You know like a portable phone has a base ,", + "User Interface : Yeah . Yeah , or if it had a {disfmarker} yeah .", + "Project Manager : like just to have a home for it .", + "Industrial Designer : {vocalsound}", + "Marketing : Yeah yeah yeah yeah .", + "User Interface : Yeah ,", + "Project Manager : {vocalsound} 'Cause people just stick it on top of their T_V_ , but the point of having a remote is not to have to walk over to the T_V_ , so {disfmarker}", + "User Interface : I mean {disfmarker}", + "Industrial Designer : {vocalsound} Well that's why it's always in the couch .", + "User Interface : Yeah .", + "Project Manager : Yeah {vocalsound} .", + "User Interface : Yeah , in in the couch {vocalsound} .", + "Marketing : {vocalsound}", + "Project Manager : {gap}", + "User Interface : I dunno , it seems like though that that would be hard , 'cause you not you're not gonna be lazy anyway and {disfmarker}", + "Project Manager : Yeah . Maybe we should design couches that have the remote control in the side arm . {vocalsound}", + "Industrial Designer : {vocalsound} {vocalsound}", + "User Interface : Yeah so we {disfmarker} {vocalsound} the project is now couches and remote controls .", + "Marketing : {vocalsound} But even just a thing to attach it to the w you know if you had a thing , a pretty object attached to the wall . But that would really make it more expensive .", + "User Interface : Yeah .", + "Marketing : But it's only a plastic thing , r really , the thing on the wall .", + "Project Manager : Yeah .", + "User Interface : Yeah .", + "Marketing : Something like that .", + "Project Manager : Do you think it needs to be bigger to not lose , or does that not factor in ?", + "Marketing : And the other thing is {disfmarker}", + "User Interface : Bigger .", + "Marketing : Not {disfmarker} well it needs to be sort of {disfmarker}", + "Project Manager : Like Hand hand held size , yeah .", + "User Interface : Hand-sized .", + "Marketing : Yeah . I don't think you need a {disfmarker}", + "Project Manager : Not not huge , but {vocalsound}", + "Industrial Designer : {vocalsound}", + "Marketing : But definitely not {disfmarker} well I don't know .", + "User Interface : It can't be that hard to put some kind of a noise on it .", + "Marketing : No , it can't be , uh-uh .", + "Industrial Designer : No it really wouldn't be .", + "Project Manager : Huh .", + "User Interface : Or like or like a light thing . You know . I dunno {vocalsound}", + "Industrial Designer : {vocalsound}", + "Marketing : {vocalsound} Like spaceship .", + "User Interface : . Yeah {vocalsound} . Or make it mobile so it runs around and comes come find you yeah {vocalsound} .", + "Industrial Designer : {vocalsound}", + "Project Manager : {vocalsound}", + "Industrial Designer : {vocalsound}", + "User Interface : That would be really {disfmarker} I'm sure we could do that for twenty five Euros a pop .", + "Project Manager : Little homing device . {vocalsound} {vocalsound} Um .", + "Industrial Designer : {vocalsound}", + "User Interface : {vocalsound} Yeah {vocalsound} . Uh .", + "Project Manager : Okay . So what do we think this remote control should {disfmarker} Five minutes .", + "Marketing : Oh dear .", + "Project Manager : Till the meeting {disfmarker} oh right . This is what we have left . Um , oh we just {gap}", + "User Interface : I also think though that it shouldn't have too many buttons ,", + "Industrial Designer : Yeah , I agree .", + "User Interface : 'cause I hate that when they have too many buttons and {disfmarker}", + "Project Manager : Yeah .", + "Industrial Designer : {vocalsound} B_ button and the F_ button , they don't do anything .", + "Marketing : Yeah , yeah yeah .", + "User Interface : I mean I know it has to have enough functions but like , I don't know you , just have like eight thousand buttons and you're like , no , you never use half of them . So .", + "Project Manager : You {disfmarker} what if um may be a little fancy but what if it had like a little screen , so it has less buttons but it still has all the functions . Like the way a mobile phone does .", + "User Interface : That would be cool .", + "Marketing : Yeah .", + "User Interface : Yeah . I mean it just seems like {disfmarker}", + "Project Manager : So you could like um {disfmarker} like if you have I dunno if you have satellite if you have a hundred channels , you can {disfmarker} the way you do it on your radio is that you uh {disfmarker}", + "User Interface : yeah .", + "Project Manager : what do you call it {disfmarker}", + "Marketing : Select . Uh .", + "Project Manager : s y yeah but you can programme , so you can programme like your favourite channels , so like if you had a s", + "Marketing : But , would you have the screen on the thing , or would you have it on the telly transmitting the screen .", + "Project Manager : That's something we could decide . Mm .", + "Marketing : Because {disfmarker}", + "User Interface : I guess they would go together somehow ? I dunno .", + "Marketing : Because , I don't know if it's {disfmarker} {vocalsound} I think it's e expensive , if you have {disfmarker} if you use the telly screen , 'cause the telly's already a screen , then you can pro sort of have a programming function , really easy sort of arrow up and down , on the remote ,", + "Project Manager : Yeah . Yeah .", + "Marketing : and then use the telly as a screen .", + "Project Manager : Right .", + "Marketing : But um {disfmarker}", + "User Interface : I'm thinking kind of {disfmarker}", + "Marketing : But yeah for sure . Something like not {disfmarker} it's not on the button but it's telling you what to do ,", + "Project Manager : Yeah .", + "Marketing : is that what you mean ?", + "Project Manager : Yeah .", + "Marketing : Right . Mm .", + "User Interface : Or like you h you see those you know people {disfmarker} I'm thinking of like celebrity cribs kind of things when like they have all those {disfmarker} these things that at their house you know {disfmarker} their their entire house is so electronic , and they have like this one master control that {disfmarker} and it's like a hand held like {disfmarker} turns on everything sort of control and it has like a screen and like {disfmarker} so I think it should be possible to have some kind of a screen , I don't know if {disfmarker} it must be {disfmarker} it would probably {disfmarker}", + "Marketing : Yeah .", + "User Interface : must be ex too expensive though t like I dunno .", + "Project Manager : Mm .", + "Marketing : But like mobile phones have screens and they're cheap .", + "User Interface : Yeah , yeah . Yeah that's true .", + "Project Manager : Yeah . I mean , we have to remember our budget is twelve point {disfmarker} twelve fifty for {disfmarker} to actually make the device .", + "Marketing : Yeah .", + "User Interface : Mm .", + "Project Manager : Um but it's something to think about , yeah .", + "User Interface : Well , I guess we have to get to that later , yeah .", + "Project Manager : I mean we'll have to see how much that would be .", + "User Interface : {vocalsound}", + "Marketing : Or some {disfmarker} it i we can find out probably on the internet {vocalsound} how much it's {disfmarker}", + "Project Manager : Yeah .", + "Marketing : Um . Yeah , and the other thing you said that thing about robust and water um {disfmarker}", + "Industrial Designer : {vocalsound}", + "Marketing : What was the word ?", + "User Interface : Furry .", + "Marketing : Water resistant .", + "Project Manager : Oh I was just {disfmarker} {vocalsound}", + "User Interface : {vocalsound}", + "Marketing : No but it's {disfmarker} I thought , ah , spot on .", + "Industrial Designer : {vocalsound}", + "Marketing : Good feel , tact tactile , good tactile feel ,", + "Project Manager : Yeah .", + "Marketing : maybe something didn doesn't make your hands sweat lot .", + "User Interface : Yeah . Mm , mm .", + "Marketing : That's quite annoying .", + "Project Manager : Maybe um just like a simple thing to have a clip on it , like so you can clip it to your {disfmarker}", + "User Interface : Yeah .", + "Project Manager : like that's another {disfmarker}", + "Marketing : Yeah , clip . Ooh {vocalsound} . Um ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "test", + "file_id": 2, + "turns": [ + 48, + 389 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "evaluation criteria", + "speaker": "" + }, + "summary": "They discussed the most important criteria maybe spongy o fancy look and feel.", + "title": "Most Important Evaluation Criteria", + "relevant_turns": [ + [ + 8, + 14 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "high", + "topic": "evaluation criteria", + "speaker": "" + }, + "summary": "Marketing stated that these were the most important criteria, said it should be spongy. Marketing also spoke about the fancy look and feel. User Interface believed it was fancy.", + "title": "Marketing Thought's on Some Evaluation Criteria", + "relevant_turns": [ + [ + 8, + 14 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "easy to use", + "speaker": "" + }, + "summary": "Marketing asked if it was easy to use. Industrial designer answered there were two parts in this remote control. What you see here was the basic part, everybody could use it, so it was easy to use. Industrial Designer thought it was easy to use for both types of users.", + "title": "Question on Ease of Using the Remote Control", + "relevant_turns": [ + [ + 176, + 186 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "easy to use", + "speaker": "" + }, + "summary": "Industrial Designer answered Marketing question, thought it was easy to use for both types of users.", + "title": "Ease of Use of the Remote Control", + "relevant_turns": [ + [ + 176, + 186 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "competitive", + "speaker": "" + }, + "summary": "Project Manager asked a number for type of market. Marketing geve one because voice recognition would make users add anything wanted. Industrial Designer thought they had succeeded.", + "title": "Market Type for the Remote Control", + "relevant_turns": [ + [ + 332, + 336 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "fully", + "specificity": "high", + "topic": "competitive", + "speaker": "" + }, + "summary": "Project Manager; give it a number; type of market; one; User Interface; two; Industrial Designer; one; succeed in developing a product; but not for this kind of market, and not for this kind of price; Marketing; one; voice recognition.", + "title": "Thoughts on Successfulness of the Remote Control", + "relevant_turns": [ + [ + 332, + 336 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "advanced", + "speaker": "Marketing , Industrial Designer" + }, + "summary": "Marketing said the advanced functions were probably a bit harder. Industrial Designer said it would be easy for an advanced user.", + "title": "Advanced Users", + "relevant_turns": [ + [ + 191, + 197 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "high", + "topic": "advanced", + "speaker": "Marketing , Industrial Designer" + }, + "summary": "Marketing pointed out the advanced functions were probably a bit harder. Industrial Designer said the advanced users would find the voice recognition function easy to use because they were already an advanced users.", + "title": "Advanced Users", + "relevant_turns": [ + [ + 191, + 197 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "fancy look", + "speaker": "Marketing , User Interface , Industrial Designer" + }, + "summary": "Marketing shared the fashion guys' opinion. User Interface asked if it was fancy. Industrial Designer believed it was fancy. But marketing said apparently they shouldn't evaluate yet.", + "title": "Fashion Guys Statement", + "relevant_turns": [ + [ + 13, + 25 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "fancy look", + "speaker": "" + }, + "summary": "They talked about fashion guys' statements, and two of them believed that it was fancy look and feel.", + "title": "Look and Feel of the Remote Control", + "relevant_turns": [ + [ + 13, + 25 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "voice recognition feature", + "speaker": "" + }, + "summary": "The voice recognition is hard for elderly to learn, but advanced user would find voice recognition function easy. Users could add a lot of functionality by using the voice recognition mode.", + "title": "Ease of Using Voice Recognition", + "relevant_turns": [ + 181, + 395, + [ + 307, + 311 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "high", + "topic": "voice recognition feature", + "speaker": "" + }, + "summary": "Voice recognition; hard to learn; for the elderly; guess an advanced user will find the voice recognition function easy to use; much functionality.", + "title": "Thoughts on Voice Recognition Function Usage", + "relevant_turns": [ + 181, + 395, + [ + 307, + 311 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "one", + "speaker": "Project Manager , Industrial Designer , Marketing" + }, + "summary": "Project Manager gave the market a number. Industrial designer gave it a one. Marketing thought of a one because of the voice recognition.", + "title": "Advantage of the Voice Recognition", + "relevant_turns": [ + [ + 332, + 335 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "fully", + "specificity": "high", + "topic": "one", + "speaker": "Project Manager , Industrial Designer , Marketing" + }, + "summary": "Project Manager; For this type of market, it's a one. Industrial Designer; give it a one; Marketing; I think a one.", + "title": "Position in this Market", + "relevant_turns": [ + [ + 332, + 335 + ] + ] + } + ], + "source": [ + "Project Manager : The basic {disfmarker} okay . Okay . Um you thought of some evaluation crit criteria ?", + "Marketing : Yes .", + "Project Manager : Okay .", + "Marketing : Uh my name is not name", + "Project Manager : {vocalsound} You are nameless . {vocalsound}", + "Industrial Designer : {vocalsound}", + "Marketing : but {disfmarker}", + "User Interface : {vocalsound}", + "Marketing : Uh well , I used the {gap} {disfmarker} the uh {gap} documents . And these uh were the most important criteria .", + "Industrial Designer : {vocalsound} Is it spongy ? {vocalsound}", + "Marketing : It should be . {gap} {disfmarker} {vocalsound} yeah ,", + "Project Manager : {vocalsound}", + "User Interface : {vocalsound}", + "Marketing : that's uh how the fashion guys uh state it . Fancy look and feel . So {disfmarker}", + "User Interface : So just walk through it step by step . I mean , is it fancy , everything {disfmarker} I believe uh I believe it's fancy . {vocalsound}", + "Marketing : Uh well appar", + "Industrial Designer : I believe it's fancy too .", + "Marketing : Yeah , but apparently uh we shouldn't evaluate yet .", + "Project Manager : No .", + "User Interface : Oh , sorry .", + "Marketing : So {disfmarker}", + "Project Manager : Okay , so", + "Industrial Designer : Okay .", + "Project Manager : this {disfmarker} these are the cr uh the criteria .", + "Marketing : Yeah , I think these are the most important criteria .", + "Project Manager : Okay , well {disfmarker}", + "Marketing : So uh", + "Project Manager : the then we'll switch to my presentation . Um {disfmarker}", + "Marketing : that's about it .", + "Industrial Designer : Is it fancy ? {vocalsound}", + "Project Manager : I d it is it is {disfmarker} {vocalsound}", + "Marketing : Uh {disfmarker}", + "Industrial Designer : {vocalsound}", + "Marketing : Yay . Is it ? Is it fancy ?", + "Project Manager : Yeah , I think so .", + "User Interface : Um the yellow rubber , I think so .", + "Industrial Designer : I think so .", + "Project Manager : {vocalsound} You like the rubber , uh Roo . {vocalsound}", + "User Interface : {vocalsound} I'm into it . {vocalsound}", + "Marketing : {vocalsound}", + "Industrial Designer : {vocalsound}", + "Marketing : So uh one ?", + "Project Manager : Yeah .", + "Industrial Designer : But it's not that fancy .", + "Project Manager : No , I'll I'll I'll give it a two .", + "Industrial Designer : I mean I think uh {disfmarker} I think it would have been more fancy if we used the titanium housing {disfmarker} the casing . It would be even more {disfmarker}", + "Project Manager : You like tita {vocalsound}", + "User Interface : {vocalsound}", + "Industrial Designer : oh , you really like titanium . I'm I'm into it . {vocalsound}", + "Marketing : {vocalsound}", + "Project Manager : That's a flavour as well .", + "User Interface : {vocalsound}", + "Industrial Designer : It has flavour . Yes , that's right . {vocalsound} You should taste it . {vocalsound}", + "Project Manager : {vocalsound} Right . Um {disfmarker}", + "User Interface : {vocalsound}", + "Project Manager : Yeah , I know ,", + "Marketing : Is it uh {disfmarker}", + "Project Manager : but but it {disfmarker} but that's fancy in the way um {disfmarker} {vocalsound} I mean fancy has has a lot of {disfmarker}", + "Industrial Designer : It has to do with fashion , I guess .", + "Project Manager : Yeah .", + "User Interface : It's trendy trendy , fun {disfmarker} {vocalsound}", + "Industrial Designer : So do {disfmarker}", + "Marketing : And w", + "User Interface : yeah .", + "Marketing : yeah , w what they want {disfmarker} wanted was uh colours and soft materials .", + "Project Manager : Yeah .", + "Marketing : So in that way {disfmarker} It {disfmarker} it's fancy .", + "Project Manager : It applies . It {disfmarker} yeah .", + "User Interface : Well , just {vocalsound} give it a two .", + "Industrial Designer : Okay .", + "Project Manager : Yeah .", + "Industrial Designer : Yes .", + "User Interface : It's not the ultimate uh fancy two , but {disfmarker}", + "Industrial Designer : I think I th I think it would have been {disfmarker} I would have think {disfmarker} uh it could have been more fancy by using the double-curved case . It would have been even more fancy , but we decided not to , because if we use a double-curved case , we could not use solar .", + "User Interface : Yeah , but that's sti that's uh {disfmarker}", + "Industrial Designer : So {disfmarker}", + "User Interface : {vocalsound} Looking at the user uh needs , we only uh don't {disfmarker} we don't have the double-curved case . We w we do have uh the rubber , we do have the colours . That's two out of three . So I believe uh we are close uh to two .", + "Industrial Designer : Yes .", + "Project Manager : Yeah , I I agree .", + "Industrial Designer : Yes , I agree too . It's okay . We did {gap} {disfmarker} yes , we did good .", + "Marketing : Okay , and uh was it innovative ?", + "User Interface : {vocalsound}", + "Project Manager : Well ,", + "Marketing : {vocalsound}", + "Project Manager : with the voice recognition feature and uh {disfmarker}", + "User Interface : But that's not in it . Ov or can we {disfmarker}", + "Marketing : Yep .", + "Project Manager : No , we are evaluating this this uh design now . This prototype .", + "Industrial Designer : Well , let's let's {disfmarker} this product .", + "User Interface : Okay .", + "Industrial Designer : So I I I think it is . I think it's innovative .", + "Project Manager : Yeah .", + "User Interface : {vocalsound} And the scroll uh wheel . The solar {disfmarker} not many remotes have the solar , I think .", + "Industrial Designer : No . It could have been a little bit more innovative u by using the kinetic uh energy source , but it's it's way too {disfmarker}", + "Marketing : Yeah , and uh {disfmarker}", + "Project Manager : That would have been a thrill .", + "Industrial Designer : yes , but {disfmarker}", + "Marketing : So uh also a uh two ?", + "Industrial Designer : I think uh it's a two .", + "Project Manager : Yep .", + "Marketing : Is it easy to use ?", + "Project Manager : I'm not sure . {vocalsound} I'm not sure .", + "User Interface : Yeah .", + "Industrial Designer : {vocalsound}", + "Marketing : {vocalsound}", + "User Interface : Well yeah , the voice recognition of course is hard to learn , I think . Well , hard {disfmarker} it's not for the for the e for the elderly . They won't use it .", + "Industrial Designer : {vocalsound} Well , but there are two parts in this remote control . What you see here is is the basic part . Everybody can use it , so that's easy to use .", + "Project Manager : Yeah .", + "Industrial Designer : That's for a novice user . When you have a more advanced , elaborate user , well , such a user really would like to explore all these additional functions . So in that in that way it is advanced ,", + "Project Manager : Yeah .", + "Industrial Designer : and I think it's easy to use for for both uh types of users .", + "User Interface : I think {disfmarker} I think a three .", + "Industrial Designer : So uh {disfmarker} It's maybe {disfmarker} it's not very uh easy for {disfmarker}", + "User Interface : {vocalsound} Wouldn't give it more .", + "Project Manager : Uh I'm doubting {disfmarker} doubting as well . Um {disfmarker}", + "Marketing : Well the p the most important function is easy to use . The the zapping , channel switching , volume . But the more advanced functions are probably a bit harder .", + "Project Manager : Okay . Uh two or three ? Three ? Wha wh what would be your guess ? I mean ease of use um does not only apply to the most basic functions .", + "Industrial Designer : Okay .", + "Project Manager : It's the uh it's it's overall . Is the device easy to use ?", + "Industrial Designer : Yeah , that's right . You're right in that , but I {gap} {disfmarker} I guess uh an advanced user will will find the voice recognition function easy to use ,", + "Project Manager : Yeah .", + "Industrial Designer : because he is already {disfmarker} he or she is already an advanced user .", + "Project Manager : Yeah .", + "Industrial Designer : So {disfmarker}", + "Project Manager : Um {disfmarker} Okay .", + "Industrial Designer : After all , I think {disfmarker} personally I would give a two . But {disfmarker}", + "Project Manager : Uh Roo , a three ?", + "User Interface : Yep .", + "Project Manager : Ruud ?", + "Marketing : Good question . Uh I'll go uh for the two .", + "Project Manager : Okay . {vocalsound}", + "Marketing : {vocalsound}", + "User Interface : {vocalsound}", + "Industrial Designer : So , it's two , two and three . Two threes . So that's ten .", + "Project Manager : So I could make it e easy ?", + "User Interface : If you make it a four it will be three in general .", + "Industrial Designer : So that's w No , two and a half .", + "User Interface : If he makes it a four . Not a three .", + "Industrial Designer : Six and four . Six and four is ten . Divided by four is two and a half . So {disfmarker}", + "User Interface : Darn . Nee .", + "Industrial Designer : Yes . {vocalsound}", + "Marketing : Hmm ? Huh ?", + "Project Manager : Roo . {vocalsound}", + "User Interface : A seven , a three {disfmarker} {vocalsound} No .", + "Marketing : Yeah . I yeah {gap} .", + "User Interface : A four and a three together .", + "Industrial Designer : {vocalsound} Four ?", + "User Interface : Yeah , you have a two , he has a two . Three ?", + "Marketing : Yeah ,", + "Industrial Designer : Two ?", + "Marketing : two , two , three {disfmarker}", + "Project Manager : No ,", + "User Interface : And a three ?", + "Project Manager : I haven't said anything yet .", + "User Interface : Nee . I know .", + "Marketing : No . {vocalsound}", + "Project Manager : Okay , but if I would say a three , then it's six , and four is ten . Divided by four is two point five .", + "Industrial Designer : Divided by four .", + "User Interface : Yes . So if you want to have the conclusion as a three {disfmarker} three . Then you would make a four . If you fill out a four {disfmarker} {vocalsound} {vocalsound}", + "Project Manager : But I'm filling in a three .", + "Industrial Designer : That's not even {disfmarker}", + "Project Manager : Does it {disfmarker} will {disfmarker} so it will be a two point five .", + "Marketing : {vocalsound}", + "Industrial Designer : But that's not possible to fill in ,", + "Project Manager : Yes , it is .", + "Industrial Designer : so we have to round it . {vocalsound}", + "Marketing : {vocalsound} Is it easy to find ? {vocalsound}", + "Project Manager : {vocalsound} I have a veto . {vocalsound} Exactly . It's not about the content , it's about {disfmarker} okay , um is it easy to f Yeah , definitely .", + "User Interface : Yeah ,", + "Industrial Designer : Yes .", + "User Interface : we haven't re uh re uh really worked it out , but you c you can you can just say find and he repeats find .", + "Industrial Designer : It it most definitely is {disfmarker} it's very easy .", + "Project Manager : Yeah , or beeps or {disfmarker} yeah .", + "User Interface : Yeah , but that's the that's the the basic idea of the the speaker uh {disfmarker}", + "Industrial Designer : Yes . Maybe {disfmarker} Uh I I think I think {disfmarker}", + "Project Manager : I'm here , I'm here . {vocalsound}", + "Industrial Designer : something like that . Maybe you have to uh programme it once , so to that l respond to uh a certain word or a certain sentence , something like where are you , and then it will sing I'm here . So something like that .", + "Project Manager : Yeah . Yeah .", + "User Interface : But even without it {disfmarker}", + "Project Manager : Yeah .", + "Marketing : {vocalsound}", + "Project Manager : Well , I uh {disfmarker}", + "Industrial Designer : So , I th", + "Project Manager : we should not uh stay too long on this subject uh because of the time , but I personally give it a one .", + "User Interface : Yeah .", + "Project Manager : Um Sebastian ?", + "Industrial Designer : {vocalsound} Yeah , me too .", + "User Interface : Me too .", + "Marketing : Yeah , I agree .", + "Project Manager : Right , well . The feel of the remote control is spongy . Well , uh", + "Marketing : {vocalsound}", + "Project Manager : it can't be more spongy . So {disfmarker} {vocalsound}", + "Industrial Designer : Well , it can be . There are cases um in which the outside casing is {disfmarker} um can be {disfmarker} uh how d how do you prono is is moldable .", + "User Interface : Was it one of our options ?", + "Industrial Designer : No , it's not one of our option ,", + "Marketing : No . Uh", + "Project Manager : No okay , but but", + "User Interface : So , in the in {disfmarker}", + "Industrial Designer : but when you look in the market , when you look {disfmarker}", + "Marketing : this this was a most spongy option . {vocalsound}", + "Project Manager : for the options given , it's the most spongy one .", + "Industrial Designer : Uh yes ,", + "User Interface : Yeah .", + "Industrial Designer : but that's not that's not uh what they are talking about , I think . Because we compare all these uh characteristics {disfmarker} characteristics with uh market {disfmarker} uh with with the real market .", + "Project Manager : Yeah . Yeah .", + "Industrial Designer : So there are uh remote controls out there which are a lot more spongy . They're out there . {vocalsound}", + "Project Manager : {vocalsound} They're out there . {vocalsound}", + "User Interface : {vocalsound} But I think in this case in this case we've done the best we could .", + "Marketing : {vocalsound}", + "Project Manager : Yeah .", + "Industrial Designer : Yes , but it's not good enough ,", + "Project Manager : {vocalsound} I'll give it a one .", + "Industrial Designer : so it's a two .", + "User Interface : {vocalsound} {vocalsound} I wan I'll take one .", + "Industrial Designer : You take one ? What do you give it ?", + "Marketing : Well yeah , it depends , 'cause it's the most spongy we could {disfmarker}", + "Project Manager : Yeah , I know , but you have to name a fig uh a number . {vocalsound}", + "Marketing : but {disfmarker} yeah .", + "Project Manager : Because we need to go on {disfmarker} in {disfmarker} for the time .", + "Marketing : Well , if I give it a one there'll be one hell of a calculation .", + "User Interface : It will be a one . {vocalsound}", + "Marketing : So I'll just give it a two and make this a one point five .", + "Industrial Designer : No no no . Uh I'll I'll change it , I'll make it m my my mark will be a four . {vocalsound}", + "Project Manager : {vocalsound} You are {disfmarker}", + "User Interface : {vocalsound}", + "Marketing : {vocalsound}", + "Project Manager : okay .", + "User Interface : {vocalsound}", + "Project Manager : The remote control offers enough features .", + "User Interface : {vocalsound}", + "Project Manager : Well , Ruud , what what do you think about it ?", + "Marketing : Well , the basic layout doesn't offem {disfmarker} offer much , but the voice recognition could add a lot . So {disfmarker}", + "Industrial Designer : {vocalsound} Basically it's it's completely programmable .", + "Marketing : Yeah , depends .", + "Project Manager : Yeah .", + "Industrial Designer : You can add very m much functionality by uh using the voice recognition mode .", + "Project Manager : Yeah , I know .", + "Industrial Designer : So it's quite advanced .", + "Project Manager : What what we didn't talk about is um uh {disfmarker}", + "User Interface : Yeah , but {vocalsound} it ha doesn't has the digits . I believe it's {disfmarker} If you uh ask yourself it offers enough features , I don't I don't think it is {disfmarker} it has all the features um a normal remote has .", + "Project Manager : I think it has .", + "Marketing : Uh depends on what you uh implement in the speech feat", + "Project Manager : Yeah . Bec because you can um {disfmarker} we didn't talk about it , but you do have uh remote controls that are able to adapt another signal . So ,", + "Industrial Designer : Yes .", + "Project Manager : you place a a regular uh remote control in front of the other one , hit the one or the two or the three , whatever , and it r records the uh the um {gap} {disfmarker} the the signals .", + "Industrial Designer : Has uh the signals sent to it .", + "User Interface : Yeah .", + "Marketing : Signal .", + "Project Manager : So you could uh uh uh enter any comment you like , as long it's able to {disfmarker} as long as our device is able to reproduce the infrared signal . So I think th this uh this is uh a a remote control with a very high level of features .", + "Industrial Designer : Absolutely .", + "Project Manager : Although there are i a few buttons , but the inside is is quite uh advanced .", + "Industrial Designer : Yes . But that {disfmarker} that's its power , I guess , because uh a regular programmable uh remote control contains , well , uh really a lot of buttons . At at least uh forty buttons .", + "Project Manager : Yeah . Yeah .", + "Industrial Designer : So it's it's quite s complicated to get uh to get used to . And this is quite s simple .", + "Project Manager : Yep .", + "Industrial Designer : You can use your voice to to programme it . It's {disfmarker}", + "Project Manager : Yeah . Okay , um let's give it a number . I'll give it uh a one . For for the {disfmarker} for this t uh type of market , I think it's a one .", + "User Interface : I'll give a two .", + "Industrial Designer : {vocalsound} Yeah , I'll give it a one .", + "Marketing : Um I think think a one , 'cause {gap} v with a voice recognition you could add anything you want , so that's like um {disfmarker}", + "Industrial Designer : Yes . I I've {disfmarker} I think we've uh succe succeed in in developing a product that's actually quite good , but not for this kind of market , and not for this kind of price .", + "User Interface : {vocalsound} {vocalsound}", + "Project Manager : Yeah .", + "Industrial Designer : So {disfmarker}", + "Project Manager : So high quality , low acceptance .", + "Industrial Designer : Hmm ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 66, + "turns": [ + 2, + 108 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "Industrial Designer 's desire , design", + "speaker": "" + }, + "summary": "Industrial Designer's desire was that the control remote design would be very handy, easy to use, and was available in various colors, with buttons used easily. Perhaps of soft-touch, like touch screen buttons, and they said that they made several designs.", + "title": "Industrial Designer's Desire", + "relevant_turns": [ + 54, + 56, + 58 + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "high", + "specificity": "high", + "topic": "Industrial Designer 's desire , design", + "speaker": "" + }, + "summary": "Industrial Designer's desire was that the control remote design would be very handy, easy to use, and was available in various colors, with buttons used easily, maybe of soft touch, like touch screen buttons because the rubber buttons could be slightly damaged, so the numbers on the buttons were not possible to read anymore. They said that they made several designs.", + "title": "Industrial Designer's Desire", + "relevant_turns": [ + 54, + 56, + 58 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "Marketing think , functional requirements", + "speaker": "Marketing" + }, + "summary": "Marketing thought that could be a bigger control, with little and simple buttons, had a low power usage, and an LCD screen.", + "title": "Marketing's Functional Requirements", + "relevant_turns": [ + 87, + 92 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "Marketing think , functional requirements", + "speaker": "Marketing" + }, + "summary": "Marketing thought that could be a bigger control because it was found more easily, with little and simple buttons, should have a low power usage because seventy-five percent of the users only zap one time an hour, so the power usage was also one time an hour, or so, with high power usage, they would use a lot of batteries. then said that could have an LCD screen because it had fewer buttons.", + "title": "Marketing's Functional Requirements", + "relevant_turns": [ + 87, + 92 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "younger people", + "speaker": "Marketing" + }, + "summary": "Marketing said that the younger people were more interested for features like LCD screens , speech recognition etcetera and they were more critical about the features because they used the remote control more often and were more technical savvy than the older people but older people spent more money, and easily, so they were not focused on the younger people.", + "title": "Marketing Study of Younger People Preferents", + "relevant_turns": [ + 79, + 96, + 99 + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "younger people", + "speaker": "Marketing" + }, + "summary": "Marketing said that younger people were more critical than older people but older people spent more money easily, so they were not focused on younger people.", + "title": "Marketing Study of Younger People Preferents", + "relevant_turns": [ + 79, + 96, + 99 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "touch screen", + "speaker": "Marketing , Industrial Designer" + }, + "summary": "Industrial Designer said that the buttons could be soft touch like touch screen buttons, Later Marketing said that could have an LCD screen witch touch screen because it could have fewer buttons, but these should easily to be used by older people.", + "title": "Industrial Designer and Marketing Talking About the Touch Screen", + "relevant_turns": [ + 56, + [ + 92, + 94 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "fully", + "specificity": "high", + "topic": "touch screen", + "speaker": "Marketing , Industrial Designer" + }, + "summary": "Industrial Designer, easy to use buttons, touch screen buttons; rubber buttons, damaged. Marketing, LCD screen, easy, various options; the other options would be gone; don't see the buttons; elderly people, from forty five to for sixty five years don't use the LCD screen a lot, if, going to implement LCD screen, don't have to make it that hard to learn. Industrial Designer, LCD screen, touch screen.", + "title": "Industrial Designer and Marketing Talking About the Touch Screen", + "relevant_turns": [ + 56, + [ + 92, + 94 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "years", + "speaker": "Marketing" + }, + "summary": "Marketing said that younger people, from sixteen to forty-five years, were more interested in features like LCD screens, speech recognition, etcetera, while the elderly people, from forty-five years to sixty five years were not that much interested in these features and they didn't use some features a lot, like the LCD screen.", + "title": "Marketing Study of Younger and Older People", + "relevant_turns": [ + 79, + 92 + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "years", + "speaker": "Marketing" + }, + "summary": "Marketing said that 16-45 years old people were more critical of the features while 45-65 years old people weren't much interested in features and didn't use LCD screens.", + "title": "Marketing Study of Younger and Older People", + "relevant_turns": [ + 79, + 92 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "remote control functions", + "speaker": "Project Manager" + }, + "summary": "Project Manager explained that at this meeting, they were taking a look at new project requirements then they had to take a decision on the remote control functions and on that opportunity, they had some more time, forty minutes.", + "title": "Project Manager Talking About Remote Control Functions", + "relevant_turns": [ + [ + 9, + 19 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "remote control functions", + "speaker": "Project Manager" + }, + "summary": "Project Manager explained that they were taking a look at new project requirements and decided on the remote control functions.", + "title": "Project Manager Talking About Remote Control Functions", + "relevant_turns": [ + [ + 9, + 19 + ] + ] + } + ], + "source": [ + "User Interface : Yeah . {vocalsound}", + "Industrial Designer : {vocalsound} Send .", + "User Interface : Choose a number ? {vocalsound}", + "Industrial Designer : Submit . {vocalsound}", + "Marketing : {vocalsound} Yep yep yep yep .", + "Project Manager : All set ?", + "Industrial Designer : Mm . Yeah .", + "Marketing : Mm-hmm .", + "Project Manager : Good . Okay . Let's see what we can find here . Okay . A very warm welcome again to everyone .", + "User Interface : {vocalsound}", + "Project Manager : Um here we are already at our uh functional design meeting . Um and this is what we are going to do . The opening , which we are doing now , um and the special note , I'm project manager but on the meetings I'm also the secretary , which means I will make uh minutes as I did of the previous meeting .", + "Industrial Designer : {vocalsound}", + "Project Manager : And uh I also put these as fast as possible in the uh project folder , so you can see them and review what we have discussed . Um if I'm right , there are three presentations , I guess each one of you has prepared one ? Good .", + "User Interface : Yes .", + "Project Manager : And um we will also take a look at new project requirements , um if you haven't heard about them yet . And then of course we have to take a decision on the remote control functions and we have some more time , forty minutes . But I think we will need it . Um well I don't know who wants to go first with his presentation .", + "Industrial Designer : I'll go first . Okay . I'll go first yeah .", + "Marketing : Yeah .", + "Project Manager : You can go first , okay .", + "User Interface : Well .", + "Marketing : Well , shall I go first with the users ?", + "User Interface : Well {vocalsound}", + "Marketing : I think {disfmarker} well okay no problem . {vocalsound}", + "Project Manager : Is there an order ? I haven't {disfmarker}", + "User Interface : everybody already has his presentation ,", + "Marketing : Ja precies , ja precies , ja precies", + "User Interface : {vocalsound} so you can adjust it . {vocalsound}", + "Industrial Designer : So . Huh ? Okay , um {disfmarker}", + "Project Manager : And one question , uh your name Denni , is it with a", + "Marketing : E_I_E_ .", + "Project Manager : I_E_ {disfmarker} E_I_E_ , okay . Thank you .", + "User Interface : {vocalsound}", + "Industrial Designer : Okay , um I wanted to explain the working design of the remote control . It's possibly very handy if you want to uh design one of those . Um {vocalsound} well so it basically works uh as I uh uh r wrote down uh in this uh little uh summary . Uh when you press a button , {vocalsound} uh that's when you do pr for example when you uh want to turn up the volume , um a little connection is made uh the the rubber uh {vocalsound} button just presses on a", + "Project Manager : Sorry . {vocalsound}", + "Marketing : {gap}", + "User Interface : {vocalsound}", + "Industrial Designer : on a little print plate uh which uh makes uh uh {vocalsound} a connection that uh gives the chips , uh which is uh mounted beneath those uh that plastic of a rubber button . Uh senses that a connection has been made , and know and knows what button you pressed , becau uh for example the the volume up or volume down button . Um uh the the chip uh makes a Morse code uh like uh signal which uh then is si uh signalled {vocalsound} to uh several transistors which makes uh which sends the signal to a little let . You know what a let is ?", + "User Interface : Yeah .", + "Industrial Designer : Okay . {vocalsound} And that makes uh the the infra-red lights signal which is sent to the television set . Uh which has a sensor in it to uh sense uh the signal of the infra-red . That's basically uh how it works . Um the findings uh uh that I found uh searching up some uh detailed information about the remote controls , are that uh they are very easy to produce , uh it is pis uh it's possible to uh make them in mass production because it is as eas it is as easy as uh printing a page , uh just uh fibreglass plate um is b uh is uh covered with uh some uh coatings and uh uh {vocalsound} and chips .", + "User Interface : {vocalsound}", + "Industrial Designer : Uh and the technology's already available , we don't have to find out how remote controls uh have to work or uh how that how uh to make some chips that are possible to uh to to transmit those uh signals . Uh I made a little uh uh animation of {vocalsound} about how a tran our uh remote controller works .", + "User Interface : {vocalsound}", + "Marketing : {gap}", + "User Interface : Oh right .", + "Marketing : {vocalsound} Animation . {vocalsound}", + "User Interface : {vocalsound}", + "Industrial Designer : {vocalsound} we tel", + "User Interface : There is something turning .", + "Industrial Designer : There .", + "Project Manager : Yeah , it's a little bug it's in the in the smart board . {vocalsound}", + "Industrial Designer : {vocalsound} Okay . Uh well", + "User Interface : {vocalsound}", + "Industrial Designer : the sub-component , I suppose that you understand what a sub-component is , is f in this example it's the button . Uh when it is pressed down , um , the switch is ter is uh is switched on , so with uh the wire is sent to the to the chip in uh co-operation with the battery of course , because to make uh a a signal possible you have to have some sort of uh li uh a d ad uh electronic uh {disfmarker}", + "User Interface : {vocalsound}", + "Marketing : Infrared light .", + "Industrial Designer : Yes , uh , okay . Um w after it's being composed by the chip uh the signal uh is transported uh to the infra-red bulb , and from there it signals a Morse code-like signal to the to the b to the bulb in uh in the television set . Okay . S Uh I wrote down some personal preferences about uh the remote control . Of course it is very handy if the remote control is hand held , so you don't have to uh uh wind it up or something , or just is it's it's very light to uh to make uh to use it . Uh I personally uh pref prefer that uh it would be p uh come available in the various colours , and uh easy to use buttons . But I suppose that the one of the other team members uh uh thought of that uh too . {vocalsound}", + "User Interface : Yeah , I've got it there too . {vocalsound} {vocalsound}", + "Industrial Designer : And it is possible for several designs and um easy to use b uh sorry , easy to use buttons . Perhaps soft touch , uh touch screen uh buttons because uh the rubber buttons are always uh uh they uh slightly uh they can be slightly damaged ,", + "Marketing : {vocalsound}", + "Industrial Designer : uh so the numbers on the buttons are not possible uh to read anymore . And uh well as I said uh before th uh we can uh make several designs . {vocalsound}", + "User Interface : Yeah .", + "Industrial Designer : Okay , well , that's my contribution to this meeting , and uh", + "Marketing : To this meeting . {vocalsound}", + "Project Manager : Okay , thank you .", + "User Interface : {vocalsound}", + "Industrial Designer : two of these this meeting . So .", + "User Interface : Shall I go uh next ?", + "Project Manager : Yep .", + "User Interface : 'Kay .", + "Project Manager : Please .", + "User Interface : So .", + "Marketing : {vocalsound} Smoking .", + "User Interface : Well uh , my name's {gap} , and I looked at uh technical functions design of the remote . Uh I did this by uh looking at examples of other remote controls , of how they uh they look , and information from the web that I found . Um well what I found was that uh th the actual use of the remote control is to send messages to television set , how you uh d what you described uh just early . And this can be all sorts of medsa messages , turn it on , turn it off , uh change the channel , adjust volume , that kind of thing . Uh play video , teletext , but also t uh play C_D_ if you use it your C_D_ player the remote control will that one . There are some uh examples of remote controls . You can see they are very different . The one has got all the functions that you could possibly need and an lot of uh buttons etcetera . And the other is uh more user friendly , little with big buttons . And uh not n all the the the the stuff you can do with it , but uh the the essential stuff is there . Um {vocalsound} I guess you could better y you should look at a a user centred uh approach , because the customers have to use them and and if they don't think it's usable they won't uh buy it . A lot of buttons they may think from I don't need s as much as that . Uh , well perf personal preferences is is uh a simple remote , with uh the basic functions that you can need that you could use . But uh keep in mind the new functions of T_V_ what we discussed earlier , split screen and uh is that a function that you should have ? Because all the T_V_s will have them . Or because of only a few and isn't really necessary . And then uh make it {disfmarker} I would make so that you can could uh use it on more than one appliance . If you have one that uh uh does with the vi the the video , it could also work with uh with the stereo , because play is play and stop stop and that sort of thing . The shu c you could reuse the buttons so that you don't have to have a lot of buttons for uh anything . And it should be a user friendly , clear buttons , and not too much . And that is my presentation .", + "Project Manager : Okay , thank you .", + "Industrial Designer : Okay . {vocalsound}", + "Marketing : 'Kay . Check . {vocalsound}", + "Industrial Designer : {vocalsound}", + "User Interface : You must still have it open .", + "Marketing : Kijke {gap} 'Kay , so . {vocalsound} We're going to j discuss the functional requirements of the remote , that m that means that functions user n want to have on the remote control , or just {disfmarker} Yeah , and the users , actually .", + "Industrial Designer : {vocalsound}", + "Marketing : The methods I I prefer is we're going to look which section of the users we are going to focus a l on more . Are the younger people going to buy the remote control or the elderly people ? And then {disfmarker} tho that section we're going to focus and adjust the remote more to that section than the whole user section . Okay . Some data . Younger people , from sixteen to thir forty five um years are more interested in fj features like L_C_D_ screens , speech recognition e etcetera . And we possess about two third of the market from in that range of age . The elderly people , from forty five years to sixty five years are not that much interested in features , and we possess less than two third , that's two fifth , of the market share in that area . {gap} Goed so .", + "Project Manager : {vocalsound}", + "Industrial Designer : Hmm .", + "Marketing : 'Kay . Findings . Fifty percent of the users lose their remote often .", + "User Interface : {vocalsound} Yeah .", + "Industrial Designer : {vocalsound}", + "Marketing : So we don't have to make it very small , like uh like a mobile phone or something , but some somewhat bi bigger than small , so you don't lose it that much anymore . {vocalsound} Seventy five percent of the users also find it ugly ,", + "Industrial Designer : Mm .", + "Marketing : and fif seventy five of the users zap a lot , so the buttons sh should be that small , or shouldn't be that complex because we have to search for the buttons , which one are you going to use . Next . Important issues about the remote . I think it would be better with a personal reference , but okay . Remote control has to have to have a low power usage , because s w seventy five percent of the users only zap one time an hour , so the power usage is also one one time an hour , or so , with a high power usage we would use a lot of but batteries . The volume button and the channel buttons are the two most important buttons on the remote control , so those {disfmarker} they {disfmarker} those have to h be find very easily . And have to be somewhat like bigger etcetera . It has also be {disfmarker} have to find easily when the label is gone . My colleague also announced it that labels should be scratched off", + "Industrial Designer : Mm .", + "User Interface : Hmm .", + "Marketing : or would be s uh {gap} senden {gap}", + "User Interface : {vocalsound}", + "Marketing : okay . {vocalsound} So uh if that's k uh if that's the problem , you also have to find it easily on the remote . Buttons . Like what all colleagues said , have to have to be minimalized . or should be covered , or in L_C_D_ screen . L_C_D_ screen is easy because we have the L_C_D_ screen , we have the various options . Put one option and then you have the all the buttons of that options , so the other options would be gone . And you don't see the buttons . So L_C_D_ screens should be easy , but an L_C_D_ screen , the problem with the L_ sc L_C_D_ screen is that elderly people fr from forty five to for sixty five years don't use the L_C_D_ screen a lot . So we have to that keep that in mind that if you're going to implement L_C_D_ screen , you don't have to make it that hard to learn or to use .", + "Industrial Designer : Uh L_C_D_ screen as in uh touch screen ?", + "Marketing : Yeah , touch screen , yeah .", + "Industrial Designer : Okay .", + "Marketing : The last but not least , younger people are more critical about the features . Because they use the remote control often more often , and are more technical than the ol older people . And the older people spend more money , and easily on a remote control .", + "User Interface : Mm .", + "Industrial Designer : 'Kay .", + "Marketing : So we have to keep in mind to to focus not a lot {disfmarker} not that much on the younger pep younger people , but also somewhat on the elderly people . And on my personal preferences , I don't have any mo more time to come with that ,", + "User Interface : {vocalsound} {vocalsound}", + "Marketing : but like I said , L_C_D_ screen is easily to use", + "Industrial Designer : {vocalsound}", + "Marketing : because you have {disfmarker} you can implement a lot of buttons in one remote with not that much buttons . And it should be easy to use . Especially the volume buttons , the channel buttes buttons and the number buttons to zap through the channels . And that is it .", + "Project Manager : Okay ,", + "Industrial Designer : Okay . {vocalsound}", + "Project Manager : thank you ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 50, + "turns": [ + 34, + 43 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "money", + "speaker": "Lynne Neagle AM , Dr Frank Atherton" + }, + "summary": "Lynne Neagle AM asked what assessment they had made of how money was being spent in other UK nations since the money was used in other UK nations to directly impact obesity but in wales, the money was put into the general pot and it was being used to fund a plethora of different things. Dr Frank Atherton said that what they needed to look at was whether the programs, the sorts of programs that were being funded in England, or indeed in Scotland, were working effectively and were they delivered in Wales.", + "title": "Utilization of Public Health Money", + "relevant_turns": [ + [ + 0, + 9 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "money", + "speaker": "Lynne Neagle AM , Dr Frank Atherton" + }, + "summary": "Lynne Neagle AM asked why the money in Wales was put into the general pot and it's being used to fund a plethora of different things instead of tackling obesity. Dr Frank Atherton said ambition in Wales was to go further than those nations, in many ways.", + "title": "Utilization of Public Health Money", + "relevant_turns": [ + [ + 0, + 9 + ] + ] + } + ], + "source": [ + "Lynne Neagle AM : Can I just ask on that before Si\u00e2n moves on? What assessment have you made of how that money is being spent in other UK nations? Because my understanding is that the money is being used in other UK nations to directly impact on obesity. Have you given any consideration to\u2014? As I understand it, that money now is being dispersed around a plethora of programmes, including the transformation programme, and what I found very odd, really, was vaccination, which is surely the core business of the NHS. Have you got any view on that?", + "Dr Frank Atherton : I'm not sure I understand your point, Chair, in terms of the link between the consequentials from\u2014. Are you talking about the consequentials from the sugar levy or are you talking about\u2014?", + "Lynne Neagle AM : Yes, because in other nations, it is being used to directly impact on initiatives to tackle obesity, whereas, we've kind of put it here in Wales into the general pot and it's being used to fund a plethora of different things.", + "Dr Frank Atherton : Well, that cuts to what I was talking about. My preference\u2014it's a personal view\u2014is that hypothecation doesn't really help us too much. I mean, what we need to look at is whether the programmes, the sorts of programmes that are being funded in England, or indeed in Scotland, are working effectively, and if they are, are they being delivered here in Wales? We have looked very carefully at the plans that England and Scotland have for tackling obesity and overweight, and we've made a comparison with what we're doing in Wales, and our ambition in Wales is to go further than those nations, in many ways. But I come back to the point that just linking the hypothecation of a relatively small amount of resource is likely to be less impactful than asking a question of public services boards and of the health system, indeed, about how much money, overall, are we putting into prevention.", + "Lynne Neagle AM : No, I recognise that, and I think we're talking about additional resource. Suzy.", + "Suzy Davies AM : I was just wondering whether you thought that there was a useful psychological link on the part of the public between saying, 'Here's a sugar levy', and 'It's going to be used to help children and adults stay healthier.' Going into a pot, it actually makes it quite difficult to explain the purpose of the tax in the first place. So, I take your overall point, but in terms of the people who we're trying to help in all this, actually creating a direct link might be quite helpful.", + "Dr Frank Atherton : You may be right. I'm not a behavioural psychologist. We'd have to ask\u2014", + "Suzy Davies AM : Neither am I. I'm a person who eats a lot of sugar. [Laughter.]", + "Dr Frank Atherton : Your point's taken.", + "Suzy Davies AM : Thank you." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 50, + "turns": [ + 47, + 65 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "data", + "speaker": "Dr Frank Atherton" + }, + "summary": "Dr Frank Atherton said that their main source of data was the child measurement program, which collected information on children entering school aged four or five.", + "title": "Main Source of Data", + "relevant_turns": [ + [ + 4, + 12 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "high", + "topic": "data", + "speaker": "Dr Frank Atherton" + }, + "summary": "Dr Frank Atherton said that their main source of data and information was the child measurement program, which collected information on children entering school aged four or five, and the latest data which was out last week showed that just under a third of children at that age were overweight or obese. The proportion of those who were severely obese was about 12 percent.", + "title": "Main Source of Data", + "relevant_turns": [ + [ + 4, + 12 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "gaps , data", + "speaker": "Dr Frank Atherton" + }, + "summary": "Dr Frank Atherton said that having a longitudinal view over time of what was happening to children would be helpful in addressing gaps in data as seen in England.", + "title": "Way to Address Gaps in Data", + "relevant_turns": [ + [ + 13, + 15 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "high", + "topic": "gaps , data", + "speaker": "Dr Frank Atherton" + }, + "summary": "Dr Frank Atherton said that having a longitudinal view over time of what was happening to children would be helpful in addressing gaps in data but it would have significant resource implications, not just for the funding, but also for schools and for the system delivering it but it would be something that would help in terms of better understanding and better evaluation.", + "title": "Way to Address Gaps in Data", + "relevant_turns": [ + [ + 13, + 15 + ] + ] + } + ], + "source": [ + "Lynne Neagle AM : Thank you. We've got some questions now from Janet Finch-Saunders.", + "Janet Finch-Saunders AM : Thank you, Chair. Delivery of the plan will be led by a national implementation board that will be accountable to Ministers. Which Minister do you believe it should be accountable to, or, given the complexity of obesity, should the board be directly accountable to the First Minister?", + "Dr Frank Atherton : Ultimately, the First Minister will be responsible for this and will want to have a strong oversight of this. It is often framed as a health issue, and the Minister, Vaughan Gething, has a strong personal commitment to this, I know. We've talked extensively with him and with sports and recreation colleagues about that, so there's a link there. It does cut across all portfolios, and so this is an issue that I have discussed with Cabinet, and that collective ownership is really important, and will be, because it can't just sit in one domain. I think what you do need to have is you do need to have a lead organisation or a lead ministry, and I would see health as\u2014I work within health, so I'm perhaps biased, but I would see health as leading this, but it needs broad ownership across Government.", + "Janet Finch-Saunders AM : I know my colleague Si\u00e2n Gwenllian mentioned earlier targets and things, but I know in Wales we're not too good at collecting data. What data is currently available on childhood obesity and what metrics will be used to measure progress against the plan's objectives?", + "Dr Frank Atherton : Well, of course, our main data source is the child measurement programme, which collects information on children entering school aged four or five. That's our main source of information. If we look at that data, it shows us\u2014. Well, I'm sure you're familiar with the statistics, but it'll be just under a third of children at that age who are overweight or obese\u2014", + "Janet Finch-Saunders AM : Could I just ask\u2014sorry to interrupt\u2014how up to date is that?", + "Dr Frank Atherton : The last survey was just last year.", + "Nathan Cook : The data was published last week.", + "Dr Frank Atherton : Yes, the lastest data was out last week.", + "Janet Finch-Saunders AM : It is pretty up to date.", + "Dr Frank Atherton : So, it's pretty up to date, and what it shows\u2014. It's not getting radically worse\u2014there's always statistical variation in these things\u2014but it's not getting any better. And, for the first time last year, we did look at the question not just of children who were overweight or obese, but we actually singled out the proportion who are obese, severely obese. So we have a figure for that for the first time, which is about 12 per cent, which is quite shocking, in a way.", + "Janet Finch-Saunders AM : It is shocking.", + "Dr Frank Atherton : So, that's our main source of information. Does that answer your question?", + "Janet Finch-Saunders AM : Yes, but how will any gaps in your data be addressed?", + "Dr Frank Atherton : Well, one of the questions that are often asked is: could we measure more on a longitudinal basis? By that I mean in England, for example, children are measured at school entry and then again at year 11\u2014at age 11 or 12., that kind of age group. And so you do have a longitudinal view over time of what's happening to children. I think that would be helpful to us in Wales, and it's one of the questions in the consultation about whether we should expand that. Obviously, that would have significant resource implications, not just for the funding, but also for schools and for the system to deliver it. But it's something that maybe would help us in terms of better understanding and better evaluation\u2014the point that was made earlier.", + "Nathan Cook : And the other data we do have is the millennium cohort study, which has been released, for 14 and 15-year-olds. That's going to be\u2014. We're starting to think about how we can utilise some of that data, looking at that longitudinal picture around children as well, which will be really helpful.", + "Janet Finch-Saunders AM : Thank you. You've answered my next question. Thank you.", + "Lynne Neagle AM : Can I just ask about the child measurement programme? The strategy commits to looking at whether we can have a second measurement taking place in Wales. Can you just tell us a bit more about your thinking on that and when you would see a second measurement taking place and how you would use that data?", + "Dr Frank Atherton : I touched on that just now, but personally I do think it would be helpful to have more information. It's always the case, There's always a trade-off between the cost of getting that information and the value of the information. So, the question of how it would be used would be really important. There is still a lot that we don't know. We know an awful lot about obesity and being overweight and the causes of it, but we don't really have a very clear understanding, in Wales at least, of the point at which children start to become overweight. Although we know that overweight children tend to go on to become overweight adults, we don't know what proportion of them between school entry and later teenage years\u2014what those changes are. So, it would help us to have some better understanding, which would help to direct some of our initiatives. I'd be generally supportive of the principle. We'll wait and see what comes out in the consultation, and it's something that we need to give thought to,\u00a0 but we do have to trade off the additionality of what the information would give us with the cost of doing that, of course." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 70, + "turns": [ + 185, + 310 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "action", + "speaker": "Grad C , Grad D" + }, + "summary": "Grad D asked where \"Action\" and \"Goodbye\" functions were, if they were going to be called and if they were present in the code for the parser. Grad C said one would need to get XML changed when encountered with ''Day'' and reported seeing \"Goodbye\" and other actions somewhere.", + "title": "The Action Function", + "relevant_turns": [ + [ + 5, + 16 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "high", + "specificity": "high", + "topic": "action", + "speaker": "Grad C , Grad D" + }, + "summary": "Grad D asked where \"Action\" and \"Goodbye\" functions were, if they were going to be called and if they were present in the code for the parser. Grad C confirmed that the XLM object did something fancy, it had style sheets and schemata. Grad C tried to find where the action \"Goodbye\" mapped into something. Grad C said when you would need to change the XML when it encounters \"Day\" and it would activate the classes in the XML stuff.", + "title": "A Discussion on Action Functions", + "relevant_turns": [ + [ + 5, + 16 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "discourse status", + "speaker": "Professor B" + }, + "summary": "Grad D said each of the functions acted on the current XML structure and changed it in some way for example by adding an \"l\" field to it. Professor B said they also seem to affect the state because some of them were other actions that seemed to state variables somewhere. Professor B added that \"Discourse Status Confirm\" was an example that would be a call on the discourse.", + "title": "Exploring the Discourse Status Confirm Action", + "relevant_turns": [ + [ + 22, + 45 + ], + [ + 85, + 90 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "discourse status", + "speaker": "Professor B" + }, + "summary": "Grad D said each of the functions acted on the current XML structure and changed it in some way for example by adding an \"l\" field to it. Professor B said they also seem to affect the state because some of them were other actions that seemed to state variables somewhere. Professor B added that \"Discourse Status Confirm\" was an example that would be a call on the discourse. Grad C said there was a feature called \"Discourse - Status\" so whenever Grad C says \"Write\" it would put it in there. Professor B said the Discourse Maintainer ran around looking for Discourse Status tags.", + "title": "Discussing the Discourse Status", + "relevant_turns": [ + [ + 22, + 45 + ], + [ + 85, + 90 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "next thing", + "speaker": "Grad C" + }, + "summary": "Grad C said the next thing Grad C would have liked to be capable to say was that they should pretend they actually wanted to change the mapping of words to the \"M-three-L\" and also wanted to add a new sentence type and make up some new \"M-three-Ls\". Professor B said the next thing they talked about was actually figuring out how to add their own tags and alike.", + "title": "The Next Things to be Discussed in the Meeting", + "relevant_turns": [ + [ + 0, + 4 + ], + [ + 88, + 92 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "high", + "topic": "next thing", + "speaker": "Grad C" + }, + "summary": "Grad C, next thing, able to do, to say, pretend, wanted to not only change, the mapping, words to the M-three-L, but, also, wanted to change, add a new sentence type, shouldn't be too tough; get a complete understanding of the whole thing.", + "title": "The Next Things to be Discussed in the Meeting", + "relevant_turns": [ + [ + 0, + 4 + ], + [ + 88, + 92 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "state", + "speaker": "Grad D , Professor B" + }, + "summary": "Grad D said each of the functions acted on the current XML structure and changed it in some way for example by adding an \"l\" field to it. Professor B said they also seemed to affect the state because some of them were other actions that seemed to state variables somewhere. Grad A said that whatever takes the \"M- three-L\" was, was what actually changed the state.", + "title": "Factors Affecting the State", + "relevant_turns": [ + [ + 27, + 42 + ], + [ + 74, + 85 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "state", + "speaker": "Grad D , Professor B" + }, + "summary": "Grad D said each of the functions acted on the current XML structure and changed it in some way for example by adding an \"l\" field to it. Professor B said they also seemed to affect the state because some of them were other actions that seemed to state variables somewhere. Professor B added that \"Discourse Status Confirm\" was an example that would be a call on the discourse and would look like state modification. Grad C suggested adding something to allow the user to change something that was done before and Grad A said that whatever takes the \"M- three-L\" was, was what actually changed the state.", + "title": "Changing States", + "relevant_turns": [ + [ + 27, + 42 + ], + [ + 74, + 85 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "xml stuff", + "speaker": "Grad C" + }, + "summary": "Grad C asked if what Grad C was looking at was already the XML stuff, where it took its own syntax and converted it somehow. Grad C said you would need to change the XML when it encountered \"Day\" and it would activate the classes in the XML stuff.", + "title": "Meeting about the XML Object", + "relevant_turns": [ + [ + 5, + 27 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "high", + "topic": "xml stuff", + "speaker": "Grad C" + }, + "summary": "Grad C asked if what Grad C was looking at was already the XML stuff, where it took its own syntax and converted it somehow. Grad C was looking for where the XML object produced the XML out of the parsed stuff. Grad C said you would need to change the XML when it encountered \"Day\" and it would activate the classes in the XML stuff. Grad D said \"M- three-L dot DTD\" was just a specification for the XML format and that each of the discussed functions acted on the current XML structure and changed it in some way for example by adding an \"l\" field to it or something close.", + "title": "Figuring out the XML Ideas", + "relevant_turns": [ + [ + 5, + 27 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "goodbye", + "speaker": "Grad D" + }, + "summary": "Grad D asked where \"Action\" and \"Goodbye\" functions were. Grad C said one would need to get XML changed when encountered with ''Day'' and reported seeing \"Goodbye\" somewhere.", + "title": "Goodbye Function on the XLM Object", + "relevant_turns": [ + [ + 5, + 24 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "high", + "topic": "goodbye", + "speaker": "Grad D" + }, + "summary": "Grad D asked where \"Action\" and \"Goodbye\" functions were, if they were going to be called and if they were present in the code for the parser. Grad C said you would need to change the XML when it encounters ''Day'' and it would activate those classes in the XML stuff. Grad C reported seeing \"Goodbye\" stuff somewhere.", + "title": "Locating the Goodbye Function on the XLM Object", + "relevant_turns": [ + [ + 5, + 24 + ] + ] + } + ], + "source": [ + "Grad C : And the next thing I would like to be able to do , and it seems like this would not be too difficult either , is {vocalsound} to say , \" OK let 's now pretend we actually wanted to not only change the {disfmarker} {vocalsound} the mapping of {disfmarker} of , uh , words to the M - three - L but we also wanted to change {disfmarker} add a new sentence type and and make up some {disfmarker} some new M - three - L {disfmarker} s \"", + "Professor B : Yep . So That 'd be great . It would be a good exercise to just see {vocalsound} whether one can get that to run .", + "Grad C : See th Mm - hmm . {vocalsound} Yep . And , um ,", + "Grad D : So , that 's {disfmarker}", + "Grad C : that 's {disfmarker} shouldn't be too tough .", + "Grad D : Fine , yeah . Yeah , so where are those {disfmarker} those functions \" Action \" , \" Goodbye \" , and so on , right ? Are they actually , um , {vocalsound} Are they going to be called ? Um , are they present in the code for the parser ?", + "Grad C : Yeah . I think what it does , it i i it does something sort of fancy . It loads um {disfmarker} It has these style sheets and also the , um , schemata . So what it probably does , is it takes the , uh , {vocalsound} um {disfmarker} Is this where it is ? This is already the XML stuff ? This is where it takes its own , um , syntax , and converts it somehow . Um . Where is the uh {disfmarker}", + "Grad D : What are you looking for ?", + "Grad C : Um , where it actually produces the {disfmarker} the XML out of the , uh , parsed {pause} stuff .", + "Grad D : Oh , OK .", + "Grad C : No , this is not it . Uh . I can't find it now . You mean , where the {disfmarker} where the act how the action \" Goodbye \" maps into something {disfmarker}", + "Grad D : Yeah .", + "Grad A : Yeah , where are those constructors defined ?", + "Grad D : Oh .", + "Grad C : Nope .", + "Grad D : No , that 's not it .", + "Grad C : Yeah . This is sort of what happens . This is what you would need to {disfmarker} to change {disfmarker} to get the , uh , XML changed . So when it encounts encounters \" Day \" , {vocalsound} it will , uh , activate those h classes in the {disfmarker} in the XML stuff But , um {disfmarker} I saw those actions {disfmarker} uh , the \" Goodbye \" stuff somewhere . Hmm , hmm , hmm , hmm , hmm .", + "Grad A : Grep for it ?", + "Grad C : Yeah . Let 's do that . Oh .", + "Grad D : Mmm . M - three - L dot DTD ?", + "Grad C : Yep .", + "Grad D : That 's just a {pause} specification for the XML format .", + "Grad C : Yep . Well , we 'll find that out . So whatever {disfmarker} n this does {disfmarker} I mean this is , basically , looks l to me like a function call , right ?", + "Professor B : Hmm ? Oh , yeah .", + "Grad C : And , um {disfmarker} So , whenever it {disfmarker} it encounters \" Goodbye \" , which we can make it do in a second , here", + "Grad A : That function automatically generates an initialized XML structure ?", + "Grad C : I", + "Grad D : I think each of those functions act on the current XML structure , and change it in some way , for example , by adding a {disfmarker} a l a field to it , or something .", + "Professor B : y Yeah . They also seem to affect state ,", + "Grad C : Mm - hmm .", + "Professor B : cause some of them {disfmarker} there were other actions uh , that {disfmarker} that s seemed to step {disfmarker} state variables somewhere ,", + "Grad D : Right .", + "Professor B : like the n s \" Discourse Status Confirm \" . OK . So that 's going to be a call on the discourse", + "Grad C : Yep .", + "Professor B : and {vocalsound} confirm that it 's {disfmarker}", + "Grad C : W we Mm - hmm", + "Grad D : Oh , you mean that 's not going to actually modify the tree ,", + "Professor B : I think that 's right .", + "Grad C : e", + "Grad D : but it 's going to change the event .", + "Professor B : I think it 's actually {disfmarker} That looks like it 's state modification .", + "Grad D : Oh . Oh .", + "Grad C : e mmm Um , well i There is a feature called \" Discourse - Status \" ,", + "Grad D : When there 's a feature .", + "Professor B : Yeah .", + "Grad C : And so whenever I just say , \" Write \" , it will {disfmarker} it will put this in here .", + "Professor B : Oh , so it always just {disfmarker} Is it {disfmarker} So it {disfmarker} Well , go back , then , cuz it may be that all those th things , while they look like function calls , are just a way of adding exactly that to the XML .", + "Grad C : h Yep .", + "Professor B : Uh - huh ! I 'm not {disfmarker} I 'm not sure .", + "Grad C : So , this {disfmarker}", + "Professor B : e I 'm not sure {disfmarker} e that {disfmarker}", + "Grad C : Um {disfmarker} well , we {disfmarker} we 'll see , when we say , let 's test something , \" Goodbye \" , causes it to c to create basically an \" Action Goodbye - End - Action \" .", + "Professor B : Right .", + "Grad C : Which is a means of telling the system to shut down .", + "Professor B : Right .", + "Grad C : Now , if we know that \" Write \" produces a \" Feature Discourse - Status Confirm Discourse - Status \" . So if I now say \" Write , Goodbye , \" it should do that . It sho it creates this ,", + "Grad D : Mm - hmm .", + "Professor B : Right .", + "Grad C : \" Confirm Goodbye \" .", + "Professor B : Yep .", + "Grad D : Right there . But there is some kind of function call , because how does it know to put Goodbye in Content , but , uh , Confirm in Features ?", + "Grad C : Oh . It d it {disfmarker} n That 's because {disfmarker}", + "Grad D : So So , it 's not just that it 's adding that field .", + "Professor B : Right .", + "Grad D : It 's", + "Professor B : Absolutely . Good point .", + "Grad D : OK .", + "Professor B : It 's {disfmarker} it 's {disfmarker} the {disfmarker} It 's under what sub - type you 're doing it . Yeah .", + "Grad C : Mm - hmm . Yeah .", + "Grad A : It 's mystery functions .", + "Grad C : Well , sometimes it m Sometimes , i", + "Grad D : Well , they 're defined somewhere , presumably .", + "Professor B : Yeah , each is {disfmarker} S so that 's funny .", + "Grad C : When it {disfmarker}", + "Professor B : You bury the s the state in the function Alright .", + "Grad C : it {disfmarker}", + "Grad A : Well , it just automatically initializes things that are common , right ?", + "Professor B : Uh", + "Grad A : So it 's just a shorthand .", + "Professor B : Yeah .", + "Grad C : For example {disfmarker} Oh , this is German . Sorry . e So , now , this , it cannot do anymore . Nothing comes out of here .", + "Grad A : A \" not a number \" is a value . Awesome .", + "Grad C : So , it doesn't speak German anymore , but it does speak English . And there is , here , a reference {disfmarker} So , this tells us that whatever is {disfmarker} has the ID \" zero \" is referenced here {disfmarker} by @ @ {comment} the restriction seed and this is exa \" I want {disfmarker} \" What was the sentence ?", + "Professor B : \" I want two seats here . \"", + "Grad C : \" need two seats here . \" Nuh . \" And where is it playing ? \" There should also be a reference to something , maybe . Our d This is re um Mmm . Here , we change {disfmarker} and so , we {disfmarker} Here we add something to the Discourse - Status , that the user wants to change something that was sort of done before And , uh {disfmarker} and that , whatever is being changed has something to do with the cinema .", + "Grad A : So then , whatever takes this M - three - L is what actually changes the state , not the {disfmarker} Yeah , OK .", + "Professor B : No , right , the Discourse Maintainer ,", + "Grad A : Yeah .", + "Professor B : yeah . I see . And it {disfmarker} and it runs around looking for Discourse Status tags , and doing whatever it does with them . And other people ignore those tags . Alright . So , yeah . I definitely think it 's {disfmarker} {vocalsound} It 's worth the exercise of trying to actually add something that isn't there .", + "Grad C : Hmm ?", + "Professor B : Uh Disc", + "Grad C : Sort of get a complete understanding of the whole thing .", + "Professor B : Yeah , a kid understanding what 's going on . Then the next thing we talked about is actually , {vocalsound} um , figuring out how to add our own tags , and stuff like that .", + "Grad C : OK . Point number two . I got the , uh , M - three - L for the routes today . Uh , so I got some more . This is sort of the uh , {vocalsound} um , Hmm . Interesting . It 's just going up , it 's not going back down . So , this is {disfmarker} um , what I got today is {vocalsound} the {disfmarker} the new {vocalsound} um {vocalsound} M - three - L for um , {vocalsound} {vocalsound} the Maps ,", + "Professor B : Yep .", + "Grad C : uh , and with some examples {disfmarker} So , this is the XML and this is sort of what it will look like later on , even though it {disfmarker} you can't see it on {disfmarker} on this resolution . And this is what it {disfmarker} sort of is the {disfmarker} the structure of Map requests , um also not very interesting , and here is the more interesting stuff for us , is the routes , route elements , and , again , as we thought it 's really simple . This is sort of the , uh , {vocalsound} {vocalsound} um , {vocalsound} parameters . We have @ @ {comment} simple \" from objects \" and \" to objects \" and so forth , points of interest along the way {disfmarker} And , um , I asked them whether or not we could , um {disfmarker} First of all , I was little bit {disfmarker} It seemed to me that this m way of doing it is sort of a stack a step backwards from the way we 've done it before . t It seems to me that some notions were missing .", + "Professor B : S", + "Grad C : So these are {disfmarker} these are {disfmarker}", + "Professor B : So these are {disfmarker} these are your friends back at EML .", + "Grad C : Yep . Who are doing this .", + "Professor B : So this is not a complicated negotiation . There 's {disfmarker} there 's not seven committees , or anything , right ?", + "Grad C : No . No , this is very straightforward .", + "Professor B : Great . So this is just trying to {disfmarker} It 's a design thing , not a political thing . Once we 've {disfmarker} eh {disfmarker} We can just sort of agree on what oughta be done .", + "Grad C : Yeah .", + "Professor B : Good .", + "Grad C : Exactly . And , um {disfmarker} And , uh {disfmarker} However , the , uh {disfmarker} e So that you understand , it is really simple . Uh {disfmarker} You {disfmarker} you have a route , and you cut it up in different pieces . And every {disfmarker} every element of that e r r f of that {disfmarker} Every segment we call a \" route element \" . And so , from A to B we cut up in three different steps , and every step has a \" from object \" where you start , a \" to object \" where y where {pause} you sort of end , and some points of interest along the way . What w I was sort of missing here , and uh , maybe it was just me being too stupid , is , {vocalsound} I didn't sort of get the {disfmarker} the notion of the global goal of the whole route . Really , s was not straightforward visibly for me . And some other stuff . And I {vocalsound} suggested that they should n be {disfmarker} k uh , kind enough to do s two things for us , is one , um , {vocalsound} {vocalsound} Also allocating , uh , some tags for our Action Schema Enter - Vista - Approach , and {disfmarker} And also , um , since you had suggested that {disfmarker} that , um , we figure out if we ever , for a demo reason , wanted to shortcut directly to the g GIS and the Planner , of how we can do it . Now , what 's the state of the art of getting to entrances , um , what 's the syntax for that , how get getting to {vocalsound} vista points and calculating those on the spot . And the Approach mode , anyhow , is the default . That 's all they do it these days . Wherever you 'll find a route planner it n does nothing but get to the closest point where the street network is {vocalsound} at minimal distance to the geometric center .", + "Professor B : Mm - hmm .", + "Grad C : So .", + "Professor B : So , well , let {disfmarker} Now , this is important . Let , uh {disfmarker} I want a a Again , outside of m almost managerial point , um {disfmarker} You 're in the midst of this , so you know better . But it seems to me it 's probably a good idea to li uh {disfmarker} minimize the number of uh , change requests we make of them . So it seemed to me , what we ought to do is get our story together . OK ? And think about it some , internally , before asking them to make changes .", + "Grad C : Mm - hmm .", + "Professor B : Oh . Does this {disfmarker} does this make sense to you guys ? It {disfmarker} I mean you 're {disfmarker} you 're doing the {disfmarker} the interaction but it seemed to me that {vocalsound} what we ought to do is come up with a {disfmarker} uh , something where you , um {disfmarker} And I {disfmarker} I don't know who 's mok working most closely on it . Probably Johno . OK . Uh , take what they have , send it to everybody saying \" this is what they have , this is what we think we should add \" , OK ? and then have a d a {disfmarker} an iteration within our group saying \" Hmm , well {disfmarker} \" OK ? And get our best idea of what we should add .", + "Grad C : Mm - hmm .", + "Professor B : And then go back to them . Is i or , I don't know does this make sense to you ? Or", + "Grad C : Yeah . {vocalsound} Especially if we want {disfmarker} Sort of , what I {disfmarker} my feeling was eh we {disfmarker} we sort of reserved something that has a r eh an OK label . That 's {disfmarker} th that was my th first sort of step .", + "Professor B : Mm - hmm .", + "Grad C : I w No matter how we want to call it , {vocalsound} this is sort of our playground .", + "Professor B : Right .", + "Grad C : And if we get something in there that is a structure elaborate and {disfmarker} and {disfmarker} and {disfmarker} and {disfmarker} and complex enough to {disfmarker} to {disfmarker} to maybe enable a whole simulation , one of these days , that would be {disfmarker} u the {disfmarker} the perfect goal .", + "Professor B : Right . That 's right . So . So , Yeah . The problem isn't the short ra range optimization . It 's the sort of {disfmarker} o one or two year kind of thing . OK . What are the thl class of things we think we might try to do in a year or two ? How {disfmarker} how would we try to characterize those and what do we want to request now {vocalsound} that 's leave enough space to do all that stuff ?", + "Grad C : Mm - hmm .", + "Professor B : Right .", + "Grad C : Yep .", + "Professor B : And that re that requires some thought .", + "Grad C : Yep .", + "Professor B : And {disfmarker} so that sounds like a great thing to do {vocalsound} as the priority item um , as soon as we can do it .", + "Grad C : Yep ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 20, + "turns": [ + 324, + 396 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "colour , logo , product", + "speaker": "" + }, + "summary": "Colour and logo to be incorporated somewhere on the product in order to identify it as a product from the company. The colors didn't necessarily have to be the colors of the company.", + "title": "Logo Position and Color of Product", + "relevant_turns": [ + [ + 0, + 8 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "high", + "topic": "colour , logo , product", + "speaker": "" + }, + "summary": "Project Manager; more of a sense that people know that this is from our company; incorporate our logo and colour in some way; logo on the bottom, or wherever you feel like it would look good; doesn't have to be the colour of our company; have that color and logo decided upon.", + "title": "Logo Position and Color of Product", + "relevant_turns": [ + [ + 0, + 8 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "finalize , product", + "speaker": "" + }, + "summary": "The product would be kept simple by excluding LCD, Teletext, and voice recognition features but include the alarm system as it would be inexpensive because it shares the same signal. The number of buttons on the product would be minimized to ease findability. The product would be designed for use just for the television with the target market being the international crowd.", + "title": "Product Features", + "relevant_turns": [ + [ + 17, + 70 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "high", + "topic": "finalize , product", + "speaker": "" + }, + "summary": "Project Manager; need to discuss; come to a decision on our remote control functions; have to decide on a target group and the functions of the remote control; already know that it'll just be for the television; Marketing; write off the LCD option; no Teletext, and no voice recognition; Project Manager; looking at something rather simple; minimize buttons; findability is important; go ahead with the alarm system idea; sure that could be inexpensive; use the same kind of infrared; it could just like make a little beeping noise; vibrate; a buzz or something.", + "title": "Product Features", + "relevant_turns": [ + [ + 17, + 70 + ] + ] + } + ], + "source": [ + "Project Manager : Alright , and another thing . This is for the design , the design of the product is that um we wanna create , um more of a sense that people know that this is from our company . So , um , all the remote controls must have our um {disfmarker} We'll incorporate our logo and colour in in some way .", + "Industrial Designer : Right . Yeah .", + "Project Manager : So , um , perhaps um our logo on the bottom , or wherever you feel like it would look good .", + "Industrial Designer : Yeah . Okay .", + "Project Manager : Um , it doesn't have to be the colour of our um of our company", + "Industrial Designer : Just {disfmarker}", + "Project Manager : but , another thing is that , um", + "Industrial Designer : {vocalsound}", + "Project Manager : we need to , we probably would have to have that colour and , and logo decided upon . Um , I'm assuming that we already have one , but for the purposes of this meeting I , I wasn't offered a , like a type of logo or colour , so if that could be um somewhere on the design so that we can be recognisable .", + "Industrial Designer : Okay . Work on that .", + "Marketing : It's probably R_ R_R_ in yellow . {vocalsound}", + "User Interface : Yeah .", + "Industrial Designer : Yeah .", + "Project Manager : The little R_ R_ yellow thing ? Okay .", + "Industrial Designer : Mm-hmm .", + "User Interface : Yeah .", + "Marketing : Yeah , I think .", + "Project Manager : Real Reaction ? Okay . Um , yes , those are the changes . Um , so , now we need to discuss , um and come to a decision on our remote control functions , of , of how this is going to be . I'm just going to look at my notes for a second . Um , we have to decide on a target group and the functions of the remote control . So , um , we already know that it'll just be for the television .", + "Industrial Designer : Okay .", + "Project Manager : It'll {disfmarker} It won't have teletext . But um , you know , we could discuss um those other options that you brought up , Genevieve .", + "Industrial Designer : {gap}", + "Marketing : Okay , so I {disfmarker} Are we going to write off the L_C_D_ option ?", + "Industrial Designer : Yeah .", + "Project Manager : Is that how most people feel about that ?", + "User Interface : Yeah .", + "Marketing : Yeah ?", + "Industrial Designer : Yeah .", + "Project Manager : Okay .", + "Marketing : Okay . So no L_C_D_ , no teletext , and no voice recognition .", + "User Interface : I think it would be annoying though if {disfmarker} I don't use teletext that much , but if it was on your T_V_ , you'd want to be able to use it , if {disfmarker}", + "Project Manager : Yeah , but another thing is that if we're reaching an international crowd , um , I know for one that in North America there is no such thing as teletext , so it'd be really superfluous .", + "User Interface : You'd {disfmarker} Yeah .", + "Marketing : Yeah .", + "User Interface : So is it just {disfmarker}", + "Industrial Designer : Yeah .", + "Marketing : Never heard of it .", + "User Interface : Okay . Alright .", + "Project Manager : Yeah . I don't know about other countries besides the U_K_ .", + "User Interface : Right .", + "Project Manager : Do you know if anywhere else has it ?", + "Industrial Designer : I don't know .", + "User Interface : I don't know .", + "Industrial Designer : More research required , I think .", + "User Interface : I don't know . {vocalsound}", + "Project Manager : Alright .", + "Industrial Designer : {vocalsound} But if {disfmarker} Was it a management decision that we're having {disfmarker}", + "Project Manager : It was a management decision ,", + "Industrial Designer : Okay .", + "Project Manager : so it's , it's pretty much out of our hands at this point .", + "Industrial Designer : So {disfmarker}", + "User Interface : Yeah .", + "Industrial Designer : Okay .", + "User Interface : Okay then .", + "Project Manager : 'Kay . So , I guess we're looking at something rather simple .", + "Marketing : Um , well I guess , just from my findings it looks like we wanna minimise buttons .", + "Industrial Designer : 'Kay .", + "Marketing : Um .", + "Industrial Designer : Minimal {disfmarker}", + "Marketing : And the {disfmarker} What was the word they used ? F findability is important .", + "Industrial Designer : {vocalsound}", + "User Interface : {vocalsound}", + "Project Manager : Yeah . I think we should definitely go ahead with the alarm system idea that you had .", + "Industrial Designer : Yeah okay .", + "Marketing : {vocalsound} Mm-hmm .", + "Project Manager : 'Cause I'm sure that could be inex inexpensive because we could use the same kind of infrared", + "User Interface : Yeah .", + "Industrial Designer : Yeah . The same signalling .", + "Project Manager : the same signal through that and it could just like make a little beeping noise .", + "Industrial Designer : I mean {disfmarker}", + "Project Manager : It's not that expensive to do .", + "Industrial Designer : Or vibrate just the same as a mobile phone . Like you just a , a buzz or something .", + "Project Manager : Yeah . Yeah . Okay . I like that idea .", + "Industrial Designer : Yeah ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 34, + "turns": [ + 102, + 156 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "parallel marketing , angle", + "speaker": "Marketing" + }, + "summary": "Marketing had two ideas for the product to be marketed, especially if it was to sell something that had four million of them. On the one hand, they could attract people who wanted to have a new device that looked cool, and on the other hand, form a kind of necessity relationship with the device because of its practicality. Marketing concluded by saying that they had to decide which angle they would take or if they would take both.", + "title": "Remote Control Marketing", + "relevant_turns": [ + [ + 3, + 12 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "normal", + "topic": "parallel marketing , angle", + "speaker": "Marketing" + }, + "summary": "Marketing, could have parallel marketing, schemes, one where it appeals to people that want to have the new device that looks cool; one that rather, than a kind of a need relationship with the device; people might not like, having a device, just looks nice; also a device, practically sound; decide which angle, gonna go to or both.", + "title": "Remote Control Marketing", + "relevant_turns": [ + [ + 3, + 12 + ] + ] + } + ], + "source": [ + "Project Manager : Okay . So , Andrew have you had any thoughts yet about how we might market something which there are already millions out there and that we want to uh uh uh t take over the entire um {disfmarker} the planet with ?", + "Industrial Designer : {vocalsound}", + "User Interface : {vocalsound}", + "Marketing : Mm-hmm , um {vocalsound} especially if we try to sell , what two million of them . Oh sorry , four million of 'em , but uh {disfmarker} I think if w if we market it as as not as not {disfmarker} well this {disfmarker} you c you could either market it as the point of view {disfmarker} we could have the two {disfmarker} we could have parallel marketing s schemes where you've got one where it appeals to people that want to have the new device that looks cool , is fashionable", + "Industrial Designer : Mm .", + "Marketing : and like you just {disfmarker} it's it's like uh it's one that rather than ra I wan I want rather than a kind of a need relationship with the device ,", + "Project Manager : Mm-hmm .", + "Marketing : but that might {disfmarker} considering the act what the device is for and the nature of some people might not like respond to having a device that they just looks nice , therefore they want it so {disfmarker} make it practical at the same time . I think it's {disfmarker} this is gonna have to appeal to people that want device that can enhance their living room", + "Project Manager : Mm-hmm .", + "Marketing : uh but also a device that uh is practically sound .", + "Project Manager : Mm-hmm . Okay , yeah , yeah , well", + "Marketing : So um , I dunno we'll have to decide which which angle we're gonna go to or both . If you {gap} .", + "Project Manager : I d I think an any uh any facets that we identify w we aim {disfmarker} need to aim for for all of . Um okay well", + "Marketing : Mm . {vocalsound}", + "Project Manager : it's uh the sort of {gap} the sort of thing that would get people uh thinking yes that's something that I haven't got and uh might need so . Uh Andrew , any thoughts about uh how we might market interchangeable fronts on on the remote control ?", + "Marketing : Um , well we could either market it together by getting control in a set colour or with {disfmarker} like you buy it with several uh like you ge you get the f uh the face-plates with it when you buy or as a separate thing , but uh {vocalsound} maybe thinking of that , it's {disfmarker} considering the nature of the device , maybe a second thing {disfmarker} like a second campaign to market new facials for your {disfmarker} to your {disfmarker} might go a bit astray", + "Industrial Designer : Mm .", + "Project Manager : Yeah .", + "Marketing : since it is the kind of thing where y you generally get one and then forget about it .", + "Project Manager : Yeah .", + "Marketing : Unless you were trying to {disfmarker}", + "Project Manager : I think {disfmarker}", + "Industrial Designer : Well you could come up with like novelty ones , like they've done with the the mobile phones , you can get like different you know scenes from different movies and stuff on the remote control", + "Marketing : Mm .", + "User Interface : Yeah .", + "Marketing : {vocalsound} Oh", + "Industrial Designer : and sorta stagger the release of them", + "Marketing : it's {disfmarker} that's a that's a good idea .", + "Industrial Designer : and get people like oh I want that cover on it now and that'll keep them spending money .", + "User Interface : Yeah .", + "Project Manager : Mm-mm .", + "Marketing : Mm .", + "Project Manager : Right , okay", + "Marketing : Yeah true ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 13, + "turns": [ + 0, + 13 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "meeting , presentations", + "speaker": "Project Manager" + }, + "summary": "Project Manager led a functional design meeting. Project Manager spoke about talking on project management. Project Manager said that there were three presentations and that the meeting would be forty minutes long.", + "title": "Functional Design Meeting and Agenda", + "relevant_turns": [ + 2 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "meeting , presentations", + "speaker": "Project Manager" + }, + "summary": "Project Manager relayed they were gathered to discuss the functional design meeting. Project Manager would be talking about project management. There were three presentations. One was about project requirements. Second one was about decision on remote control functions. The last one was on closing. The meeting would be forty minutes. Project Manager would discuss few points on new proposal that management came with. The teletext became outmoded. The remote control should only be used on TV. The third point was about establishing marketing.", + "title": "Particulars and Proposals on the Function Design Meeting", + "relevant_turns": [ + 2 + ] + } + ], + "source": [ + "Project Manager : Okay uh Agnes , you can help me for the slide when {gap}", + "User Interface : Yep . Sure .", + "Project Manager : okay . Okay , welcome back . I hope uh you have a fresh head and a fresh time . How t now the meeting actually we gathering here to discuss about the functional design meeting . Okay , and uh we'll issue some information from uh all of you . And it's in the , I think uh , in the sharing folder . And uh I will invite uh the Christine and the Ed and uh Agnes to discuss about on the various subjects . So can you go to the next slide ? Yeah uh the agenda of the meeting is opening . Then uh I'm going to talk about uh the project management , what I'm going to do , and uh , of course , I'm doing the project management and secretary both , okay , to take the minutes of the meeting . And there are three presentations . One is uh new project requirements . And the second one about uh decision on remote control functions . And uh finally we are closing . Uh and the meeting time will be uh forty minutes , so you have to be very quick . And I have come up with the {disfmarker} management come with the new proposal , okay , and I have to discuss a few points on this . Uh both says new insights in the aim of your project . Uh the one is uh the teletext becomes uh outmoded , okay because if uh because of the computer systems and the new technology . So we don't need to consider really about the teletext all in our new project design . And the second one is about uh the remote control . Should be used only for the T_V_ . That's what our uh management says . And the third point , it's very very important to establish our uh marketing or uh corporate image , okay , with this new project or new product . Okay . {vocalsound} So I will invite uh {disfmarker} Agnes , can you go to the third slide ?", + "User Interface : No , this is the third slide .", + "Project Manager : Okay , {gap} . So , I'll invite uh Christine to discuss about uh the functional design .", + "Industrial Designer : 'Kay , do you wanna open the {disfmarker}", + "User Interface : Sure . Um . You're participant s", + "Industrial Designer : I'm number two .", + "User Interface : Two ?", + "Project Manager : {vocalsound}", + "Industrial Designer : That's it .", + "User Interface : Do you want the mouse , or do you want me to {disfmarker}", + "Industrial Designer : I'll do the notes . Yeah , thanks .", + "Project Manager : {vocalsound}" + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 78, + "turns": [ + 0, + 172 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "volume , variation", + "speaker": "" + }, + "summary": "Postdoc F gave an update on the transcription effort, talked about raising the issue of microphone procedures with references to the cleanliness of recordings, and also talked if them having great steps forward in terms of the nonspeech-speech pre-segmentation of the signal. PhD C spoke of their old Munich loudness-based spectrum. PhD C talked about their old Munich loudness-based spectrum on mel scale twenty critical bands and then loudness, also stated the four additional features which were energy, loudness, modified loudness, and zero-crossing rate, thus twenty-four features.", + "title": "Discussions on Microphone Issues", + "relevant_turns": [ + [ + 11, + 28 + ], + [ + 86, + 90 + ], + [ + 111, + 113 + ], + 163 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "high", + "topic": "volume , variations", + "speaker": "" + }, + "summary": "Postdoc F asked about PhD C about the parameters changed. PhD C said one could specify the minimum length of speech and silent portions that one wants and talked of doing some modifications on the parameters by changing the minimum length for silence. Postdoc F talked about being provided with several different versions. PhD C talked about Susanne Burger having something that could use eight-channel transliterations simultaneously.", + "title": "PhD C's Modifications and Susanne Burger at CMU", + "relevant_turns": [ + [ + 86, + 90 + ], + [ + 111, + 113 + ], + [ + 120, + 121 + ], + 163 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "feature", + "speaker": "Professor G , PhD C" + }, + "summary": "Professor G said one of the things being pushed in the discussion was why much time was being spent on the feature issue, and added that they just broadened it a bit instead of just using silence as a putative change point also. Professor G talked about already having the super-structure with Gaussians and simple HMMs and so forth, said there was a bit of difference of opinion, and thought that it was interesting to look at features that were useful. PhD C said it was their old Munich, a loudness-based spectrum on mel scale twenty critical bands and then loudness. PhD C said it was twenty-four features after stating the four additional features.", + "title": "Discussion on the Feature Issue", + "relevant_turns": [ + [ + 71, + 81 + ], + [ + 108, + 114 + ], + [ + 136, + 145 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "feature", + "speaker": "Professor G , PhD C" + }, + "summary": "PhD C spoke about 4 additional features which were energy, loudness, modified loudness, and zero-crossing rate. Professor G said still on the features they had twenty-four features. Professor G added that a lot of the twenty-four features were spectral features.", + "title": "Discussion About the Twenty-four Features", + "relevant_turns": [ + [ + 71, + 81 + ], + [ + 108, + 114 + ], + [ + 136, + 145 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "silence", + "speaker": "Professor G , PhD C" + }, + "summary": "Professor G talked of the suggestions that came up in a brief meeting in Spain with Malono Pardo and Javier, and suggested starting what they had before but added into the non-silence boundaries. PhD C talked about the HMM-based system with Gaussian mixtures for speech and nonspeech, and the system used only one Gaussian for silence and another Gaussian for speech.", + "title": "Gaussian Used by the System", + "relevant_turns": [ + [ + 65, + 69 + ], + [ + 89, + 91 + ], + [ + 73, + 75 + ], + 121 + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "high", + "topic": "silence", + "speaker": "Professor G , PhD C" + }, + "summary": "PhD C talked of doing some training on one dialogue transcribed, they also did a nonspeech transcription. Professor G said that as a simplification Javier originally looked for the speaker change points using silence as a putative speaker change point, and suggested broadening it a bit, instead of using silence as a putative change point. PhD C said one could specify the minimum length of speech and silence portions that one wanted, and spoke of the modifications on the parameters. Professor G spoke of a simplification and only used silence as a speaker change point.", + "title": "PhD C's Talk About Javier's Work", + "relevant_turns": [ + [ + 65, + 69 + ], + [ + 89, + 91 + ], + [ + 73, + 75 + ], + 121 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "loud", + "speaker": "PhD C" + }, + "summary": "PhD C said that quiet speakers in the mix were one thing and it was the reason for adding more mixtures for the speech and PhDC saw that there were two different types of speakers. PhD C talked about doing two mixtures and stated what the two mixtures were.", + "title": "PhD C's Findings on the Type of Speakers", + "relevant_turns": [ + [ + 96, + 119 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "high", + "topic": "loud", + "speaker": "PhD C" + }, + "summary": "PhD C spoke of adding two mixtures and said that there were loudly speaking speakers and quietly speaking speakers, the two mixtures PhD C did were one for the loud and another for the quiet speakers. PhD C said doing it for five minutes on one dialogue was enough to train the system, the system adapted while running. PhD C further talked of their old Munich, a loudness-based spectrum on the mel scale.", + "title": "PhD C's Findings on the Type of Speakers", + "relevant_turns": [ + [ + 96, + 119 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "interface", + "speaker": "Postdoc F" + }, + "summary": "Postdoc F talked about the other thing Thilo and Dave Gelbert were involved with and explained they had a meeting, regarding the representation of overlaps at present because of the limitations of the interface they were using. According to Postdoc F overlaps were not being encoded by the transcribers in as complete and detailed a way as may be desired in the corpus ultimately. Postdoc F further said they did not have start and endpoints at each point where there was an overlap. They just had the overlaps encoded in a simple bin. At the meeting, they were entertaining how they might either expand the interface or find other tools that already did what would be useful.", + "title": "Postdoc F's Meeting with Thilo and Dave Gelbert", + "relevant_turns": [ + [ + 154, + 158 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "high", + "topic": "interface", + "speaker": "Postdoc F" + }, + "summary": "Postdoc F; Because you can have multiple channels, there's a single timeline, it's very clear, flexible, and all those nice things. OK. So, um, I spoke I had a meeting with Dave Gelbart and he had, uh, excellent ideas on how the interface could be modified to do this kind of representation. But, um, in the meantime you were checking into the existence of already, um, existing interfaces which might already have these properties. So, do you wanna say something about that?", + "title": "Postdoc F's Meeting with Thilo and Dave Gelbert", + "relevant_turns": [ + [ + 154, + 158 + ] + ] + } + ], + "source": [ + "Grad A : OK . We seem to be recording .", + "Professor G : Alright !", + "Grad A : So , sorry about not {disfmarker}", + "Professor G : We 're not crashing .", + "PhD D : Number four .", + "Grad A : not pre - doing everything . The lunch went a little later than I was expecting , Chuck .", + "PhD E : Hmm ?", + "Professor G : OK .", + "PhD B : Chuck was telling too many jokes , or something ?", + "Grad A : Yep . Pretty much .", + "PhD E : Yeah .", + "Professor G : OK . {vocalsound} Does anybody have an agenda ?", + "Grad A : No .", + "Postdoc F : Well , I 'm {disfmarker} I sent a couple of items . They 're {disfmarker} they 're sort of practical .", + "Professor G : I thought {pause} somebody had .", + "Postdoc F : I don't know if you 're {disfmarker}", + "Professor G : Yeah , that 's right .", + "Postdoc F : if {disfmarker} if that 's too practical for what we 're {pause} focused on .", + "Grad A : I mean , we don't want anything too practical .", + "Professor G : Yeah , we only want th useless things .", + "Grad A : Yeah , that would be {disfmarker}", + "Professor G : Yeah . No , why don't we talk about practical things ?", + "Postdoc F : OK .", + "Professor G : Sure .", + "Postdoc F : Well , um , I can {pause} give you an update on the {pause} transcription effort .", + "Professor G : Great .", + "Postdoc F : Uh , maybe {nonvocalsound} raise the issue of microphone , uh , um procedures with reference to the {pause} cleanliness of the recordings .", + "Professor G : OK , transcription , uh , microphone issues {disfmarker}", + "Postdoc F : And then maybe {nonvocalsound} ask , th uh , these guys . The {disfmarker} we have great {disfmarker} great , uh , p steps forward in terms of the nonspeech - speech pre - segmenting of the signal .", + "Professor G : OK .", + "Grad A : Well , we have steps forward .", + "PhD C : Yeah .", + "Postdoc F : Well , it 's a {disfmarker} it 's a big improvement .", + "PhD C : I would prefer this .", + "Professor G : Yes . Yeah , well . OK . Uh {disfmarker}", + "PhD D : We talk about the {disfmarker} {vocalsound} the results of", + "Professor G : You have some {disfmarker} Yeah .", + "Grad A : I have a little bit of IRAM stuff", + "Professor G : OK .", + "PhD D : use {disfmarker}", + "Grad A : but {pause} I 'm not sure if that 's of general interest or not .", + "Professor G : Uh , bigram ?", + "Grad A : IRAM .", + "PhD D : IRAM .", + "Professor G : IRAM .", + "Grad A : IRAM , bigram ,", + "Professor G : Well , m maybe .", + "PhD D : Bi - Bigram .", + "Grad A : you know .", + "Professor G : Yeah , let 's {disfmarker} let 's see where we are at three - thirty .", + "PhD B : Hmm .", + "Professor G : Um {disfmarker}", + "PhD B : Since , uh {disfmarker} since I have to leave as usual at three - thirty , can we do the interesting stuff first ?", + "Postdoc F : I beg your pardon ?", + "Professor G : Well {disfmarker}", + "PhD C : Which is {disfmarker} ?", + "Grad A : What 's the interesting stuff ?", + "Postdoc F : I beg your pardon ?", + "PhD D : Yeah .", + "Professor G : Yeah . Th - now you get to tell us what 's the interesting part .", + "PhD E : Please specify .", + "Professor G : But {disfmarker}", + "PhD B : Well , uh , I guess the work that 's been {pause} done on segmentation would be most {disfmarker}", + "PhD C : Yeah .", + "Postdoc F : I think that would be a good thing to start with .", + "PhD B : Yeah .", + "Professor G : OK . Um , and , um , {vocalsound} the other thing , uh , which I 'll just say very briefly that maybe relates to that a little bit , which is that , um , uh , one of the suggestions that came up in a brief meeting I had the other day when I was in Spain with , uh , Manolo Pardo and {vocalsound} Javier , uh , Ferreiros , who was {pause} here before , was , um , why not start with what they had before but add in the non - silence boundaries . So , in what Javier did before when they were doing , um {disfmarker} h he was looking for , uh , speaker change {pause} points .", + "PhD D : Mm - hmm .", + "Professor G : Um . As a simplification , he originally did this only using {pause} silence as , uh , a {pause} putative , uh , speaker change point .", + "PhD C : Yeah .", + "Professor G : And , uh , he did not , say , look at points where you were changing broad sp uh , phonetic class , for instance . And for Broadcast News , that was fine . Here obviously it 's not .", + "PhD D : Yeah .", + "Professor G : And , um , so one of the things that they were pushing in d in discussing with me is , um , w why are you spending so much time , uh , on the , uh , feature issue , uh , when perhaps if you sort of deal with what you were using before", + "PhD D : Uh - huh .", + "Professor G : and then just broadened it a bit , instead of just ta using silence as putative change point also {disfmarker} ?", + "PhD D : Nnn , yeah .", + "Professor G : So then you 've got {disfmarker} you already have the super - structure with Gaussians and H - you know , simple H M Ms and so forth . And you {disfmarker} you might {disfmarker} So there was a {disfmarker} there was a little bit of a {disfmarker} a {disfmarker} a {disfmarker} a difference of opinion because I {disfmarker} I thought that it was {disfmarker} it 's interesting to look at what features are useful .", + "PhD D : Yeah .", + "Professor G : But , uh , on the other hand I saw that the {disfmarker} they had a good point that , uh , if we had something that worked for many cases before , maybe starting from there a little bit {disfmarker} Because ultimately we 're gonna end up {vocalsound} with some s su kind of structure like that ,", + "PhD D : Yeah .", + "Professor G : where you have some kind of simple HMM and you 're testing the hypothesis that , {vocalsound} uh , there is a change .", + "PhD D : Yeah .", + "Professor G : So {disfmarker} so anyway , I just {disfmarker} reporting that .", + "PhD D : OK .", + "Professor G : But , uh , uh {disfmarker} So . Yeah , why don't we do the speech - nonspeech discussion ?", + "Postdoc F : Yeah . Do {disfmarker} I {disfmarker} I hear {disfmarker} you {disfmarker} you didn't {disfmarker}", + "PhD C : Speech - nonspeech ? OK .", + "Postdoc F : Uh - huh . Yeah .", + "PhD C : Um , so , uh , what we basically did so far was using the mixed file to {disfmarker} to detect s speech or nonspeech {pause} portions in that .", + "Professor G : Mm - hmm .", + "PhD C : And what I did so far is I just used our old Munich system , which is an HMM - ba based system with Gaussian mixtures for s speech and nonspeech . And it was a system which used only one Gaussian for silence and one Gaussian for speech . And now I added , uh , multi - mixture possibility for {disfmarker} {vocalsound} for speech and nonspeech .", + "Professor G : Mm - hmm . Mm - hmm .", + "PhD C : And I did some training on {disfmarker} on one dialogue , which was transcribed by {disfmarker} Yeah . We {disfmarker} we did a nons s speech - nonspeech transcription .", + "PhD D : Jose .", + "PhD C : Adam , Dave , and I , we did , for that dialogue and I trained it on that . And I did some pre - segmentations for {disfmarker} for Jane . And I 'm not sure how good they are or what {disfmarker} what the transcribers say . They {disfmarker} they can use it or {disfmarker} ?", + "Postdoc F : Uh , they {disfmarker} they think it 's a terrific improvement . And , um , it real it just makes a {disfmarker} a world of difference .", + "Professor G : Hmm .", + "Postdoc F : And , um , y you also did some something in addition which was , um , for those in which there {nonvocalsound} was , uh , quiet speakers in the mix .", + "PhD C : Yeah . Uh , yeah . That {disfmarker} that was one {disfmarker} one {disfmarker} one thing , uh , why I added more mixtures for {disfmarker} for the speech . So I saw that there were loud {disfmarker} loudly speaking speakers and quietly speaking speakers .", + "Professor G : Mm - hmm .", + "PhD C : And so I did two mixtures , one for the loud speakers and one for the quiet speakers .", + "Grad A : And did you hand - label who was loud and who was quiet , or did you just {disfmarker} ?", + "PhD C : I did that for {disfmarker} for five minutes of one dialogue", + "Grad A : Right .", + "PhD C : and that was enough to {disfmarker} to train the system .", + "PhD B : W What {disfmarker} ?", + "PhD D : Yeah .", + "PhD C : And so it {disfmarker} it adapts , uh , on {disfmarker} while running . So .", + "PhD B : What kind of , uh , front - end processing did you do ?", + "PhD C : Hopefully .", + "PhD D : OK .", + "PhD C : It 's just our {disfmarker} our old Munich , uh , loudness - based spectrum on mel scale twenty {disfmarker} twenty critical bands and then loudness .", + "PhD B : Mm - hmm .", + "PhD C : And four additional features , which is energy , loudness , modified loudness , and zero crossing rate . So it 's twenty - four {disfmarker} twenty - four features .", + "PhD B : Mmm .", + "Professor G : Mm - hmm .", + "Postdoc F : And you also provided me with several different versions ,", + "PhD C : Yeah .", + "Postdoc F : which I compared .", + "PhD C : Yeah .", + "Postdoc F : And so you change {nonvocalsound} parameters . What {disfmarker} do you wanna say something about the parameters {nonvocalsound} that you change ?", + "PhD C : Yeah . You can specify {vocalsound} the minimum length of speech or {disfmarker} and silence portions which you want . And so I did some {disfmarker} some modifications in those parameters , basically changing the minimum {disfmarker} minimum {pause} length for s for silence to have , er to have , um {disfmarker} yeah {disfmarker} to have more or less , uh , silence portions in inserted . So .", + "Grad A : Right . So this would work well for , uh , pauses and utterance boundaries and things like that .", + "PhD D : Yeah .", + "PhD C : Yeah . Yeah .", + "Grad A : But for overlap I imagine that doesn't work at all ,", + "PhD C : Yeah .", + "PhD D : Yeah .", + "Grad A : that you 'll have plenty of s sections that are {disfmarker}", + "PhD C : Yeah .", + "PhD D : Yeah .", + "PhD C : That 's it . Yeah .", + "Postdoc F : Mm - hmm , mm - hmm .", + "PhD D : Yeah .", + "Grad A : But {disfmarker}", + "Postdoc F : That 's true . But {nonvocalsound} it {disfmarker} it saves so much time {disfmarker} the {disfmarker} the {nonvocalsound} transcribers", + "Professor G : Um {disfmarker}", + "Grad A : Yep .", + "Postdoc F : just enormous , enormous savings . Fantastic .", + "Professor G : That 's great . Um , just qu one quickly , uh , still on the features . So {vocalsound} you have these twenty - four features .", + "PhD C : Yeah .", + "Professor G : Uh , a lot of them are spectral features . Is there a {disfmarker} a transformation , uh , like principal components transformation or something ?", + "PhD C : No .", + "Grad A : Yeah . It was IS two .", + "PhD C : No . W w we {disfmarker} originally we did that", + "Professor G : Just {disfmarker}", + "PhD C : but we saw , uh , when we used it , uh , f for our close - talking microphone , which {disfmarker} yeah , for our {disfmarker} for our recognizer in Munich {disfmarker} we saw that w it 's {disfmarker} it 's not {disfmarker} it 's not so necessary . It {disfmarker} it works as well f with {disfmarker} with {disfmarker} without , uh , a LDA or something .", + "Professor G : OK . OK . No , I was j {pause} curious .", + "PhD C : Yeah .", + "Postdoc F : Mm - hmm .", + "Professor G : Yeah , I don't think it 's a big deal for this application ,", + "PhD C : Yeah .", + "PhD D : Right .", + "Professor G : but {disfmarker} but {disfmarker} Yeah , it 's a {disfmarker}", + "Postdoc F : Mm - hmm . OK . But then there 's another thing that also Thilo 's involved with , which is , um {disfmarker} OK , and {disfmarker} and also Da - Dave Gelbart . So there 's this {disfmarker} this problem of {disfmarker} and w and {disfmarker} so we had this meeting . Th - the {nonvocalsound} {disfmarker} also Adam , before the {disfmarker} the {disfmarker} before you went away . Uh we , um {disfmarker} regarding the representation {nonvocalsound} of overlaps , because at present , {nonvocalsound} {vocalsound} um , because {nonvocalsound} of the limitations of {vocalsound} th the interface we 're using , overlaps are , uh , not being {nonvocalsound} encoded by {nonvocalsound} the transcribers in as complete {nonvocalsound} and , uh , detailed a way as it might be , and as might be desired {disfmarker} I think would be desired in the corpus ultimately .", + "Professor G : Mm - hmm .", + "Postdoc F : So we don't have start and end points {nonvocalsound} at each point where there 's an overlap . We just have the {disfmarker} the {nonvocalsound} overlaps {nonvocalsound} encoded in a simple bin . Well , OK . So {nonvocalsound} @ @ the limits of the {nonvocalsound} over of {disfmarker} of the interface are {vocalsound} such that we were {disfmarker} at this meeting we were entertaining how we might either expand {nonvocalsound} the {disfmarker} the {vocalsound} interface or find other tools which already {pause} do what would be useful . Because what would ultimately be , um , ideal in my {disfmarker} my view and I think {disfmarker} I mean , I had the sense that it was consensus , is that , um , a thorough - going musical score notation would be {nonvocalsound} the best way to go . Because {nonvocalsound} you can have multiple channels , there 's a single time - line , it 's very clear , flexible , and all those nice things .", + "Professor G : Mm - hmm .", + "Postdoc F : OK . So , um , um , I spoke {disfmarker} I had a meeting with Dave Gelbart on {disfmarker} on {disfmarker} and he had , uh , excellent ideas on how {pause} the interface could be {pause} modified to {disfmarker} to do this kind of representation . But , um , he {disfmarker} in the meantime you were checking into the existence of already , um , existing interfaces which might already have these properties . So , do you wanna say something about that ?", + "PhD C : Yes . Um , I {vocalsound} talked with , uh , Munich guys from {disfmarker} from Ludwi - Ludwig Maximilians University , who do a lot of transcribing and transliterations .", + "Professor G : Mm - hmm .", + "PhD C : And they basically said they have {disfmarker} they have , uh , a tool they developed {pause} themselves and they can't give away , uh , f it 's too error - prone , and had {disfmarker} it 's not supported , a a a and {disfmarker}", + "Professor G : Yeah .", + "PhD C : But , um , Susanne Bur - Burger , who is at se CMU , he wa who was formally at {disfmarker} in Munich and w and is now at {disfmarker} with CMU , she said she has something which she uses to do eight channels , uh , trans transliterations , eight channels simultaneously ,", + "Professor G : Excuse me .", + "PhD C : but it 's running under Windows .", + "Postdoc F : Under Windows .", + "PhD C : So I 'm not sure if {disfmarker} if {disfmarker} if we can use it .", + "Postdoc F : Mm - hmm .", + "PhD C : She said she would give it to us .", + "Postdoc F : Mm - hmm .", + "PhD C : It wouldn't be a problem . And I 've got some {disfmarker} some kind of manual {pause} down in my office .", + "Grad A : Well , maybe we should get it and if it 's good enough we 'll arrange Windows machines to be available ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 36, + "turns": [ + 204, + 237 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "feasibility , multipurpose , remote control", + "speaker": "Project Manager" + }, + "summary": "Project Manager said that got one at home, and that was pretty handy when they had a DVD or video recorder, then thought that if they could put different devices on one remote control it was easier as well.", + "title": "Project Manager Thoughts About Multipurpose Remote Control", + "relevant_turns": [ + [ + 10, + 22 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "feasibility , multipurpose , remote control", + "speaker": "Project Manager" + }, + "summary": "Project Manager said it was handy, but with different devices on the remote, was easier by a lot.", + "title": "Project Manager Thoughts About Multipurpose Remote Control", + "relevant_turns": [ + [ + 10, + 22 + ] + ] + } + ], + "source": [ + "Project Manager : Nice . Okay . {vocalsound} But so mm does everybody has um experiences with uh remote controls , and I mean not the ordinary mote controls , but also a little bit different ones ? Like you can use for other ?", + "Marketing : {vocalsound}", + "User Interface : Mm . Oh really ?", + "Project Manager : No ?", + "User Interface : Huh .", + "Project Manager : You ? {vocalsound}", + "User Interface : It's a {disfmarker}", + "Industrial Designer : No , me neither .", + "Marketing : Well , we have a kind of broad T_V_ at home , and a D_V_D_ player , so we got like a lot of remote controls , one for the T_V_ , one for the video recorder , one for the D_V_D_ player .", + "Project Manager : Ah yeah .", + "Marketing : And I think it's {disfmarker} it would be best to just make one remote control that can operate them all .", + "Project Manager : Yep . Yeah", + "User Interface : Sure . Yeah .", + "Project Manager : I've I've got one at home . And you can uh program I think eight different devices in it , and you can use it for your television , anything else .", + "User Interface : Okay , yeah . Yeah .", + "Project Manager : And it also operates on infra-red , so you have to got the little device inside your room , and then you can operate it from the third or th or second floor .", + "User Interface : Okay , yeah .", + "Marketing : Oh", + "Project Manager : So that's pretty handy when you have a video recorder or D_V_D_ player downstairs and you've got a link to your T_V_ on the second floor . So that's a pretty handy um", + "Marketing : really .", + "User Interface : Hmm . Oh . Mm-hmm .", + "Marketing : Yeah .", + "Project Manager : thing . {vocalsound} Um but only the I think that if you can put different kind of devices in one remote control , it makes it a lot easier as well . It's uh {disfmarker}", + "Marketing : Yeah .", + "User Interface : Oh .", + "Project Manager : That's good to remember .", + "Marketing : So I think you can take minutes again .", + "Project Manager : Yeah , that's nice , I think . {vocalsound}", + "Marketing : Since it's your job .", + "Project Manager : So we've {disfmarker} we want different functions", + "Marketing : Yeah .", + "Project Manager : uh and we can maybe see if we can do something with the infra-red . But I don't know if that will exceed the production costs . So that uh that's something we have to find out , I think .", + "User Interface : Mm .", + "Marketing : Yeah . But that would be really good if we could do that . {vocalsound}" + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 18, + "turns": [ + 103, + 120 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "sectors , live discussion", + "speaker": "Eluned Morgan AM" + }, + "summary": "Eluned Morgan AM said they had been discussing with people in rural areas directly, the need to convince the FE sector to be more responsive to the demand, they had put \u00a310 million to take them serious about their aim.", + "title": "Eluned Morgan AM's Aims", + "relevant_turns": [ + [ + 5, + 7 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "high", + "specificity": "normal", + "topic": "sectors , live discussion", + "speaker": "Eluned Morgan AM" + }, + "summary": "They had been discussing to convince the FE sector to be quicker and more responsive, ensuring employers got what they were asking for.", + "title": "Eluned Morgan AM's Aims", + "relevant_turns": [ + [ + 5, + 7 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "employability programme , impact , sectors", + "speaker": "Eluned Morgan AM" + }, + "summary": "Eluned Morgan AM said as part of the employability programme, asked what would be the impact in some areas such as health or economy, focus on sectors that would be likely to suffer the worst impact if the worst happened.", + "title": "Eluned Morgan AM's Employability Programme", + "relevant_turns": [ + 1, + 3 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "employability programme , impact , sectors", + "speaker": "Eluned Morgan AM" + }, + "summary": "Eluned Morgan AM said as part of the employability programme, asked every member of the Cabinet what would be the impact in areas such as health or economy, important to collaborate doing the analysis through the regional skills partnerships, facing the greatest risk, focusing on sectors that would be likely to suffer the worst impact if the worst happened.", + "title": "Eluned Morgan AM's Employability Programme", + "relevant_turns": [ + 1, + 3 + ] + } + ], + "source": [ + "Llyr Gruffydd AM : Talking about the impact on the wider economy, on the point you made earlier that it's not just the direct effect on these institutions, but also on the businesses that they engage with, that is a concern in this context, that means, of course, that there is a lot of pressure in this context on the work that other departments in the Government are doing, because perhaps they are the ones dealing with some of this. So, could you tell us a little bit about how you're working with Ministers and Cabinet Secretaries and other departments within the Government to safeguard these interests?", + "Eluned Morgan AM : So, as part of the employability programme, I have started going round every member of the Cabinet to ask what the impact will be on them\u2014for example, in health, and, certainly, the economy, but here are many other areas. What's important for us is that we do collaborate and we do get this analysis, but we hope to do that on the ground through the regional skills partnerships. That's our way of ensuring that we can have an understanding, on the ground, of what's needed by employers. And so ensuring that people feed into that and that we respond to those requirements\u2014that's where we're focusing our work. So, we're asking, for example, health boards to ensure that they feed into the regional skills partnerships.", + "Llyr Gruffydd AM : Is there a danger that we're a little bit behind in this process? Because Brexit could be upon us in no time at all, and, of course, this work is still ongoing.", + "Eluned Morgan AM : Well, I have been pushing and ensuring that in the direct areas facing the greatest risk, and agriculture's one of those, of course\u2014. We have been pushing to see what we can do further, so, for example, I'm in the process of developing a policy on rural skills at present because I do think it's important that we do focus on those sectors that are likely to suffer the worst impact if the worst does happen. So, those preparations are in place as far as they can be, but, of course, it's very difficult without knowing to what extent it's going to impact on us.", + "Llyr Gruffydd AM : And each sector's running on its own timescale, I would presume. But, as you've mentioned rural skills, when do you foresee that that work will appear, and when will plans or schemes or whatever you're intending to put in place see the light of day?", + "Eluned Morgan AM : Well, we hope during this term that that will be published or announced. So, certainly, it is something that we have been discussing with people in rural areas directly, with the colleges, to see what the provision is there and to what extent we need to expand that, and to what extent we will need to change and move really quickly if there is no deal. That's something that I think we have to learn and we need to convince the FE sector about in terms of moving more quickly and to be more responsive to the demand that there is in the workplace.", + "Llyr Gruffydd AM : Yes, because there is the dilemma you touched on earlier about providing the skills that are required for the economy and providing the courses that are easy to fill. That is a live discussion across FE and HE, but you're confident that that discussion is taking place in a constructive and positive way and moving in the right direction.", + "Eluned Morgan AM : Well, it's helped that we've put \u00a310 million on the table, because they do understand now that we are serious about our aim of ensuring that they do respond to what employers are asking for. So that has helped a lot in terms of focus and, of course, we're in the middle of a review now as well in terms of how we fund FE, and that will certainly be a part of that.", + "Llyr Gruffydd AM : Okay, thanks.", + "Lynne Neagle AM : Thank you. Can I just go back\u2014?", + "Kirsty Williams AM : Sorry, Chair, could I just clarify something? The last question you asked me about\u2014", + "Lynne Neagle AM : I was just going to go back to that, yes.", + "Kirsty Williams AM : \u2014fees\u2014. Sorry. Of course, that is in the context of a 'no deal' scenario. There could be a scenario where there are reciprocal arrangements, so, if a deal was reached with the European Union that established the principle of reciprocal arrangements, then, obviously, the ability of the HE institutions to charge international fees would be curtailed. I just want to make that clear.", + "Lynne Neagle AM : If there's not that agreement\u2014", + "Kirsty Williams AM : If there's no deal\u2014", + "Lynne Neagle AM : \u2014then it will be open to universities to charge market-driven, international rates.", + "Kirsty Williams AM : Yes, that's right. Sorry, I just wanted to clarify. I should have made it very clear that the answer I gave was in the context of no deal, which is what we seem to be talking about mostly this morning, but if there was a deal to have reciprocal arrangements, then that ability, obviously, would be curtailed.", + "Lynne Neagle AM : Okay, thank you. Are there any other questions from Members? No. Okay, well, can I thank the Cabinet Secretary, the Minister and the officials for attending and for answering all our questions? We very much appreciate your time. As usual, you'll be sent a transcript to check for accuracy after the meeting. Thank you very much. Okay. Item 5, then, is papers to note. Members will see that there are 18 papers to note, so I'd like to suggest that we note them as a block, please, and just to flag that I would like to return to paper to note 18 when we go into private. Is that okay with everyone? Everyone happy to note those? Thank you. Item 6, then, can I propose, in accordance with Standing Order 17.42, that the committee resolves to meet in private for the remainder of the meeting and the whole of the meeting next week? Are Members content? Okay, thank you." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 2, + "turns": [ + 427, + 516 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "Pen", + "speaker": "Project Manager" + }, + "summary": "Project Manager presented on project evaluation of a digital pen during a meeting. The rest took notes on pen and paper. Marketing said digital pens were mostly for benefit of tracking.", + "title": "Presentation on a Digital Pen", + "relevant_turns": [ + [ + 0, + 11 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "Pen", + "speaker": "Project Manager" + }, + "summary": "Project Manager presented on project evaluation of a digital pen during a meeting.", + "title": "Digital Pen Design Discussion", + "relevant_turns": [ + [ + 0, + 11 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "Costs", + "speaker": "Project Manager" + }, + "summary": "Project Manager stated that the costs involved with the digital pen would be taken up with a different group since the prototype has been done. It would be hard to tell if ideas were expensive until you knew the costs.", + "title": "Costs of Designing a Digital Pen", + "relevant_turns": [ + [ + 46, + 55 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "Costs", + "speaker": "Project Manager" + }, + "summary": "Project Manager said the costs involved with the digital pen would be taken up with a different group since they had done a prototype. It was hard to tell if ideas were a bit too expensive or within the budget until you knew the costs.", + "title": "Costs Involved in Design of a Digital Pen", + "relevant_turns": [ + [ + 46, + 55 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "Paper", + "speaker": "User Interface" + }, + "summary": "Project Manager remarked that people made good use of the pen and paper during the start of the meeting. User Interface and Marketing had taken down notes. User Interface said it would have been nice to be able to transfer their paper notes onto the computer themselves.", + "title": "Taking Down Paper Notes", + "relevant_turns": [ + [ + 0, + 12 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "high", + "specificity": "normal", + "topic": "Paper", + "speaker": "User Interface" + }, + "summary": "User Interface said it would have been nice to transfer their paper notes onto the computer themselves.", + "title": "Transfer of Paper Notes to Computers", + "relevant_turns": [ + [ + 0, + 12 + ] + ] + } + ], + "source": [ + "Project Manager : Okay . Um don't know how lo much longer we've got . At least five minutes I think . Um quickly we'll pop onto project evaluation . Um . So , we've got these uh four criteria here for uh satisfaction . Does anybody want to um um do you have any opinions on any of them ? For example um {disfmarker} we'll work backwards I suppose . The ability to work on this project using the technology we've been presented with . Um {gap} people made good use of the uh pen and paper ?", + "User Interface : Yeah ,", + "Project Manager : I would say {gap} {disfmarker}", + "User Interface : got notes and doodles .", + "Marketing : {vocalsound} Wrote nearly a page ,", + "Industrial Designer : Yeah .", + "Marketing : but not {gap} .", + "Project Manager : I'm not quite sure what the advantage for us using a digital pen might be .", + "User Interface : Well I think this is a {disfmarker} I think the digital pen's mostly for the benefit of the uh", + "Marketing : I think tracking .", + "User Interface : of the researchers studying this . It's all p goes into their corpus .", + "Project Manager : It must {disfmarker}", + "User Interface : Though it would have been nice to be able to transfer the um transfer our n our paper notes onto the uh computer ourselves .", + "Marketing : Yeah , that woulda been pretty good .", + "Project Manager : It does seem like the paper's still a heavy consideration for taking notes . So maybe this is literally just a way around it . Um I dunno . How are people satisfied with the teamwork we've managed to display today ?", + "User Interface : {gap} .", + "Marketing : I'd {disfmarker}", + "Industrial Designer : Good .", + "Marketing : yeah I liked it , yeah .", + "Project Manager : Leadership . As much as can be leadered in this uh thing .", + "Industrial Designer : Very good .", + "Marketing : I li yeah , top marks .", + "Project Manager : Um last one we've got is room for creativity .", + "Marketing : {vocalsound} Well {vocalsound}", + "User Interface : {vocalsound} Unti uh uh until uh until accounts came along ,", + "Project Manager : Now , I think we got {disfmarker}", + "User Interface : {gap} squish .", + "Industrial Designer : We're burs bursting with creativity .", + "Marketing : yeah . {vocalsound}", + "Project Manager : {vocalsound} Yeah", + "Marketing : We we're not lacking in ideas , you know it's {disfmarker} that was not the problem .", + "Project Manager : I think of {disfmarker} in the end , ideas that can be used {gap} sadly {gap} . Not so much that we weren't full of ideas , but of ones that are gonna allow us to actually build the thing . It's a bit of a pity .", + "Marketing : Mm-hmm .", + "Project Manager : Um I would have to agree on that . I think we needed a larger budget .", + "Marketing : Yeah .", + "Project Manager : If you're going to aim your a um product maybe at the technological kind of sector , then you can afford to maybe jack the price up slightly from what it is .", + "User Interface : Yeah .", + "Project Manager : Because they will pay outrageous cash to {gap}", + "User Interface : Mm . I mean I th {vocalsound} I mean I think to r retaining the s the more sort of bio-morphic form in the articulation would gain more in s uh would gain more profit in sales than it would lose in uh", + "Project Manager : first on the market .", + "User Interface : in added expense .", + "Project Manager : Mm .", + "Industrial Designer : And the price was like {disfmarker} it was twice the w assembly cost . And would it have to be twice that ? It could be like coulda had the assembly {gap} like maybe fifteen Euro .", + "Project Manager : It could even {disfmarker}", + "Industrial Designer : We'll still settle for twenty five {vocalsound} .", + "Project Manager : That's true , yeah .", + "Industrial Designer : Maybe . {vocalsound}", + "Project Manager : Um I suppose these are all that will have to be taken up with a at a different group at I guess . As to a {gap} the costs involved . But I mean we've got a a prototype .", + "User Interface : Such as it is .", + "Project Manager : {vocalsound} So I dunno , I I think it's gone okay today , considering the information that we've had at our disposal , and um such .", + "Marketing : Maybe the counts wou woulda been better if we had a list or more {disfmarker} Yeah , to begin with .", + "Industrial Designer : In the beginning , yeah .", + "Marketing : Yeah .", + "Project Manager : Probably would have {disfmarker} mean we could have come up with a lot more solid design in the end ,", + "Marketing : Yeah .", + "Project Manager : I would have to agree . It is very much a pity to um get so far into the stage and then find out that maybe some of your ideas are just a bit too expensive . Always hard to tell until you know the costs . Um . Okay . Are the costs within budget ? Well ,", + "Industrial Designer : {vocalsound}", + "Project Manager : they are now that we have our slightly less than capable product .", + "Marketing : Okay .", + "Project Manager : We've evaluated it , and we can say that we came out with a value of three .", + "Marketing : Yeah .", + "User Interface : Actually I want th one thing I would say {disfmarker}", + "Project Manager : {vocalsound}", + "User Interface : I mean something that could perhaps be part of the product mm the um m product testing market research process would be to uh produce mock-ups of both versions and see just how much of a difference the over {gap} going over-budget um m would make to sales .", + "Project Manager : It's {disfmarker} yeah ?", + "Marketing : And like response from consumers {gap} .", + "User Interface : And we could even you know , market two versions .", + "Project Manager : {vocalsound}", + "Marketing : {vocalsound}", + "User Interface : Wee cheapie version with the nice bio-morphic rubber . {vocalsound}", + "Project Manager : And then the final one where you get to call it Hal .", + "User Interface : Yes .", + "Project Manager : But we'll go into that later .", + "Marketing : {vocalsound} Sure .", + "Project Manager : Right um", + "Marketing : {vocalsound}", + "Project Manager : is there anything else that anybody would like to to add , um {gap} anything they think that's not been covered , before I quickly write up a final report . Um I dunno , I mean we've got a product . We maybe aren't as happy with it as we'd like to be , but we've got something we think we can maybe stick onto the the market and sell . And of course something we have been avoiding talking about 'cause of we've no information is selling them directly to the manufacturers . There is a huge market .", + "Marketing : Yeah .", + "Project Manager : I mean we've briefly touched on it but we've no more knowledge then there's little we can say on that .", + "Marketing : Yeah .", + "User Interface : Mm .", + "Project Manager : Yeah . So um unless anybody's got anything they'd like to add , we can maybe round this up slightly earlier than we'd need to and then we can finish up the writing and such .", + "User Interface : And I can get my bus . Okay .", + "Project Manager : Yeah ?", + "Marketing : Yeah . Okay , let's {disfmarker}", + "Project Manager : Uh thank you for your participation .", + "Marketing : Thank you .", + "User Interface : Thank you .", + "Marketing : {vocalsound} I was actually kind of upset you know at the budget , and that we had to cut a lot of stuff . It's like man , we we can't have the locator thing . And s yeah that's just bad . Do you think maybe {gap} the prices were were made ?", + "Project Manager : That {gap} a question we can ask {gap} . {vocalsound}" + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 9, + "turns": [ + 463, + 594 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "disadvantages , ATLAS , other options", + "speaker": "" + }, + "summary": "Grad C thought that, if ATLAS was used, there would be a big learning curve. But later on, they could use its whole infrastructure. A flat file format wouldn't be very efficient, but easy to use. Perl could be used to read and construct an internal representation. P-file was an alternative known by them, but there used to be a problem, and it tended to be large.", + "title": "Use of ATLAS and its Alternatives", + "relevant_turns": [ + [ + 0, + 2 + ], + [ + 5, + 6 + ], + 14, + 21, + [ + 35, + 36 + ], + [ + 65, + 72 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "normal", + "topic": "disadvantages , ATLAS , other options", + "speaker": "" + }, + "summary": "Grad C hesitated about ATLAS, it was a big learning curve, and mentioned a flat file format might not be as efficient, but everyone could program in Perl. PhD A said Perl could be used to read it in and construct an internal representation, Grad C added that if you wanted to use the structured XML query language, user wouldn't program it in that language, if ATLAS was used as an external file representation, quick tools could be done, and they could use the ATLAS infrastructure. Grad C proposed to look at P-file, which they were familiar with and had experience with, the problem would be too large.", + "title": "Use of ATLAS and its Alternatives", + "relevant_turns": [ + [ + 0, + 2 + ], + [ + 5, + 6 + ], + 14, + 21, + [ + 35, + 36 + ], + [ + 65, + 72 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "disadvantages , ATLAS , other options", + "speaker": "Grad C" + }, + "summary": "Grad C hesitated about using ATLAS because it would mean a big learning curve, unlike P-files, which they already knew, but the problem of P-files was a big size. Grad C mentioned a flat file format might not be as good, but everyone could program and use Perl. Grad C said that if ATLAS was used as an external file representation, eventually they could use all the ATLAS infrastructure.", + "title": "Grad C's View on ATLAS and its Alternatives", + "relevant_turns": [ + 0, + 2, + 5, + 21, + 35, + 67, + 75 + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "fully", + "specificity": "high", + "topic": "disadvantages , ATLAS , other options", + "speaker": "Grad C" + }, + "summary": "Grad C; little hesitant, ATLAS and a database, big learning curve, just to get going; flat file format, program in Pearl; for Pearl, structured XML query language, set of tools, specify given the D-DDT DTD of the document, within a particular tag, particular text in it, particular value; user, wouldn't program it in this language, someone would build a tool that used that as a library, wouldn't have to construct the internal representations; ATLAS external file representation, rich enough, could do quick tools, use the whole ATLAS inter infrastructure; alternatives to P-file, already familiar with it; expertise; there's the learning-curve problem, two-gigabyte limit on the file system size.", + "title": "Grad C's View on ATLAS and its Alternatives", + "relevant_turns": [ + 0, + 2, + 5, + 21, + 35, + 67, + 75 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "disadvantages , ATLAS , other options", + "speaker": "PhD F" + }, + "summary": "PhD F agreed on the usage of a flat file format, and also liked the idea of using the ATLAS external file representation. PhD F mentioned the need to give a response for a word-level prosodic.", + "title": "PhD F's View on ATLAS and its Alternatives", + "relevant_turns": [ + [ + 5, + 6 + ], + [ + 22, + 24 + ], + [ + 35, + 36 + ], + 109 + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "normal", + "topic": "disadvantages , ATLAS , other options", + "speaker": "PhD F" + }, + "summary": "PhD F agreed on the usage of flat file format, which would not be very efficient, but might work because everyone could program in Perl. PhD F mentioned the need to give a response for a word-level prosodic, or at the segment level. PhD F suggested getting enough information on where they conditioned the location of features on information and liked the idea of using ATLAS external file representation, and stated the importance of the main sort of word-level.", + "title": "PhD F's View on ATLAS and its Alternatives", + "relevant_turns": [ + [ + 5, + 6 + ], + [ + 22, + 24 + ], + [ + 35, + 36 + ], + 109 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "ATLAS , learning curve", + "speaker": "Grad C" + }, + "summary": "Grad C wasn't sure about the whole framework of ATLAS because of the big learning curve, but Grad C thought that, using its external file representation was an option.", + "title": "Grad C's Opinion on ATLAS", + "relevant_turns": [ + [ + 0, + 2 + ], + 35, + [ + 65, + 67 + ], + 115 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "ATLAS , learning curve", + "speaker": "Grad C" + }, + "summary": "Grad C hesitated about choosing ATLAS because it would mean a big learning curve, and said that if ATLAS was used as an external file representation, it could be useful to do quick tools, just like in Perl, and after a while of learning, they could use all the ATLAS inter infrastructure.", + "title": "Grad C's Opinion on ATLAS", + "relevant_turns": [ + [ + 0, + 2 + ], + 35, + [ + 65, + 67 + ], + 115 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "p-file", + "speaker": "Grad C , PhD A" + }, + "summary": "Grad C proposed to look at P-file, which they were familiar with and had experience, the problem would be they got too large. Nevertheless, by extending the API, on file could be split up into smaller files.", + "title": "Grad C and PhD A's View on P-Files", + "relevant_turns": [ + [ + 65, + 67 + ], + [ + 72, + 75 + ], + 79, + [ + 92, + 97 + ], + 101, + 105 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "p-file", + "speaker": "Grad C , PhD A" + }, + "summary": "Grad C proposed looking at P-file as an alternative. PhD A mentioned there was an issue regarding the size, because of the bunch of libraries. Grad C said there was a two-gigabyte limit on the file system size, by extending the API, they could be split up into smaller files. PhD had worked with P-files.", + "title": "Grad C and PhD A's View on P-Files", + "relevant_turns": [ + [ + 65, + 67 + ], + [ + 72, + 75 + ], + 79, + [ + 92, + 97 + ], + 101, + 105 + ] + } + ], + "source": [ + "Grad C : I guess I 'm just a little hesitant to try to go whole hog on sort of the {disfmarker} the whole framework that {disfmarker} that NIST is talking about , with ATLAS and a database and all that sort of stuff ,", + "PhD F : So {disfmarker}", + "Grad C : cuz it 's a big learning curve , just to get going .", + "PhD D : Hmm .", + "PhD A : Hmm .", + "Grad C : Whereas if we just do a flat file format , sure , it may not be as efficient but everyone can program in Perl and {disfmarker} and use it .", + "PhD F : OK .", + "Grad C : Right ?", + "PhD A : But this is {disfmarker}", + "Grad C : So , as opposed to {disfmarker}", + "PhD A : I {disfmarker} I 'm still , um , {vocalsound} not convinced that you can do much at all on the text {disfmarker} on the flat file that {disfmarker} that {disfmarker} you know , the text representation . e Because the text representation is gonna be , uh , not reflecting the structure of {disfmarker} of your words and annotations . It 's just {disfmarker} it 's {disfmarker}", + "Grad C : Well , if it 's not representing it , then how do you recover it ? Of course it 's representing it .", + "PhD A : No . You {disfmarker} you have to {disfmarker} what you have to do is you have to basically {disfmarker}", + "Grad C : That 's the whole point .", + "PhD A : Y yeah . You can use Perl to read it in and construct a internal representation that is essentially a lattice . But , the {disfmarker} and then {disfmarker}", + "Grad C : OK .", + "PhD D : Yeah .", + "Grad C : Well , that was a different point .", + "PhD A : Right .", + "Grad C : Right ? So what I was saying is that {disfmarker}", + "PhD A : But that 's what you 'll have to do . Bec - be", + "Grad C : For Perl {disfmarker} if you want to just do Perl . If you wanted to use the structured XML query language , that 's a different thing . And it 's a set of tools {vocalsound} that let you specify given the D - DDT {disfmarker} DTD of the document , um , what sorts of structural searches you want to do . So you want to say that , you know , you 're looking for , um , a tag within a tag within a particular tag that has this particular text in it , um , and , uh , refers to a particular value . And so the point isn't that an end - user , who is looking for a query like you specified , wouldn't program it in this language . What you would do is , someone would build a tool that used that as a library . So that they {disfmarker} so that you wouldn't have to construct the internal representations yourself .", + "PhD F : Is a {disfmarker} See , I think the kinds of questions , at least in the next {disfmarker} to the end of this year , are {disfmarker} there may be a lot of different ones , but they 'll all have a similar nature . They 'll be looking at either a word - level prosodic , uh , an {disfmarker} a value ,", + "Grad C : Mm - hmm .", + "PhD F : like a continuous value , like the slope of something . But you know , we 'll do something where we {disfmarker} some kind of data reduction where the prosodic features are sort o uh , either at the word - level or at the segment - level ,", + "Grad C : Right .", + "PhD F : or {disfmarker} or something like that . They 're not gonna be at the phone - level and they 're no not gonna be at the frame - level when we get done with sort of giving them simpler shapes and things . And so the main thing is just being able {disfmarker} Well , I guess , the two goals . Um , one that Chuck mentioned is starting out with something that we don't have to start over , that we don't have to throw away if other people want to extend it for other kinds of questions ,", + "Grad C : Right .", + "PhD F : and being able to at least get enough , uh , information out on {disfmarker} where we condition the location of features on information that 's in the kind of file that you {pause} put up there . And that would {disfmarker} that would do it ,", + "Grad C : Yeah . I think that there are quick and dirty solutions ,", + "PhD F : I mean , for me .", + "Grad C : and then there are long - term , big - infrastructure solutions . And so {vocalsound} we want to try to pick something that lets us do a little bit of both .", + "PhD F : In the between , right . And especially that the representation doesn't have to be thrown away ,", + "Grad C : Um {disfmarker} Right .", + "PhD F : even if your tools change .", + "Grad C : And so it seems to me that {disfmarker} I mean , I have to look at it again to see whether it can really do what we want , but if we use the ATLAS external file representation , um , it seems like it 's rich enough that you could do quick tools just as I said in Perl , and then later on if we choose to go up the learning curve , we can use the whole ATLAS inter infrastructure ,", + "PhD F : Yeah . I mean , that sounds good to me .", + "Grad C : which has all that built in .", + "PhD F : I {disfmarker} I don't {disfmarker} So if {disfmarker} if you would l look at that and let us know what you think .", + "Grad C : Sure .", + "PhD F : I mean , I think we 're sort of guinea pigs , cuz I {disfmarker} I want to get the prosody work done but I don't want to waste time , you know , getting the {disfmarker}", + "PhD A : Oh , maybe {disfmarker}", + "PhD F : Yeah ?", + "PhD A : um {disfmarker}", + "Grad C : Well , I wouldn't wait for the formats , because anything you pick we 'll be able to translate to another form .", + "PhD A : Well {disfmarker} Ma well , maybe you should actually look at it yourself too to get a sense of what it is you 'll {disfmarker} you 'll be dealing with ,", + "PhD F : OK .", + "PhD A : because , um , you know , Adam might have one opinion but you might have another , so", + "Grad B : Yeah .", + "PhD F : Yeah , definitely .", + "PhD A : I think the more eyes look at this the better .", + "PhD F : Especially if there 's , e um {disfmarker} you know , if someone can help with at least the {disfmarker} the setup of the right {disfmarker}", + "Grad C : Hi , Jane .", + "PhD F : Oh , hi .", + "PhD A : Mmm .", + "PhD F : the right representation , then , i you know , I hope it won't {disfmarker} We don't actually need the whole full - blown thing to be ready ,", + "Grad C : Can you {disfmarker} Oh , well .", + "PhD F : so . Um , so maybe if you guys can look at it and sort of see what ,", + "Grad B : Yeah .", + "Grad C : Sure .", + "PhD F : um {disfmarker} I think we 're {disfmarker} we 're {disfmarker} {vocalsound} we 're actually just {disfmarker}", + "Grad C : We 're about done .", + "PhD F : yeah ,", + "Grad B : Hmm .", + "PhD F : wrapping up , but , um {disfmarker} Yeah , sorry , it 's a uh short meeting , but , um {disfmarker} Well , I don't know . Is there anything else , like {disfmarker} I mean that helps me a lot ,", + "Grad C : Well , I think the other thing we might want to look at is alternatives to P - file .", + "PhD F : but {disfmarker}", + "Grad C : I mean , th the reason I like P - file is I 'm already familiar with it , we have expertise here , and so if we pick something else , there 's the learning - curve problem . But , I mean , it is just something we developed at ICSI .", + "PhD A : Is there an {disfmarker} is there an IP - API ?", + "Grad C : And so {disfmarker} Yeah .", + "PhD A : OK .", + "Grad C : There 's an API for it . And , uh ,", + "PhD A : There used to be a problem that they get too large ,", + "Grad C : a bunch of libraries , P - file utilities .", + "PhD A : and so {pause} basically the {disfmarker} uh the filesystem wouldn't {disfmarker}", + "Grad C : Well , that 's gonna be a problem no matter what . You have the two - gigabyte limit on the filesystem size . And we definitely hit that with Broadcast News .", + "PhD A : Maybe you could extend the API to , uh , support , uh , like splitting up , you know , conceptually one file into smaller files on disk so that you can essentially , you know , have arbitrarily long f", + "Grad C : Yep . Most of the tools can handle that .", + "PhD A : Yeah .", + "Grad C : So that we didn't do it at the API - level . We did it at the t tool - level . That {disfmarker} that {disfmarker} most {disfmarker} many of them can s you can specify several P - files and they 'll just be done sequentially .", + "PhD A : OK .", + "Grad C : So .", + "PhD F : So , I guess , yeah , if {disfmarker} if you and Don can {disfmarker} if you can show him the P - file stuff and see .", + "Grad C : Sure .", + "PhD F : So this would be like for the F - zero {disfmarker}", + "Grad B : True .", + "Grad C : I mean , if you do \" man P - file \" or \" apropos P - file \" , you 'll see a lot .", + "Grad B : I 've used the P - file , I think . I 've looked at it at least , briefly , I think when we were doing s something .", + "PhD A : What does the P stand for anyway ?", + "Grad C : I have no idea .", + "Grad B : Oh , in there .", + "Grad C : I didn't de I didn't develop it . You know , it was {disfmarker} I think it was Dave Johnson . So it 's all part of the Quicknet library . It has all the utilities for it .", + "PhD A : No , P - files were around way before Quicknet . P - files were {disfmarker} were around when {disfmarker} w with , um , {vocalsound} RAP .", + "Grad C : Oh , were they ?", + "PhD D : Mm - hmm .", + "PhD A : Right ?", + "PhD F : It 's like the history of ICSI .", + "PhD A : You worked with P - files .", + "Grad C : Mm - hmm .", + "PhD F : Like {disfmarker}", + "PhD D : No .", + "PhD A : I worked with P - files .", + "PhD F : Yeah ?", + "PhD D : I don't remember what the \" P \" is , though .", + "PhD A : No .", + "Grad C : But there are ni they 're {disfmarker} The {pause} Quicknet library has a bunch of things in it to handle P - files ,", + "PhD A : Yeah .", + "Grad C : so it works pretty well .", + "PhD A :", + "PhD F : And that isn't really , I guess , as important as the {disfmarker} the main {disfmarker} I don't know what you call it , the {disfmarker} the main sort of word - level {disfmarker}", + "Grad C : Neither do I .", + "PhD D : Probably stands for \" Phil \" . Phil Kohn .", + "Grad C : It 's a Phil file ?", + "PhD D : Yeah . That 's my guess .", + "PhD F : Huh . OK . Well , that 's really useful . I mean , this is exactly the kind of thing that I wanted to settle . Um , so {disfmarker}", + "Grad C : Yeah , I 've been meaning to look at the ATLAS stuff again anyway .", + "PhD F : Great .", + "Grad C : So , just keep {disfmarker}", + "PhD F : Yeah . I guess it 's also sort of a political deci I mean , if {disfmarker} if you feel like that 's a community that would be good to tie into anyway , then it 's {disfmarker} sounds like it 's worth doing .", + "Grad C : Yeah , I think it {disfmarker} it w", + "PhD A : j I think there 's {disfmarker}", + "Grad C : And , w uh , as I said , I {disfmarker} what I did with this stuff {disfmarker} I based it on theirs . It 's just they hadn't actually come up with an external format yet . So now that they have come up with a format , it doesn't {disfmarker} it seems pretty reasonable to use it .", + "PhD A : Mmm .", + "Grad C : But let me look at it again .", + "PhD F : OK , great .", + "Grad C : As I said , that {disfmarker}", + "PhD F : Cuz we actually can start {disfmarker}", + "Grad C : There 's one level {disfmarker} there 's one more level of indirection and I 'm just blanking on exactly how it works . I gotta look at it again .", + "PhD F : I mean , we can start with , um , I guess , this input from Dave 's , which you had printed out , the channelized input . Cuz he has all of the channels , you know , with the channels in the tag and stuff like that .", + "Grad C : Yeah , I 've seen it .", + "PhD F : So that would be i directly ,", + "Grad C : Yep . Easy {disfmarker} easy to map ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 13, + "turns": [ + 62, + 98 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "price", + "speaker": "Project Manager , Marketing" + }, + "summary": "Project Manager said sorry about last meeting since they were supposed to discussed the financial aspect. He added that he knew both project plan and budget. Marketing asserted that they could sell well. Project Manager mentioned that the company would want to make at least fifty million Euro. Project Manager further suggested the remote control. Marketing gave the proposed sales and production price, plus the recent survey result.", + "title": "Financial Aspect of New Product", + "relevant_turns": [ + [ + 0, + 36 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "price", + "speaker": "Project Manager , Marketing" + }, + "summary": "Project Manager said sorry about last meeting since they were supposed to discuss the financial aspect. He added that he knew both project plan and budget. Marketing asserted that they could sell well. Project Manager mentioned that the company would want to make at least fifty million Euro and the price had to be reasonable from Sales. Project Manager further suggested a universal and slim remote control. Marketing said sales prices were to be twenty-five Euro and the production price to be twelve and a half Euro, prices that weren't exactly in the market. Marketing added recent surveys results showed that fifteen to thirty-five, eighty percent were willing to spend money on something fancy and trendy. Marketing ended that market price was reasonable but they could take a risk of making it more expensive.", + "title": "New Product Pricing Plans", + "relevant_turns": [ + [ + 0, + 36 + ] + ] + } + ], + "source": [ + "Project Manager : Yeah the the {disfmarker} I'm sorry because uh the last meeting we supposed to discuss about the financial thing .", + "User Interface : {vocalsound}", + "Marketing : {vocalsound}", + "Project Manager : Uh let me go quickly , maybe if I can go back {vocalsound} . I know the project plan and the budget . So I can close this , {gap} not sure . Was in uh {disfmarker} S This . So let me see where is this file .", + "User Interface : That's Christine's .", + "Project Manager : This is Christine . {vocalsound}", + "User Interface : And that's mine , I think .", + "Project Manager : That's yours , okay . Saving .", + "Marketing : {vocalsound} {gap}", + "User Interface : In modified .", + "Marketing : I don't know ,", + "Project Manager : Okay , uh", + "Marketing : I think verbally we can {disfmarker} we can pretty much sell .", + "Project Manager : I will {disfmarker} I will send you a mail , okay ? The project may be the the project aim , okay . At the end of the day , the company uh wants to make at least uh the fifty million Euro . Okay , and uh of course the price will be very reasonable on the the sales side . Okay , that maybe Eddie will talk to you about uh how much uh the price and uh what's uh {disfmarker} how much its cost for the manufacturing and how much it's going to be {disfmarker} we sell in the market . Okay . Then uh you can come back with your feedback . And I I have one {disfmarker} maybe the suggestion or opinion . This remote control , okay , it can be for like universal , to use for any T_V_ . Okay , and it will be slim , okay , and uh {disfmarker}", + "Industrial Designer : {vocalsound} Not fat ?", + "Project Manager : Not fat .", + "Industrial Designer : Not fat , huh .", + "Project Manager : Okay .", + "Industrial Designer : {vocalsound} Might be hard to find , though .", + "Project Manager : Yep . But let's try it , okay , with the different uh {disfmarker} the designs , okay , the functional designs .", + "Marketing : Hmm .", + "Industrial Designer : Oh , okay .", + "Project Manager : Okay ? So any other questions ?", + "Marketing : Uh from her side , I don't think uh there's too many more questions .", + "Project Manager : Okay . Thank you Christine for uh time being ,", + "Marketing : If you can come to the {disfmarker}", + "Project Manager : so then uh Ed , so can you tell about {disfmarker}", + "Marketing : Okay , from the marketing {disfmarker} yeah , from the marketing side , just to to give an idea what the management is looking for , I was looking for a a remote control to have a s", + "User Interface : S 'scuse me for one sec .", + "Marketing : I have a sales price of twenty-five Euro , with a production price of uh twelve and a half Euro . For what uh I think from what we're trying to find , we're tr we're looking for , I don't think that price is exactly in the market . Okay ?", + "Project Manager : Mm-hmm .", + "Marketing : I'll explain myself here now in the sense that uh in a {disfmarker} in the recent surveys , uh from the ages {disfmarker} fr from fifteen to thirty-five , eighty percent are willing to spend more money for something as fancy as trendy .", + "Project Manager : {vocalsound}", + "Marketing : Twenty-five Euros , uh that's that's a preson reasonable price . That's a market price right now . Now if we're gonna take a risk , and push this up a bit , make it more expensive ,", + "Project Manager : Yep .", + "Marketing : but give them added things that they don't have now ,", + "Project Manager : Yep ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "test", + "file_id": 1, + "turns": [ + 80, + 94 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "public interest test", + "speaker": "Vikki Howells AM , Barry Hughes" + }, + "summary": "Vikki Howells AM asked Barry Hughes about the factors that the CPS would considerate when applying the public interest test. Barry Hughes replied that if the defence of reasonable chastisement didn't apply, the stage of public interest test would apply after a sequence of three offences. Barry Hughes also said that the application of the public interest test tried to have an approach that was proportionate to the offending.", + "title": "Barry Hughes' View on Public Interest Test", + "relevant_turns": [ + [ + 1, + 4 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "high", + "specificity": "high", + "topic": "public interest test", + "speaker": "Vikki Howells AM , Barry Hughes" + }, + "summary": "Vikki Howells AM inquired about the factors that the CPS would be taking into consideration when applying the public interest test. Barry Hughes answered that the defence of reasonable chastisement applied for isolated events that didn't pass the evidential stage, but if that defence didn't apply at all, after a sequence of three offences, the public interest test would kick in, coming to the fore much more quickly. Barry Hughes also said that the essence of the public interest test application was about an approach that was proportionate to the offending.", + "title": "Barry Hughes' View on Public Interest Test", + "relevant_turns": [ + [ + 4, + 5 + ], + [ + 9, + 12 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "assault , child", + "speaker": "Barry Hughes" + }, + "summary": "Barry Hughes was asked about how the best interests of the child would be taken into account in considering whether to go forward with a prosecution. Barry Hughes explained that if there were an assault by someone outside the family upon a child, the views from the parents would be a main factor to investigate, but in circumstances where both parents, arguably, were the suspects, the police would help providing the information about how the child felt about what had happened. Barry Hughes agreed that a child couldn't consent to a serious assault.", + "title": "Child's Assault Explained by Barry Hughes", + "relevant_turns": [ + [ + 4, + 5 + ], + [ + 9, + 12 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "assault , child", + "speaker": "Barry Hughes" + }, + "summary": "Barry Hughes explained the investigation process in case of an assault upon a child, how the views of the parents would be a main factor if there was an assault by someone outside the family upon a child, and how the child's view would be the main lead in circumstances where both parents, arguably, were the suspects.", + "title": "Child's Assault Explained by Barry Hughes", + "relevant_turns": [ + [ + 4, + 5 + ], + [ + 9, + 12 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "consent , law", + "speaker": "Barry Hughes , Suzy Davies AM" + }, + "summary": "Suzy Davies AM said a child couldn't consent to assault. Barry Hughes agreed and added that a serious assault couldn't be consented, but explained how the law was less clear as to what you could consent to when it came to much lesser assaults, as the consent to a tattoo, for example. Suzy Davies AM agreed and said it was below a certain standard. Finally, Barry Hughes said the law regarding consent needed to be developed.", + "title": "Consent in Law's Matter According to Barry Hughes", + "relevant_turns": [ + [ + 9, + 12 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "consent , law", + "speaker": "Barry Hughes , Suzy Davies AM" + }, + "summary": "Suzy Davies AM said a child couldn't consent to assault. Barry Hughes agreed and added that a serious assault couldn't be consented, but there was less clarity on what you can consent to regarding lesser assaults, so it needed to be developed. Suzy Davies AM agreed.", + "title": "Consent in Law's Matter According to Barry Hughes", + "relevant_turns": [ + [ + 9, + 12 + ] + ] + } + ], + "source": [ + "Lynne Neagle AM : Okay. Okay, thank you. We've got some questions now specifically on prosecutions and potential alternatives from Vikki Howells.", + "Vikki Howells AM : Thank you, Chair. You've already touched quite a bit on the issue of the public interest test. Is there anything else you'd like to put on record about the factors that the CPS would be taking into consideration when applying the public interest test in respect of this Bill?", + "Barry Hughes : Can I give you an example, which might illustrate the way in which things could be different? This is one, which\u2014I give credit to Iwan for this, because he thought of it. If we take an adult with a small child\u2014say, a four-year-old\u2014in a supermarket, and the child is pulling cans off the shelves, it's quite annoying, and they keep doing it and keep doing it. The parent remonstrates, and the parent ends up finding that verbal admonishment is inadequate, and smacks the child lightly on the legs, which does the trick and the child stops. Presently, if someone in that supermarket were to report that to the police, I think the police would probably conclude that that is covered by the defence of reasonable chastisement. In other words, the evidential stage wouldn't be passed; you don't get on to consider the public interest. But if we have that same parent in there the following week, and you have the same happen again, presently, the defence would apply. Now, there comes a point in time when the defence stops applying. If that defence didn't apply at all, and we had a sequence of three offences, the public interest test would kick in, if I may put it like that, pretty quickly, because it would be repeated behaviour. So, that would be the distinction between how things are now and how they would be in the future, because the defence would not be available, so the public interest test would then come to the fore that much more quickly. So, when we apply the public interest test, the essence of it is about proportionality, and trying to come up with an approach that is proportionate to the offending. We look at the age of the offender, the age of the victim, we look at the circumstances, we look at the impact upon the victim, we look at the impact that's likely in relation to the suspect, and there is, within the code, a long list of matters that we take into account. Some of them are fairly obvious, such as previous convictions. If someone's got previous convictions for doing something wrong, it's more likely they're going to be prosecuted the next time. But there's no part of the law that says that prosecution will always follow. Mostly, it's reasonably obvious; the more serious an offence, the more likely you are to be prosecuted.", + "Vikki Howells AM : Thank you, that's really useful, and\u2014", + "Lynne Neagle AM : Just before you move on, can I ask you a question? This morning the committee was meeting with groups of parents who are opposed to the Bill and groups of parents who are for the Bill, and one of the parents this morning was querying where the interests of the child would come into the public interest test. Now, I've looked at the code and there is a section about impact on the victim. Can you just clarify for the record how the best interests of the child would be taken into account in considering whether to go forward with a prosecution?", + "Barry Hughes : Normally, if there were an assault by someone else upon a child, outside the family, we would tend to take views from the parents of that child. In circumstances where both parents, arguably, are the suspects, we probably wouldn't be asking them. We would find another way, and we would talk with the police to ensure that we are informed about how the child feels about what has happened. It may be that there are\u2014. I can foresee real difficulties in circumstances where we have parents who are separating where the children are being used, effectively, in divorce proceedings, for example, where we might have one parent saying there was a really bad impact upon the child and the other parent saying there wasn't. We'd want to find a way to cut through that to work out really from the police how does the child feel about that. So, we would tailor it to the circumstances of the particular incident to assess how the child feels about it. It's not determinative, nor is it determinative in cases where we prosecute for adult defendants inflicting some form of assault upon adult victims. It's not determinative but it is a factor that we take into account.", + "Lynne Neagle AM : Okay, thank you. Suzy, you've got a supplementary on that.", + "Suzy Davies AM : Yes. In the same session this morning I thought this was an interesting question raised by a parent, on the rights of the child side of things, where if a parent offers a child two forms of punishment because that child has done something that they know they shouldn't have, and they're given the option of, 'You can have a quick smack and a cwtch, or you're going to your bedroom for quarter of an hour', and the child is allowed to choose and the child chooses the smack, what happens then? I'm not offering any views on the fact that this choice has been given, but it was put to us today about how would that fall in the law once it were changed.", + "Barry Hughes : That's a really interesting question. There is a body of law that\u2014", + "Suzy Davies AM : A child can't consent to assault.", + "Barry Hughes : Yes, you can't consent to a serious assault, apart from in certain\u2014. The law is really quite difficult. So, for example, tattooing is a serious assault on one level, but you can consent to a tattoo. I can think of one case where a man branded his initials on a woman's buttocks, but she consented to it and the Court of Appeal held that they could consent to that. I can also think of a series of cases, which I won't get into here, that involve sadomasochistic behaviour between adults, some of which was really serious, and involved people willingly applying themselves to things that no sane person would do. And the Court of Appeal in that case, a case called Brown, said, 'No, that's going too far\u2014you can't consent to that.' Then, you may have seen there was a case from the midlands recently where a gentleman operating a tattoo parlour was also involved in body surgery\u2014splitting people's tongues. That went too far as well. So, there is again\u2014I referred before to the spectrum of offending, and there is a clear spectrum of offending that you can realistically consent to and then you get to offending you can't consent to. So, the law has considered that in some depth. I'm still not entirely clear, and I speak as a lawyer. When it comes to much lesser assaults, the law is more unclear as to what you can consent to.", + "Suzy Davies AM : Yes, because we're talking below a certain standard here as well. Okay.", + "Barry Hughes : As to what you can consent to, it's less clear. It would need to be developed.", + "Suzy Davies AM : Okay, thank you for that.", + "Lynne Neagle AM : Thank you. Vikki." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "test", + "file_id": 32, + "turns": [ + 678, + 864 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "deletions , improving the net", + "speaker": "" + }, + "summary": "PhD C observed that the number of deletion dramatically increased or doubled in the HM case and neural network doubled the number of deletions. Professor B suggested they focus on improving the net if the net was hurting at the moment.", + "title": "Impact of Deletions on Improving Net", + "relevant_turns": [ + [ + 0, + 13 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "deletions , improving the net", + "speaker": "" + }, + "summary": "PhD C said observed in the HM case that the number of deletion dramatically increases. Professor B suggested they needed to focus on improving the net.", + "title": "Impact of Deletions on Improving Net", + "relevant_turns": [ + [ + 0, + 13 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "neural net", + "speaker": "" + }, + "summary": "Professor B thought that maybe the noise subtraction was subtracting off speech and thinks it would be interesting to see what would happen having just the neural net without the LDA on - line normalization and maybe the results could not just be a little bit worse. He also said was disturbed in the resurgence of neural nets that happened in the eighties where a lot of people were just using them for all sort of things because neural nets were pretty easy to use without looking into all linear versions of them.", + "title": "Effects of Adding Neural Net", + "relevant_turns": [ + [ + 22, + 29 + ], + [ + 61, + 72 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "neural net", + "speaker": "" + }, + "summary": "Professor B said maybe the noise subtraction was subtracting off speech when adding the neural net and that running neural net only without side path with pure features wasn't helping at all until a second path was added in with the pure features and it would be interesting to see neural net without the LDA on - line normalization and the solution could be to focus on improving the net if the net really hurting at the moment.", + "title": "Effects of Adding Neural Net", + "relevant_turns": [ + [ + 22, + 29 + ], + [ + 61, + 72 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "noisy cases", + "speaker": "" + }, + "summary": "PhD C said that the most noisy cases were the distant microphone for testing and the professor B agreed and added that maybe the noise subtraction was subtracting off speech . He then added that the TIMIT noises sort of a range of noises and aren't much the stationary driving kind of noises. PhD C said that there was four noises which include Babble, car, train station and street.", + "title": "Causes of Noisy Cases", + "relevant_turns": [ + [ + 21, + 46 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "normal", + "topic": "noisy cases", + "speaker": "" + }, + "summary": "PhD C; The most noisy cases remains the distant microphone for testing; Professor B; maybe the noise subtraction was subtracting off speech; the TIMIT noises sort of a range of noises and they 're not so much the stationary driving kind of noises; PhD C; there's a car noise . So there's f just four noises", + "title": "Causes of Noisy Cases", + "relevant_turns": [ + [ + 21, + 46 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "deletion", + "speaker": "PhD C , PhD A" + }, + "summary": "PhD C said that he observed in the HM case that the number of deletion increases dramatically, when the neural network added it doubles the number of deletions. PhD A asked if the number stayed the same and PhD C answered that they stayed the same or a little bit lower.", + "title": "Impact of Neural Network on Deletions", + "relevant_turns": [ + [ + 0, + 10 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "deletion", + "speaker": "PhD C , PhD A" + }, + "summary": "PhD C said the number of deletion dramatically increases in HM case and adding neural network doubles deletions number; PhD A asked if Insertion substitutions stayed same", + "title": "Impact of Neural Network on Deletions", + "relevant_turns": [ + [ + 0, + 10 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "neural net features", + "speaker": "Professor B , PhD C" + }, + "summary": "Professor B wanted to know until a second path was put in with the pure features if the neural net wasn't helping at all. PhD C said that it was helping if the features were bad, Just plain P L Ps or M F. He also said that as soon as the LDA on - line normalization were added, all were doing similar enough things.", + "title": "Effect of Adding Neural Net", + "relevant_turns": [ + [ + 54, + 64 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "high", + "topic": "neural net features", + "speaker": "Professor B , PhD C" + }, + "summary": "Professor B asked if until they put the second path in with the pure features , the neural net wasn't helping at all; PhD C said It was helping if the features were bad.", + "title": "Effect of Adding Neural Net", + "relevant_turns": [ + [ + 54, + 64 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "lda", + "speaker": "PhD A , PhD D" + }, + "summary": "PhD A said that the Hub-five systems have been using LDA to run on features right before they train the models and said the LDA used by PhD D seems pretty far back in the process. PhD D answered that their LDA different from the LDA that PhD A talking about and that their LDA was for two dimensional tile applying only in time not in frequency.", + "title": "Applications of LDA", + "relevant_turns": [ + [ + 91, + 103 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "lda", + "speaker": "PhD A , PhD D" + }, + "summary": "PhD A said the Hub - five systems recently have been using LDA on the features right before they train the models, the LDA right there before the HM but said the PhD D LDA seems like it was pretty far back in the process. PhD D answered that their LDA was different from the one talked about and that their LDA was only in time, not in frequency for two dimensional tile and it was more like a filtering in time.", + "title": "Applications of LDA", + "relevant_turns": [ + [ + 91, + 103 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "feature", + "speaker": "Professor B , PhD A" + }, + "summary": "Professor B talked about feature where its like you have posterior combination but then get the features from that and use them as a feature combination with the other things. like feeding both discriminatively trained thing and other thing that was not to have a good set of features and by having both there, the discriminative stuff would help. PhD A suggested that it wouldn't be necessarily to do LDA on the non - tandem features because they would be doing something to them.", + "title": "Feature Combination", + "relevant_turns": [ + [ + 126, + 139 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "high", + "topic": "feature", + "speaker": "Professor B , PhD A" + }, + "summary": "Professor B; Let's feed both this discriminatively trained thing and something that's not; you have the posterior combination but then you get the features from that and use them as a feature combination with these these other things; by having them both there, the discriminative stuff gonna help you; PhD A; you wouldn't necessarily then want to do LDA on the non - tandem features because now you would be doing something to them.", + "title": "Feature Combination", + "relevant_turns": [ + [ + 126, + 139 + ] + ] + } + ], + "source": [ + "PhD C : Yeah , actually {vocalsound} to s eh , what I observed in the HM case is that the number of deletion dramatically increases . It {disfmarker} it doubles .", + "Professor B : Number of deletions .", + "PhD C : When I added the num the neural network it doubles the number of deletions . Yeah , so I don't you know {vocalsound} how to interpret that , but , mmm {disfmarker}", + "Professor B : Yeah . Me either .", + "PhD C : t", + "PhD A : And {disfmarker} and did {disfmarker} an other numbers stay the same ? Insertion substitutions stay the same ?", + "PhD C : They p stayed the same ,", + "PhD A : Roughly ?", + "PhD C : they {disfmarker} maybe they are a little bit uh , lower .", + "PhD A : Uh - huh .", + "PhD C : They are a little bit better . Yeah . But {disfmarker}", + "Professor B : Did they increase the number of deletions even for the cases that got better ?", + "PhD C : Mm - hmm .", + "Professor B : Say , for the {disfmarker} I mean , it {disfmarker}", + "PhD C : No , it doesn't .", + "Professor B : So it 's only the highly mismatched ?", + "PhD C : No .", + "Professor B : And it {disfmarker} Remind me again , the \" highly mismatched \" means that the {disfmarker}", + "PhD C : Clean training and {disfmarker}", + "Professor B : Uh , sorry ?", + "PhD C : It 's clean training {disfmarker} Well , close microphone training and distant microphone , um , high speed , I think .", + "Professor B : Close mike training {disfmarker}", + "PhD C : Well {disfmarker} The most noisy cases are the distant microphone for testing .", + "Professor B : Right . So {disfmarker} Well , maybe the noise subtraction is subtracting off speech .", + "PhD C : Separating . Yeah .", + "Professor B : Wh", + "PhD C : But {disfmarker} Yeah . I mean , but without the neural network it 's {disfmarker} well , it 's better . It 's just when we add the neural networks .", + "Professor B : Yeah , right .", + "PhD C : The feature are the same except that {disfmarker}", + "Professor B : Uh , that 's right , that 's right . Um {disfmarker}", + "PhD A : Well that {disfmarker} that says that , you know , the , um {disfmarker} the models in {disfmarker} in , uh , the recognizer are really paying attention to the neural net features .", + "PhD C : Yeah .", + "PhD A : Uh .", + "PhD C : Mm - hmm .", + "Professor B : But , yeah , actually {disfmarker} {nonvocalsound} the TIMIT noises {pause} are sort of a range of noises and they 're not so much the stationary driving kind of noises , right ? It 's {disfmarker} it 's pretty different . Isn't it ?", + "PhD C : Uh , there is a car noise . So there are f just four noises . Um , uh , \" Car \" , I think , \" Babble \" ,", + "PhD D : \" Babble . \"", + "PhD C : \" Subway \" , right ? and {disfmarker}", + "PhD D : \" Street \" or \" Airport \" or something .", + "PhD C : and {disfmarker} \" Street \" isn't {disfmarker}", + "PhD D : Or \" Train station \" .", + "PhD C : \" Train station \" , yeah .", + "PhD D : Yeah .", + "PhD C : So {disfmarker} it 's mostly {disfmarker} Well , \" Car \" is stationary ,", + "Professor B : Mm - hmm .", + "PhD C : \" Babble \" , it 's a stationary background plus some voices ,", + "Professor B : Mm - hmm .", + "PhD C : some speech over it . And the other two are rather stationary also .", + "Professor B : Well , I {disfmarker} I think that if you run it {disfmarker} Actually , you {disfmarker} maybe you remember this . When you {disfmarker} in {disfmarker} in the old experiments when you ran with the neural net only , and didn't have this side path , um , uh , with the {disfmarker} the pure features as well , did it make things better to have the neural net ?", + "PhD C : Mm - hmm .", + "Professor B : Was it about the same ? Uh , w i", + "PhD C : It was {disfmarker} b a little bit worse .", + "Professor B : Than {disfmarker} ?", + "PhD C : Than just the features , yeah .", + "Professor B : So , until you put the second path in with the pure features , the neural net wasn't helping at all .", + "PhD C : Mm - hmm .", + "Professor B : Well , that 's interesting .", + "PhD C : It was helping , uh , if the features are b were bad ,", + "Professor B : Yeah .", + "PhD C : I mean . Just plain P L Ps or M F", + "Professor B : Yeah .", + "PhD C : C Cs . as soon as we added LDA on - line normalization , and {vocalsound} all these things , then {disfmarker}", + "Professor B : They were doing similar enough things . Well , I still think it would be k sort of interesting to see what would happen if you just had the neural net without the side thing .", + "PhD C : Yeah ,", + "Professor B : And {disfmarker} and the thing I {disfmarker} I have in mind is , uh , maybe you 'll see that the results are not just a little bit worse .", + "PhD C : mm - hmm .", + "Professor B : Maybe that they 're a lot worse . You know ? And , um {disfmarker} But if on the ha other hand , uh , it 's , say , somewhere in between what you 're seeing now and {disfmarker} and {disfmarker} and , uh , what you 'd have with just the pure features , then maybe there is some problem of a {disfmarker} of a , uh , combination of these things , or correlation between them somehow .", + "PhD C : Mm - hmm .", + "Professor B : If it really is that the net is hurting you at the moment , then I think the issue is to focus on {disfmarker} on , uh , improving the {disfmarker} the net .", + "PhD C : Yeah ,", + "Professor B : Um .", + "PhD C : mm - hmm .", + "Professor B : So what 's the overall effe I mean , you haven't done all the experiments but you said it was i somewhat better , say , five percent better , for the first two conditions , and fifteen percent worse for the other one ? But it 's {disfmarker} but of course that one 's weighted lower ,", + "PhD C : Y yeah , oh . Yeah .", + "Professor B : so I wonder what the net effect is .", + "PhD C : I d I {disfmarker} I think it 's {disfmarker} it was one or two percent . That 's not that bad , but it was l like two percent relative worse on SpeechDat - Car . I have to {disfmarker} to check that . Well , I have {disfmarker} I will .", + "PhD D : Well , it will {disfmarker} overall it will be still better even if it is fifteen percent worse , because the fifteen percent worse is given like f w twenty - five {disfmarker} point two five eight .", + "Professor B : Right .", + "PhD C : Mm - hmm . Hmm .", + "Professor B : Right . So the {disfmarker} so the worst it could be , if the others were exactly the same , is four ,", + "PhD D : Is it like {disfmarker}", + "Professor B : and {disfmarker} and , uh , in fact since the others are somewhat better {disfmarker}", + "PhD D : Yeah , so it 's four . Is i So either it 'll get cancelled out , or you 'll get , like , almost the same .", + "Professor B : Uh .", + "PhD C : Yeah , it was {disfmarker} it was slightly worse .", + "PhD D : Slightly bad . Yeah .", + "PhD C : Um ,", + "Professor B : Yeah , it should be pretty close to cancelled out .", + "PhD D : Yeah .", + "PhD A : You know , I 've been wondering about something .", + "PhD C : Mm - hmm .", + "PhD A : In the , um {disfmarker} a lot of the , um {disfmarker} the Hub - five systems , um , recently have been using LDA . and {disfmarker} and they , um {disfmarker} They run LDA on the features right before they train the models . So there 's the {disfmarker} the LDA is {disfmarker} is right there before the H M", + "PhD D : Yeah .", + "PhD A : So , you guys are using LDA but it seems like it 's pretty far back in the process .", + "PhD D : Uh , this LDA is different from the LDA that you are talking about . The LDA that you {disfmarker} saying is , like , you take a block of features , like nine frames or something , {comment} and then do an LDA on it ,", + "PhD A : Yeah . Uh - huh .", + "PhD D : and then reduce the dimensionality to something like twenty - four or something like that .", + "PhD A : Yeah , you c you c you can .", + "PhD D : And then feed it to HMM .", + "PhD A : I mean , it 's {disfmarker} you know , you 're just basically i", + "PhD D : Yeah , so this is like a two d two dimensional tile .", + "PhD A : You 're shifting the feature space . Yeah .", + "PhD D : So this is a two dimensional tile . And the LDA that we are f applying is only in time , not in frequency {disfmarker} high cost frequency . So it 's like {disfmarker} more like a filtering in time , rather than doing a r", + "PhD A : Ah . OK . So what i what about , um {disfmarker} i u what i w I mean , I don't know if this is a good idea or not , but what if you put {disfmarker} ran the other kind of LDA , uh , on your features right before they go into the HMM ?", + "PhD D : Uh , it {disfmarker}", + "PhD C : Mm - hmm . No , actually , I think {disfmarker} i", + "PhD D : m", + "PhD C : Well . What do we do with the ANN is {disfmarker} is something like that except that it 's not linear . But it 's {disfmarker} it 's like a nonlinear discriminant analysis .", + "PhD A : Yeah . Right , it 's the {disfmarker} It 's {disfmarker} Right . The {disfmarker} So {disfmarker} Yeah , so it 's sort of like {disfmarker}", + "PhD C : But .", + "PhD A : The tandem stuff is kind of like i nonlinear LDA .", + "PhD C : Yeah . It 's {disfmarker}", + "PhD A : I g", + "PhD C : Yeah .", + "PhD A : Yeah .", + "Professor B : Yeah .", + "PhD A : But I mean , w but the other features that you have , um , th the non - tandem ones ,", + "PhD C : Uh . Mm - hmm . Yeah , I know . That {disfmarker} that {disfmarker} Yeah . Well , in the proposal , they were transformed u using PCA , but {disfmarker}", + "PhD A : Uh - huh .", + "PhD C : Yeah , it might be that LDA could be better .", + "Professor B : The a the argument i is kind of i in {disfmarker} and it 's not like we really know , but the argument anyway is that , um , uh , we always have the prob I mean , discriminative things are good . LDA , neural nets , they 're good .", + "PhD A : Yeah .", + "Professor B : Uh , they 're good because you {disfmarker} you {disfmarker} you learn to distinguish between these categories that you want to be good at distinguishing between . And PCA doesn't do that . It {disfmarker} PAC - PCA {disfmarker} low - order PCA throws away pieces that are uh , maybe not {disfmarker} not gonna be helpful just because they 're small , basically .", + "PhD A : Right .", + "Professor B : But , uh , the problem is , training sets aren't perfect and testing sets are different . So you f you {disfmarker} you face the potential problem with discriminative stuff , be it LDA or neural nets , that you are training to discriminate between categories in one space but what you 're really gonna be g getting is {disfmarker} is something else .", + "PhD A : Uh - huh .", + "Professor B : And so , uh , Stephane 's idea was , uh , let 's feed , uh , both this discriminatively trained thing and something that 's not . So you have a good set of features that everybody 's worked really hard to make ,", + "PhD A : Yeah .", + "Professor B : and then , uh , you {disfmarker} you discriminately train it , but you also take the path that {disfmarker} that doesn't have that ,", + "PhD A : Uh - huh .", + "Professor B : and putting those in together . And that {disfmarker} that seem So it 's kind of like a combination of the {disfmarker} uh , what , uh , Dan has been calling , you know , a feature {disfmarker} uh , you know , a feature combination versus posterior combination or something . It 's {disfmarker} it 's , you know , you have the posterior combination but then you get the features from that and use them as a feature combination with these {disfmarker} these other things . And that seemed , at least in the last one , as he was just saying , he {disfmarker} he {disfmarker} when he only did discriminative stuff , i it actually was {disfmarker} was {disfmarker} it didn't help at all in this particular case .", + "PhD A : Yeah .", + "Professor B : There was enough of a difference , I guess , between the testing and training . But by having them both there {disfmarker} The fact is some of the time , the discriminative stuff is gonna help you .", + "PhD A : Mm - hmm .", + "Professor B : And some of the time it 's going to hurt you ,", + "PhD A : Right .", + "Professor B : and by combining two information sources if , you know {disfmarker} if {disfmarker} if {disfmarker}", + "PhD A : So you wouldn't necessarily then want to do LDA on the non - tandem features because now you 're doing something to them that {disfmarker}", + "Professor B : That i i I think that 's counter to that idea .", + "PhD A : Yeah , right .", + "Professor B : Now , again , it 's {disfmarker} we 're just trying these different things . We don't really know what 's gonna work best . But if that 's the hypothesis , at least it would be counter to that hypothesis to do that .", + "PhD A : Right .", + "Professor B : Um , and in principle you would think that the neural net would do better at the discriminant part than LDA .", + "PhD A : Right . Yeah . Well {disfmarker} y", + "Professor B : Though , maybe not .", + "PhD A : Yeah . Exactly . I mean , we , uh {disfmarker} we were getting ready to do the tandem , uh , stuff for the Hub - five system , and , um , Andreas and I talked about it , and the idea w the thought was , \" Well , uh , yeah , that i you know {disfmarker} th the neural net should be better , but we should at least have uh , a number , you know , to show that we did try the LDA in place of the neural net , so that we can you know , show a clear path .", + "Professor B : Right .", + "PhD A : You know , that you have it without it , then you have the LDA , then you have the neural net , and you can see , theoretically . So . I was just wondering {disfmarker} I {disfmarker} I {disfmarker}", + "Professor B : Well , I think that 's a good idea .", + "PhD A : Yeah .", + "Professor B : Did {disfmarker} did you do that", + "PhD A : Um . No .", + "Professor B : or {disfmarker} tha that 's a {disfmarker}", + "PhD A : That 's what {disfmarker} that 's what we 're gonna do next as soon as I finish this other thing . So .", + "Professor B : Yeah . Yeah . No , well , that 's a good idea . I {disfmarker} I {disfmarker}", + "PhD A : We just want to show .", + "Professor B : i Yeah .", + "PhD A : I mean , it {disfmarker} everybody believes it ,", + "Professor B : Oh , no it 's a g", + "PhD A : but you know , we just {disfmarker}", + "Professor B : No , no , but it might not {disfmarker} not even be true .", + "PhD A : Yeah .", + "Professor B : I mean , it 's {disfmarker} it 's {disfmarker} it 's {disfmarker} it 's {disfmarker} it 's a great idea . I mean , one of the things that always disturbed me , uh , in the {disfmarker} the resurgence of neural nets that happened in the eighties was that , um , a lot of people {disfmarker} Because neural nets were pretty easy to {disfmarker} to use {disfmarker} a lot of people were just using them for all sorts of things without , uh , looking at all into the linear , uh {disfmarker} uh , versions of them .", + "PhD A : Yeah . Mm - hmm . Yeah .", + "Professor B : And , uh , people were doing recurrent nets but not looking at IIR filters , and {disfmarker} You know , I mean , uh , so I think , yeah , it 's definitely a good idea to try it .", + "PhD A : Yeah , and everybody 's putting that on their {vocalsound} systems now , and so , I that 's what made me wonder about this ,", + "Professor B : Well , they 've been putting them in their systems off and on for ten years ,", + "PhD A : but .", + "Professor B : but {disfmarker} but {disfmarker} but , uh ,", + "PhD A : Yeah , what I mean is it 's {disfmarker} it 's like in the Hub - five evaluations , you know , and you read the system descriptions and everybody 's got , {vocalsound} you know , LDA on their features .", + "Professor B : And now they all have that . I see .", + "PhD A : And so .", + "Professor B : Yeah .", + "PhD A : Uh .", + "PhD C : It 's the transformation they 're estimating on {disfmarker} Well , they are trained on the same data as the final HMM are .", + "PhD A : Yeah , so it 's different . Yeah , exactly . Cuz they don't have these , you know , mismatches that {disfmarker} that you guys have .", + "PhD C : Mm - hmm .", + "PhD A : So that 's why I was wondering if maybe it 's not even a good idea .", + "PhD C : Mm - hmm .", + "PhD A : I don't know . I {disfmarker} I don't know enough about it ,", + "PhD C : Mm - hmm .", + "PhD A : but {disfmarker} Um .", + "Professor B : I mean , part of why {disfmarker} I {disfmarker} I think part of why you were getting into the KLT {disfmarker} Y you were describing to me at one point that you wanted to see if , uh , you know , getting good orthogonal features was {disfmarker} and combining the {disfmarker} the different temporal ranges {disfmarker} was the key thing that was happening or whether it was this discriminant thing , right ? So you were just trying {disfmarker} I think you r I mean , this is {disfmarker} it doesn't have the LDA aspect but th as far as the orthogonalizing transformation , you were trying that at one point , right ?", + "PhD C : Mm - hmm .", + "Professor B : I think you were .", + "PhD C : Mm - hmm . Yeah .", + "Professor B : Does something . It doesn't work as well . Yeah . Yeah ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 74, + "turns": [ + 471, + 591 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "target group , corresponding functionalities", + "speaker": "" + }, + "summary": "Marketing suggested that the remote should not have more functionality because it was a cheap-end remote and also said that if they say the age group was fifteen to twenty-five, then not many of them would actually own TVs to use remote control and Project Manager said that they were targeting the twenty to forty group.", + "title": "Target Group and Functionality of New Remote Control", + "relevant_turns": [ + [ + 9, + 21 + ], + [ + 54, + 58 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "normal", + "topic": "target group , corresponding functionalities", + "speaker": "" + }, + "summary": "Marketing suggested that the remote should not have more functionality because it was a low market cheap-end remote control and so they could not beat the modern functionality and that if people were buying a new remote control for functionality they would buy a universal remote. Marketing also said that if they said the age group was fifteen to twenty-five, then not many of them would actually own TVs to use remote control. Project Manager said they were targeting more of the twenty to forty group who just have or already have a job and have the money but may not want to spend that much money on a universal control.", + "title": "Target Group and Functionality of New Remote Control", + "relevant_turns": [ + [ + 9, + 21 + ], + [ + 54, + 58 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "universal remote , decision", + "speaker": "" + }, + "summary": "Marketing said that they could not go for a universal remote because of the price range and that they were neither building a universal remote nor a high-end product. Project Manager said that universal remote controls were quite expensive.", + "title": "Type of New Remote Control", + "relevant_turns": [ + [ + 17, + 21 + ], + [ + 30, + 50 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "high", + "topic": "universal remote , decision", + "speaker": "" + }, + "summary": "Marketing said they could not go for universal remotes because of the price range, they were not building a universal remote or building a high-end product, if they needed to get into universal remote territory they needed to get into things like LCD screens which would drive the cost up, that was the reason why universal remote controls tended to be quite expensive. They could try to go in between and offer a product that was not expensive and complicated even though people had the idea it was more functional than normal remote control.", + "title": "Type of New Remote Control", + "relevant_turns": [ + [ + 17, + 21 + ], + [ + 30, + 50 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "price", + "speaker": "Marketing , Project Manager , Industrial Designer" + }, + "summary": "Marketing didn't really know what the price range for remote controls was and asked if they going to be at the very bottom of the price range or kind of middle to bottom. Project Manager said that they were trying to offer a kind of universal control for less money. Industrial Designer said that since they were going to take into account what they were to sell around four million the price of the chip was very cheap so it was to design less kind of universal remote control for twelve Euro fifty.", + "title": "Price as Criteria for New Remote Control", + "relevant_turns": [ + [ + 56, + 97 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "price", + "speaker": "Marketing , Project Manager , Industrial Designer" + }, + "summary": "Marketing asked what would be the price range for the new remote control. Project Manager said they were trying to offer a kind of universal control for less money. Industrial Designer said it was okay to design universal RC for the twelve Euro fifty.", + "title": "Price as Criteria for New Remote Control", + "relevant_turns": [ + [ + 56, + 97 + ] + ] + } + ], + "source": [ + "Project Manager : Uh we should now uh try to decide um on our target group .", + "User Interface : Yeah .", + "Marketing : Yeah . Which I think is quite tricky .", + "Industrial Designer : {vocalsound}", + "Marketing : Um , basically we're trying to get people to buy a remote control {vocalsound} {disfmarker}", + "User Interface : Yeah .", + "Marketing : wouldn't they already have a remote control with their television when they buy one ?", + "User Interface : {vocalsound}", + "Project Manager : Of course they have already one . So our our our remote control has to be better .", + "Marketing : But it's not going to have more functionality ,", + "User Interface : Mm-hmm .", + "Marketing : 'cause it's only a low market , it's a cheap-end remote control , we can't beat modern functionality , we might {disfmarker} we'll be able to {vocalsound} beat them on th the look of it , th the design of it but that's not a big seller , if they're not just going to buy a new remote control just 'cause it looks pretty , they have to actually need it as well .", + "Project Manager : Mm-hmm .", + "Marketing : So I'm not sure how we can get people to buy this thing .", + "Project Manager : Mm . I {disfmarker} well I think {vocalsound} many people said uh in your in in your research uh uh uh the appearance of the uh R_C_ is is important when they are buying one", + "Marketing : Mm . Yeah . But why are they buying one in the first place ?", + "Project Manager : but {disfmarker} Indeed . So that will be about functionality {disfmarker}", + "Marketing : Mm . But if people are buying a new remote control for functionality they'll buy a universal remote . I've got friends who've got so many things they need a universal remote , otherwise they're using five different remotes for their all their things .", + "Project Manager : Mm . Mm-hmm . Mm .", + "Marketing : In that case they wouldn't buy our product , because it doesn't give them what they need in terms of functionality .", + "Project Manager : So your you think we should go for a more u universal high-performance {disfmarker}", + "Marketing : Well , we can't , with the price range . We We're not building a universal remote , we're not building a high end product .", + "Project Manager : What do {disfmarker} What do you think about {disfmarker} What componen", + "Industrial Designer : Yeah we have yeah twelve point five Euros uh per uh per R_ s R_C_", + "Marketing : Mm .", + "Industrial Designer : and I think uh with this now you know that chips are very uh cheaps", + "Marketing : Mm-hmm .", + "Industrial Designer : and uh we can include it in our control some new new features .", + "Marketing : Mm .", + "Industrial Designer : Yeah . And um {disfmarker} But yeah", + "Marketing : But {disfmarker} yeah . If we're getting into universal remote territory , we're getting to L_C_D_ screens and things like that", + "Industrial Designer : that's {disfmarker}", + "Marketing : which would drive the cost up a lot .", + "Project Manager : I don't know . I don't know whether that's necessary .", + "Industrial Designer : Ye", + "Project Manager : Is the L_C_D_ screen {disfmarker}", + "Marketing : For universal remotes {disfmarker}", + "Industrial Designer : I don't think L_C_D_ is not necessary {disfmarker} well , th for long term .", + "Marketing : If you {disfmarker} mm .", + "Project Manager : I think thi this could be this could be a market because uh universal remote controls uh tend to be uh quite expensive .", + "Marketing : And quite complicated to use ,", + "Project Manager : S so we can try to go in between ,", + "Marketing : yes .", + "Project Manager : and offer a product which is not as expensive and not as complicated", + "Marketing : Mm-hmm . Not as flexible maybe , yeah , but s", + "Industrial Designer : Yeah .", + "Marketing : yeah .", + "Project Manager : but but still but still people have the idea this is more functional than a normal uh uh R_C_", + "Industrial Designer : {vocalsound} Universal .", + "Marketing : Mm-hmm .", + "Project Manager : because it has more uh it it is in some kind universal .", + "Industrial Designer : Yeah .", + "Marketing : Mm-hmm .", + "Project Manager : {vocalsound}", + "Marketing : But if we're going for the say fifteen to twenty five age group then not many of them would actually own T_V_s to use a remote control on .", + "Project Manager : Mm yes but w we're targeting I think on more on the on the twenty to forty group .", + "Marketing : Okay . So they're {disfmarker} yeah .", + "Project Manager : People {disfmarker} yes . Who just have or already have a job and have the money but may not want to spend that much money on a on a universal universal control .", + "Marketing : Mm-hmm . Mm-hmm . Yep . I don't know really what the the price range for remote controls is . Are we gonna be at the very bottom of the price range , or are we kind of middle to bottom ? I don't know .", + "Project Manager : Uh well", + "Industrial Designer : Mm .", + "Project Manager : {vocalsound} I think uh when we think it over I thi I think we are trying to offer the a kind of universal control for for less money .", + "Industrial Designer : {vocalsound}", + "Marketing : Mm . Mm-hmm .", + "Industrial Designer : Yeah .", + "Project Manager : So d Do you agree ?", + "User Interface : Well {disfmarker} Well I it's fine with me like the price as long as it is uh not too expensive .", + "Industrial Designer : {vocalsound} Yeah", + "User Interface : Uh and it d uh {disfmarker} Our provin", + "Industrial Designer : because we have to take into account that we are gonna b we are gonna sell uh four aro around four million so when we speak about these numbers uh the price of a chip is {vocalsound} uh price of a chip is very cheap .", + "Marketing : Mm .", + "User Interface : Mm .", + "Industrial Designer : {vocalsound} So I'm okay for designing um a ne uh less {vocalsound} yeah a a kind of universal uh R_C_ yeah .", + "Project Manager : Mm-hmm . You think it's possible for the twelve Euro fifty ?", + "Industrial Designer : Yeah .", + "Project Manager : Okay . Um so then we we decide on on on going to this more universal kind of control .", + "User Interface : Uh yeah , that's that's what we needed basically .", + "Marketing : Mm-hmm .", + "Project Manager : Mm . Mm . Okay .", + "User Interface : Uh that's needed right now . And uh basically you can look to the standards of other {disfmarker}", + "Industrial Designer : Yeah that's needed , yeah . {vocalsound}", + "Marketing : Mm . Yeah .", + "Industrial Designer : And if we want to get the market , we really need that .", + "Marketing : Yeah . So I guess what I'd like from a universal remote is maybe choosing between three devices , being able to switch between them , there may be stereo , V_C_R_ and T_V_ .", + "User Interface : Actu", + "Industrial Designer : Yes . Exactly . {vocalsound}", + "User Interface : Yeah .", + "Marketing : And just be able to s use them all from the same remote , but not at the same time .", + "Project Manager : Yes .", + "User Interface : {vocalsound} Yeah you can also browse through all the standards you know , where are the limit of standards for all of them and you can just browse through them .", + "Industrial Designer : Is that okay for you ? Yeah .", + "Project Manager : Mm mm mm mm .", + "Industrial Designer : Yeah . Yeah .", + "Project Manager : So given we are going for this uh uh universal type uh m {vocalsound} maybe it is good when you try to find out which components you therefore need and y you will try to get more specific uh user interface content", + "Industrial Designer : Yes .", + "Marketing : Mm .", + "User Interface : Okay . Okay .", + "Project Manager : and uh maybe you can look on on what trends are in this uh in this type of market .", + "Marketing : Mm-hmm yep .", + "User Interface : Voila {vocalsound} . Hmm .", + "Project Manager : So anyone uh has a point to bring in", + "User Interface : So . Well .", + "Project Manager : or shall we {disfmarker} no .", + "User Interface : Oh I don't have anything right now . We can we'll we'll go", + "Industrial Designer : Oh", + "Project Manager : Okay .", + "Industrial Designer : that's that's fine then .", + "User Interface : and we'll I'm sure we'll up something good", + "Marketing : Mm-hmm .", + "Project Manager : W yes ,", + "User Interface : for the {vocalsound}", + "Project Manager : we uh we can have lunch now .", + "Industrial Designer : Yeah .", + "Marketing : Mm-hmm .", + "Project Manager : So um Then th th the next meeting will uh", + "User Interface : Yeah so we meet in {disfmarker} well {vocalsound} what are our {disfmarker}", + "Project Manager : after lunch you have uh we have uh thirty minutes of work and then we have the next meeting . But you will be informed via the computer .", + "User Interface : Okay .", + "Project Manager : Okay .", + "User Interface : Cool . So see you later .", + "Industrial Designer : {vocalsound} Okay {vocalsound} perfect ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 9, + "turns": [ + 90, + 197 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "p-file", + "speaker": "Grad C , PhD D" + }, + "summary": "Grad C said that the use of P-file would be appropriated for different kinds of pitch values or for any frame-level, however, mentioned that it was too verbose. PhD D added that P-file for each frame was storing a vector of cepstral or PLP values, Grad C complimented saying that it was whatever you wanted, because it built into the concept of frames, utterances, sentences, and also into arbitrary vectors of values.", + "title": "P-File Application", + "relevant_turns": [ + [ + 1, + 5 + ], + [ + 40, + 56 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "p-file", + "speaker": "Grad C , PhD D" + }, + "summary": "According to Grad C and PhD D, P-file was useful for different pitch values or any frame-level and utterances, and it stored a vector of cepstral or PLP values.", + "title": "P-File Application", + "relevant_turns": [ + [ + 1, + 5 + ], + [ + 40, + 56 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "store , features", + "speaker": "Grad C , PhD F , PhD D , PhD A" + }, + "summary": "PhD F said that for every frame you get a pitch value, PhD D added that lattices were big, so Grad C suggested using P-file, and that ICSI had a format for frame-level representation of features. Grad C said there was a way in XML to refer to external resources, and PhD F asked about its advantages, Grad C answered it was more compact, and PhD F complemented saying those were long meetings, and Grad C mentioned that at frame-level it was better to encode binary. PhD A said it was possible to G-zip text formats. Grad C said that at frame-level, even P-file was too verbose. PhD D said P-file was storing a vector of cepstral or PLP values, Grad C replied it could take different types, but it was still tighter than ASCII. PhD A said they used a generalization of the Sphere format. Grad C asked what HTK did for features, and PhD A answered that it had its own feature format.", + "title": "Formats to Store Features", + "relevant_turns": [ + [ + 0, + 7 + ], + [ + 9, + 18 + ], + 21, + [ + 40, + 42 + ], + [ + 51, + 54 + ], + [ + 58, + 60 + ], + [ + 73, + 79 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "high", + "topic": "store , features", + "speaker": "Grad C , PhD F , PhD D , PhD A" + }, + "summary": "PhD F said that for every frame you get a pitch value, so Grad C suggested to use P-file, and said that ICSI had a format for frame-level representation of features, also mentioned there that XML could refer to external resources, and PhD F asked about its advantages, Grad C answered it was more compact, and that at frame-level it was better to encode binary because even P-file was too verbose. PhD A said it was possible to G-zip text formats, and that P-file was tighter than ASCII. PhD A said they used a generalization of the Sphere format. Grad C asked what HTK did for features, and PhD A answered that it had their own feature format.", + "title": "Formats To Store Features", + "relevant_turns": [ + [ + 0, + 7 + ], + [ + 9, + 18 + ], + 21, + [ + 40, + 42 + ], + [ + 51, + 54 + ], + [ + 58, + 60 + ], + [ + 73, + 79 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "phone-level , vector", + "speaker": "Grad C , PhD F , PhD D , PhD A" + }, + "summary": "PhD A said O Ss format was perfect for phone-level, like phones or syllables. PhD F said that phones were every five frames. Grad C mentioned it was debatable to do phone-level. Then, PhD D questioned about the storage capacity of P-file, saying that it stored a vector of cepstral or PLP values, and Grad C replied it could take different types. PhD F said you could only store a feature vector at frame-by-frame.", + "title": "Formats At Phone-Level And Vectors", + "relevant_turns": [ + [ + 26, + 30 + ], + 33, + [ + 38, + 39 + ], + [ + 51, + 54 + ], + 99 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "phone-level , vector", + "speaker": "Grad C , PhD F , PhD D , PhD A" + }, + "summary": "PhD A said O Ss format was perfect for phone-level. PhD F mentioned phones were every five frames. PhD D said that P-file stored a vector of cepstral or PLP values, and Grad C replied it could take different types. PhD F said you could only store a feature vector at frame-by-frame.", + "title": "Formats At Phone-Level And Vectors", + "relevant_turns": [ + [ + 25, + 30 + ], + 33, + [ + 38, + 39 + ], + [ + 51, + 54 + ], + 99 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "frame-level", + "speaker": "Grad C" + }, + "summary": "Grad C would use P-file for frame-level stuff. Grad C said that ICSI had a format for frame-level representation of features and that anything at frame-level you had better encode binary. Grad C also mentioned that frame-level was not good for big files, because you would run out of space, and it was too verbose.", + "title": "Grad C's Opinion On Frame-Level", + "relevant_turns": [ + [ + 5, + 7 + ], + [ + 17, + 20 + ], + [ + 23, + 26 + ], + 40 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "normal", + "topic": "frame-level", + "speaker": "Grad C" + }, + "summary": "Grad C would use P-file for any frame-level stuff. Grad C said that ICSI had a format for frame-level representation of features, and that frame-level was not a good idea for big files, because it was too verbose.", + "title": "Grad C's Opinion On Frame-Level", + "relevant_turns": [ + [ + 5, + 7 + ], + [ + 17, + 20 + ], + [ + 23, + 26 + ], + 40 + ] + } + ], + "source": [ + "PhD F : I mean , we actually have {disfmarker} So , one thing that Don is doing , is we 're {disfmarker} we 're running {disfmarker} For every frame , you get a pitch value ,", + "PhD D : Lattices are big , too .", + "PhD F : and not only one pitch value but different kinds of pitch values", + "Grad C : Yeah , I mean , for something like that I would use P - file", + "PhD F : depending on {disfmarker}", + "Grad C : or {disfmarker} or any frame - level stuff I would use P - file .", + "PhD F : Meaning {disfmarker} ?", + "Grad C : Uh , that 's a {disfmarker} well , or something like it . It 's ICS uh , ICSI has a format for frame - level representation of features . Um .", + "PhD F : OK . That you could call {disfmarker} that you would tie into this representation with like an ID .", + "Grad C : Right . Right . Or {disfmarker} or there 's a {disfmarker} there 's a particular way in XML to refer to external resources .", + "PhD F : And {disfmarker} OK .", + "Grad C : So you would say \" refer to this external file \" . Um , so that external file wouldn't be in {disfmarker}", + "PhD F : So that might {disfmarker} that might work .", + "PhD D : But what {disfmarker} what 's the advantage of doing that versus just putting it into this format ?", + "Grad C : More compact , which I think is {disfmarker} is better .", + "PhD D : Uh - huh .", + "Grad C : I mean , if you did it at this {disfmarker}", + "PhD F : I mean these are long meetings and with {disfmarker} for every frame ,", + "Grad C : You don't want to do it with that {disfmarker} Anything at frame - level you had better encode binary", + "PhD F : um {disfmarker}", + "Grad C : or it 's gonna be really painful .", + "PhD A : Or you just compre I mean , I like text formats . Um , b you can always , uh , G - zip them , and , um , you know , c decompress them on the fly if y if space is really a concern .", + "PhD D : Yeah , I was thi I was thinking the advantage is that we can share this with other people .", + "Grad C : Well , but if you 're talking about one per frame , you 're talking about gigabyte - size files . You 're gonna actually run out of space in your filesystem for one file .", + "PhD F : These are big files . These are really {disfmarker} I mean {disfmarker}", + "Grad C : Right ? Because you have a two - gigabyte limit on most O Ss .", + "PhD A : Right , OK . I would say {disfmarker} OK , so frame - level is probably not a good idea . But for phone - level stuff it 's perfectly {disfmarker}", + "PhD F : And th it 's {disfmarker}", + "PhD A : Like phones , or syllables , or anything like that .", + "PhD F : Phones are every five frames though , so . Or something like that .", + "PhD A : But {disfmarker} but {disfmarker} but most of the frames are actually not speech . So , you know , people don't {disfmarker} v Look at it , words times the average {disfmarker} The average number of phones in an English word is , I don't know , {comment} five maybe ?", + "PhD F : Yeah , but we actually {disfmarker}", + "PhD A : So , look at it , t number of words times five . That 's not {disfmarker} that not {disfmarker}", + "PhD F : Oh , so you mean pause phones take up a lot of the {disfmarker} long pause phones .", + "PhD A : Exactly .", + "Grad C : Yep .", + "PhD A : Yeah .", + "PhD F : Yeah . OK . That 's true . But you do have to keep them in there . Y yeah .", + "Grad C : So I think it {disfmarker} it 's debatable whether you want to do phone - level in the same thing .", + "PhD F : OK .", + "Grad C : But I think , a anything at frame - level , even P - file , is too verbose .", + "PhD F : OK . So {disfmarker}", + "Grad C : I would use something tighter than P - files .", + "PhD F : Do you {disfmarker} Are you familiar with it ?", + "Grad C : So .", + "PhD F : I haven't seen this particular format ,", + "PhD A : I mean , I 've {disfmarker} I 've used them .", + "PhD F : but {disfmarker}", + "PhD A : I don't know what their structure is .", + "PhD F : OK .", + "PhD A : I 've forgot what the str", + "PhD D : But , wait a minute , P - file for each frame is storing a vector of cepstral or PLP values ,", + "Grad C : It 's whatever you want , actually .", + "PhD D : right ? Right .", + "Grad C : So that {disfmarker} what 's nice about the P - file {disfmarker} It {disfmarker} i Built into it is the concept of {pause} frames , utterances , sentences , that sort of thing , that structure . And then also attached to it is an arbitrary vector of values . And it can take different types .", + "PhD F : Oh .", + "Grad C : So it {disfmarker} th they don't all have to be floats . You know , you can have integers and you can have doubles , and all that sort of stuff .", + "PhD F : So that {disfmarker} that sounds {disfmarker} that sounds about what I w", + "Grad C : Um . Right ? And it has a header {disfmarker} it has a header format that {pause} describes it {pause} to some extent . So , the only problem with it is it 's actually storing the {pause} utterance numbers and the {pause} frame numbers in the file , even though they 're always sequential . And so it does waste a lot of space .", + "PhD A : Hmm .", + "Grad C : But it 's still a lot tighter than {disfmarker} than ASCII . And we have a lot of tools already to deal with it .", + "PhD F : You do ? OK . Is there some documentation on this somewhere ?", + "Grad C : Yeah , there 's a ton of it . Man - pages and , uh , source code , and me .", + "PhD F : OK , great . So , I mean , that sounds good . I {disfmarker} I was just looking for something {disfmarker} I 'm not a database person , but something sort of standard enough that , you know , if we start using this we can give it out , other people can work on it ,", + "Grad C : Yeah , it 's not standard .", + "PhD F : or {disfmarker} {comment} Is it {disfmarker} ?", + "Grad C : I mean , it 's something that we developed at ICSI . But , uh {disfmarker}", + "PhD F : But it 's {pause} been used here", + "Grad C : But it 's been used here", + "PhD F : and people 've {disfmarker}", + "Grad C : and {disfmarker} and , you know , we have a {pause} well - configured system that you can distribute for free , and {disfmarker}", + "PhD D : I mean , it must be the equivalent of whatever you guys used to store feat your computed features in , right ?", + "PhD F : OK .", + "PhD A : Yeah , th we have {disfmarker} Actually , we {disfmarker} we use a generalization of the {disfmarker} the Sphere format .", + "PhD D : Mmm .", + "PhD A : Um , but {disfmarker} Yeah , so there is something like that but it 's , um , probably not as sophist", + "Grad C : Well , what does H T K do for features ?", + "PhD D : And I think there 's {disfmarker}", + "Grad C : Or does it even have a concept of features ?", + "PhD A : They ha it has its own {disfmarker} I mean , Entropic has their own feature format that 's called , like , S - SD or some so SF or something like that .", + "PhD F : Yeah .", + "Grad C : I 'm just wondering , would it be worth while to use that instead ?", + "PhD D : Yeah .", + "PhD A : Hmm ?", + "PhD F : Yeah . Th - this is exactly the kind of decision {disfmarker} It 's just whatever {disfmarker}", + "PhD D : But , I mean , people don't typically share this kind of stuff , right ?", + "PhD A : Right .", + "Grad C : They generate their own .", + "PhD D : I mean {disfmarker} Yeah .", + "PhD F : Actually , I {disfmarker} I just {disfmarker} you know , we {disfmarker} we 've done this stuff on prosodics and three or four places have asked for those prosodic files , and we just have an ASCII , uh , output of frame - by - frame .", + "Grad C : Ah , right .", + "PhD F : Which is fine , but it gets unwieldy to go in and {disfmarker} and query these files with really huge files .", + "Grad C : Right .", + "PhD F : I mean , we could do it . I was just thinking if there 's something that {disfmarker} where all the frame values are {disfmarker}", + "Grad C : And a and again , if you have a {disfmarker} if you have a two - hour - long meeting , that 's gonna {disfmarker}", + "PhD F : Hmm ? They 're {disfmarker} they 're fair they 're quite large .", + "Grad C : Yeah , I mean , they 'd be emo enormous .", + "PhD F : And these are for ten - minute Switchboard conversations ,", + "Grad C : Right .", + "PhD F : and {disfmarker} So it 's doable , it 's just that you can only store a feature vector at frame - by - frame and it doesn't have any kind of ,", + "PhD D : Is {disfmarker} is the sharing part of this a pretty important {pause} consideration", + "PhD F : um {disfmarker}", + "PhD D : or does that just sort of , uh {disfmarker} a nice thing to have ?", + "PhD F : I {disfmarker} I don't know enough about what we 're gonna do with the data . But I thought it would be good to get something that we can {disfmarker} that other people can use or adopt for their own kinds of encoding . And just , I mean we have to use some we have to make some decision about what to do .", + "Grad C : Yeah .", + "PhD F : And especially for the prosody work , what {disfmarker} what it ends up being is you get features from the signal , and of course those change every time your alignments change . So you re - run a recognizer , you want to recompute your features , um , and then keep the database up to date .", + "Grad C : Right .", + "PhD F : Or you change a word , or you change a {vocalsound} utterance boundary segment , which is gonna happen a lot . And so I wanted something where {pause} all of this can be done in a elegant way and that if somebody wants to try something or compute something else , that it can be done flexibly . Um , it doesn't have to be pretty , it just has to be , you know , easy to use , and {disfmarker}" + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 30, + "turns": [ + 7, + 27 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "buttons", + "speaker": "User Interface" + }, + "summary": "User Interface gave a summary on how they would design the remote control using very few buttons while finding ways to make it attractive for people to use them. User Interface stated that they had to focus on primary functions such as buttons for sound, for on-off, shifting up a channel or shifting down as well as adding attractive functions such as speech recognition and a special button for selecting subtitles. User Interface suggested making the remote user-friendly by adopting large buttons. User Interface also mentioned that they wanted to use a little display for displaying the functions of the buttons. Industrial Designer stated that the buttons could be made using plastic or rubber and that the supplement and the buttons, really depended on the designer.", + "title": "Buttons on the Remote Control", + "relevant_turns": [ + 12, + 18 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "buttons", + "speaker": "User Interface" + }, + "summary": "User Interface gave a summary on how they would design the remote control using very few buttons while finding ways to make it attractive to control the remote control. User Interface stated they had to focus on primary functions such as buttons for sound, for on-off, shifting up a channel or shifting down, the numbers (zero to nine) as well as adding attractive functions such as speech recognition with a cheap system and a special button for selecting subtitles. User Interface explained at one push on the special button people would get small subtitles while double push or double click, would get people big subtitles. User Interface suggested making the remote user-friendly by adopting large buttons. User Interface also mentioned they wanted to use a little display for displaying the functions of the buttons. Industrial Designer stated the buttons could be made using plastic or rubber and the supplement and the buttons really depended on the designer.", + "title": "Types of Buttons on the Remote Control", + "relevant_turns": [ + 12, + 18 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "trend", + "speaker": "Marketing" + }, + "summary": "Marketing gave a report about the trend-watching that had been done over the past few days. Marketing had deployed some trend-watchers to Milan and Paris to get all of the newest trends and consulted some additional trend-watchers, after the original trend-watchers return, about what the best design would be. Marketing said the trend-watchers consulted advised that the remote control and the docking station should be telephone-shaped. Industrial Designer also mentioned that the trend-watcher presentation showed that people liked wood, but it raised the price and it didn't really fit the image unless they would start two product lines. That form should follow function.", + "title": "The Trend Report on Remote Controls", + "relevant_turns": [ + 4, + 18 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "trend", + "speaker": "Marketing" + }, + "summary": "Marketing gave a report about the trend-watching that had been done over the past few days. Marketing had deployed some trend-watchers to Milan and Paris to get all of the newest trends and consulted some additional trend-watchers, after the original trend-watchers return, about what the best design would be. Marketing said the trend-watchers consulted advised that the remote control and the docking station should be telephone-shaped, blend in the room and be simple. Industrial Designer also mentioned that the trend-watcher presentation showed that people liked wood versus a grey-black color but it raised the price and it didn't really fit the image unless they would start two product lines. That form should follow the function.", + "title": "Trends Influencing Remote Control Design", + "relevant_turns": [ + 4, + 18 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "docking station", + "speaker": "Marketing" + }, + "summary": "Marketing mentioned that the docking station should blend in the room, staying simple. Marketing said the trend-watchers consulted advised that the remote control and the docking station should be telephone-shaped. So one could imagine that the remote control would be standing up straight in the docking station but old people would prefer a design where the remote control just lay flat in the docking station. Industrial Designer suggested the use of kinetic energy or battery to power the docking station with the former making the docking station obsolete.", + "title": "Designing the Docking Station", + "relevant_turns": [ + 4, + 18 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "docking station", + "speaker": "Marketing" + }, + "summary": "Marketing said that the docking station should blend in the room with no eye-catching designs but instead would just be simple. Marketing said the docking station and small screen would be their main points of interest because that would be the innovativeness in the remote control so those features were really important. Marketing said the trend-watchers consulted advised that the remote control and the docking station should be telephone-shaped. So people could imagine that the remote control would be standing up straight in the docking station but the older people would prefer a design where the remote control just lay flat in the docking station. Industrial Designer presented the use of a basic battery and kinetic energy (shake to produce energy) as an energy source for the docking station with the latter option making the docking station obsolete.", + "title": "Factors to Consider While Designing a Docking Station", + "relevant_turns": [ + 4, + 18 + ] + } + ], + "source": [ + "Marketing : Sure .", + "Project Manager : Okay .", + "Marketing : I'll start off then .", + "Project Manager : Good luck . {vocalsound}", + "Marketing : Doh . 'Kay I'm uh gonna inform you about the trend-watching I've done over the past few days . Um we've done some market research . We distributed some more enquetes , questionnaires . And um besides that um I deployed some trend-watchers to Milan and Paris to well get all of the newest trends . And I've consulted some additional trend-watch trend-watchers , after the original trend-watchers return , about what the the best design would be . Um okay these are some overall findings . Um most important thing is the fancy design . Um the research indicated that that was by far the most important factor . Um innovativeness was about half as important as the fancy design . By innovativeness this means um functions which are not featured in other remote controls . Um about half of , half as important as the innovativeness was the was easy to use . Um for our um group , we're focusing on the people of sixty to eighty y years old , this is um , these factors are slightly more equal . 'Kay these are some more group specific findings . Uh the older people prefer dark colours . Uh they like recognisable shapes , and familiar material . And our surveys have indicated that especially wood is pretty much the material for older people . Um this is , this image will give you a little bit of an impression about um the look-and-feel that um the remote should have . Um this leads us to some personal preferences . Uh the remote control and the docking station should uh blend in in the in the room . Um so this would mean no uh eye-catching designs . Just keep it simple and {disfmarker} Well the docking station and small screen would be our main points of interest , because this would be the {disfmarker} These would uh be the innovativeness in the remote control . So this would be very important that we {vocalsound} at least include these features . Um well the trend-watchers I consulted advised that it b should be , the remote control and the docking station should be telephone-shaped . So you could imagine that uh the remote control will be standing up straight in the docking station . This is not really {disfmarker} This is pretty much a new shape to uh older people . So they would prefer uh a design where the remote control just lies flat in the docking station . So it would be kinda more telephone-shaped . Um besides that we would advise um to bring two editions , one with a wood-like colour and maybe feel , and one with a grey-black colour . The wood-like for the more uh exclusive people . People with more money . Uh the grey-black colour for well people with less means . That would be all .", + "Project Manager : Okay . Thank you . Any questions about the the trends ?", + "Marketing : Any questions ?", + "Project Manager : Mayb", + "User Interface : Mm no .", + "Project Manager : No ? Okay , we go on to the next one .", + "User Interface : {gap}", + "Project Manager : {vocalsound}", + "User Interface : Um {vocalsound} 'kay um yeah . {gap} uh some uh research uh a about um designing of an interface . Um the uh last meeting uh we had a about um uh using a f few buttons . So uh um uh that's w what I what I want to uh uh to do in uh our design . So um finding an attractive uh way to control uh the remote control . Um the uh {disfmarker} I found some uh something about uh speech uh recognition . So maybe uh we can uh use uh that . Um {disfmarker} Uh and uh using a little uh display . So um findings . Um yeah just um we have just to focus on the primary um functions . So uh only uh buttons uh for uh sound , um for uh on-off , um uh shifting u up uh sa uh ca channel or uh down shifting down . Um uh let's see . Um yeah and {disfmarker} Uh {gap} we uh need some uh new a attractive functions uh uh which attract uh uh people for using it . So uh it's uh like a speak uh speech uh recognition and um a special button for selecting uh subtitles . Just uh what we uh mentioned uh last uh meeting . Um and yeah overall um user-friendly . So uh using uh large large buttons . Um {disfmarker} It's uh possible to uh uh to make um quite cheap uh system for uh speech uh recognition . Um you can think about um uh when you lost your um remote control , you can uh call it and um it gives an um sig signal . So uh uh yeah . And and uh for uh shifting up a sen uh c ch channel or uh for um uh putting out uh sound or something , you can uh just give a sign uh say um sound off or {disfmarker} A and uh yeah . Television uh put the sound off uh put the sound off uh . Um {disfmarker} Let's see . Uh yeah . I was thinking about the special uh button for uh subtitles , um just one button to keep it uh simple . Uh one push on the button uh you get uh uh small uh subtitles . Um double push push um , if double click , um so uh you get uh big uh subtitles , for uh people uh um uh which c f uh who can't uh read small uh subtitles . So uh {disfmarker} Um {disfmarker} Yeah and w we have to keep uh in general buttons uh so um we've got um the buttons we have to use . The on-off , sound on-off , sound higher or lower , um the numbers , uh zero to uh uh nine . Um the general buttons m more general b one button for shifting up and shifting down uh channel . Um also we want to uh use a little d display uh for um for displaying the uh the functions of the buttons . And um we can uh build in a function f which uh shows the channel or some uh which the t television is on . So um made a little uh picture of uh it . Um {disfmarker} See . Um yeah . Just um we can put uh the on-off button uh over in this uh corner , um almost uh e all uh remote controls uh are using a on-off button on that place . Um so uh people uh will uh recognise uh um the button .", + "Industrial Designer : {vocalsound}", + "User Interface : So um {disfmarker} D display uh of it , it's uh just a small display . Uh um you can put it uh on top . Um it's uh most uh uh place where people uh , most of {gap} looks at . So uh um and a special uh button for shifting up uh and uh shifting down uh channel , um it's uh on place where um the thumb of of the {disfmarker} So you you can uh easily uh shift up or shift down . Um it's uh quite uh handy place . So um and uh all the f functions for subtitle uh one button , uh for sound uh {disfmarker} Uh and uh for our design , um uh we have to discuss about it uh I think uh so uh the form of it so {disfmarker}", + "Project Manager : Okay .", + "User Interface : And that's it .", + "Project Manager : Uh thank you . {vocalsound}", + "Industrial Designer : Okay . About the components design . Um for the energy source we can use a basic battery or , a as an optional thing , a kinetic energy , like in a watch , which you just shake and it produces energy . But if we choose for that option , the docking station would c become obsolete . So I don't think it's really an option . Uh for the casing , uh the uh manufacturing department can deliver uh a flat casing , single or double curved casing . It's really up the the design that we're gonna use . It's uh doesn't uh imply any technical restrictions . Uh as a case supplement , we could um , I thought of that l later , uh a rubber uh belt , like a anti-slip . Uh for the b buttons , we can use plastic or rubber . And the chip-set , um it says simple here , but it should be advanced , because we're using an L_C_D_ uh screen . And as uh the trend-watcher presentation showed , um people like wood , but it raises the price and it doesn't really fit the image , unless we would start two product lines . Form should follow function overall . Um well the kinetic energy source is rather fancy . But depends on what we want . I think we should disc discuss that . Um for the case , uh the supplement and the buttons , it really depends on the designer . And the chip-set uh really should be advanced because otherwise uh it would really be a simple uh remote control . And that's it .", + "Project Manager : Okay . Thank you . So that brings us to the discussion about our concepts . Mm .", + "Marketing : {vocalsound}" + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 72, + "turns": [ + 500, + 630 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "words", + "speaker": "PhD E , Professor B" + }, + "summary": "PhD E said they could stop at words but they won't. They would go all the way down to phonemes. Professor B said that if their metric of badness was word error, then maybe they should be looking at words. Professor B added that syllables had a lot of good properties but one would want to go further all the way to words and even concepts. PhD E said the common reason one couldn't do words was that there were too many of them so you would need to have some smaller set that could be used. Therefore, everyone goes to phonemes. PhD E said the important categories were the words and they could be put into the loop somehow to determine the goodness of sets of clusters.", + "title": "Data Clustering Using Words", + "relevant_turns": [ + [ + 68, + 77 + ], + [ + 96, + 98 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "words", + "speaker": "PhD E , Professor B" + }, + "summary": "Professor B added that syllables had a lot of good properties but one would want to go further all the way to words and even concepts. PhD E said the common reason one couldn't do words was that there were too many of them so you would need to have some smaller set that could be used. Therefore, everyone goes to phonemes. PhD E said the important categories were the words and they could be put into the loop somehow to determine the goodness of sets of clusters.", + "title": "Looking at Words During Data Clustering", + "relevant_turns": [ + [ + 68, + 77 + ], + [ + 96, + 98 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "phonemes", + "speaker": "Grad C" + }, + "summary": "Grad C said Sangita had temporal patterns for a certain set of phonemes and each one of them had a nice pattern over time. Grad C said also said Sangita had a TRAP for each one of the phonemes times fifteen.", + "title": "Temporal Patterns for a Certain Set of Phonemes", + "relevant_turns": [ + [ + 1, + 11 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "phonemes", + "speaker": "Grad C" + }, + "summary": "Grad C said Sangita had temporal patterns for a certain set of phonemes and each one of them had a nice pattern over time. Grad C said also said Sangita had a TRAP for each one of the phonemes times fifteen for each of the fifteen critical bands and had done this through agglomerative hierarchical clustering. Which was basically a clustering algorithm that started with many different points and many different clusters corresponding to the number of data. Grad C said that there were ways to generalize categories other than constraining your clustering to the set of phonemes that you already had.", + "title": "Clustering to a Set of Phonemes", + "relevant_turns": [ + [ + 1, + 11 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "clustering", + "speaker": "Grad C" + }, + "summary": "Grad C reported having read some literature about the clustering of data and added that Sangita had temporal patterns for a certain set of phonemes and each one of them had a nice pattern over time. Grad C said also said Sangita had a TRAP for each one of the phonemes times fifteen for each of the fifteen critical bands and had done this through agglomerative hierarchical clustering. Which was basically a clustering algorithm that started with many different points and many different clusters corresponding to the number of data. Grad C said that there were ways to generalize categories other than constraining your clustering to the set of phonemes that you already had. Grad C said that at some point in the clustering algorithm they would find that they had clustered things like, OK.", + "title": "Discussion on Clustering of Data", + "relevant_turns": [ + [ + 1, + 13 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "clustering", + "speaker": "Grad C" + }, + "summary": "Grad C said Sangita had temporal patterns for a certain set of phonemes and each one of them had a nice pattern over time. Grad C said also said Sangita had a TRAP for each one of the phonemes times fifteen for each of the fifteen critical bands and had done this through agglomerative hierarchical clustering. Which was basically a clustering algorithm that started with many different points and many different clusters corresponding to the number of data. Grad C said that at some point in the clustering algorithm they would find that they had clustered things like, OK.", + "title": "Meeting on the Clustering Algorithm", + "relevant_turns": [ + [ + 1, + 13 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "time , TRAP", + "speaker": "Grad C" + }, + "summary": "Grad C said Sangita had temporal patterns for a certain set of phonemes and each one of them had a nice pattern over time. Grad C said also said Sangita had a TRAP for each one of the phonemes times fifteen for each of the fifteen critical bands and had done this through agglomerative hierarchical clustering. Grad C said maybe they should take a look at arbitrary windows in time of varying length and cluster those.", + "title": "Temporal Patterns over Time", + "relevant_turns": [ + 1, + 3, + 9, + 11, + 20 + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "fully", + "specificity": "normal", + "topic": "time , TRAP", + "speaker": "Grad C" + }, + "summary": "Grad C, clustering of data, discovering intermediate categories, o classify, Sangita, doing on, TRAPS things, temporal patterns for, a certain set of phonemes, from TIMIT, the most common phonemes; each one of them has a, nice pattern over time, a one second window, has these patterns; has a, TRAP for each one of the phonemes, times fifteen, for each of the fifteen critical bands; agglomerative hierarchical clustering, basically, clustering algorithm, starts with many, many different points, many different clusters, corresponding to the number of data, patterns that you have in the data, metric, measures, how closely related, start, merging the patterns, most closely related; whereas maybe, want to just take, a look at, arbitrary windows in time, of varying length, and cluster those. The representation of the data, thinking of, was using, critical band, energies, over different lengths of time, yeah.", + "title": "Temporal Patterns over Time", + "relevant_turns": [ + 1, + 3, + [ + 9, + 11 + ], + 20 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "models", + "speaker": "PhD E , Professor B" + }, + "summary": "PhD E said that the common wisdom was you couldn't do words because there were too many of them, so you would need some smaller set for use and so everyone goes for phonemes. But the problem was that they build models of words in terms of phonemes and those models were really cartoon-ish. Professor B said that they were not trying for models of words. Professor B told PhD E that they might not have word models but instead phone models, that would still work somehow.", + "title": "Discussion on Models", + "relevant_turns": [ + [ + 76, + 77 + ], + 91, + [ + 105, + 108 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "normal", + "topic": "models", + "speaker": "PhD E , Professor B" + }, + "summary": "PhD E said that the common wisdom was that you couldn't do words because there were too many of them, so you would need some smaller set for use and so everyone goes for phonemes. But the problem was that they build models of words in terms of phonemes and those models were really cartoon-ish. Professor B said that they were not trying for models of words. So when one looked at conversational speech, for example, they didn't see the phonemes that were in one's word models. Professor B told PhD E that they might not have word models but instead phone models, that would still work somehow. PhD E said humans have some kind of mechanism that allows for word models to be munged and that PhD E didn't know how to build that in.", + "title": "How Word Models Function", + "relevant_turns": [ + [ + 76, + 77 + ], + 91, + [ + 105, + 108 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "noise", + "speaker": "Professor B" + }, + "summary": "Professor B said what they wanted to do was have something that, particularly in the presence of noise was better at distinguishing between categories that were actually close to one another, and hence, would probably be clustered together. Professor B said that if there was added noise, then low-energy phones sometimes wouldn't get heard and that our brains fill in and imagine what should be there.", + "title": "The Effects of Noise", + "relevant_turns": [ + 39, + [ + 109, + 122 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "high", + "specificity": "high", + "topic": "noise", + "speaker": "Professor B" + }, + "summary": "Professor B said what they wanted to do was have something that, particularly in the presence of noise was better at distinguishing between categories that were actually close to one another, and hence, would probably be clustered together. Professor B said that if there was added noise then low-energy phones sometimes wouldn't get heard. That, if it turned into another word or another pair of words, then that was more likely to happen. PhD E said that people understood the context of the situation when having a conversation and so if there was noise in there, their brain would fill in and imagine what should be there. Professor B added that even if they did a diagnostic rhyme test kind of things, where there really wasn't any information like that, people were still better at noise than the machines were.", + "title": "Noise Assessment", + "relevant_turns": [ + 39, + [ + 109, + 122 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "human", + "speaker": "PhD E , Professor B" + }, + "summary": "Professor B reported having understood that there was another constraint to be considered that would be straightforward for example, a human being to mark if they had manual annotation. PhD E said to be discriminative one had to have categories and the only categories that they knew of to use, were sort of those human significant categories that were significant to humans, like phonemes and things like that. PhD E said that humans have some kind of mechanism that allows for word models to be munged.", + "title": "Human Abilities in Data Clustering", + "relevant_turns": [ + 41, + 58, + 108 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "high", + "topic": "human", + "speaker": "PhD E , Professor B" + }, + "summary": "Professor B, other constraint, considering, wanna have categories, would be straightforward, a human being to mark if you had manual annotation. PhD E, to be discriminative, have to have categories, categories that are significant to humans; when, go to conversational, not all the phonemes, there, doesn't really matter, as humans because, mechanism that allows for these word models, whatever, models, to be munged.", + "title": "Human Abilities in Data Clustering", + "relevant_turns": [ + 41, + 58, + 108 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "discrimination", + "speaker": "Professor B" + }, + "summary": "Professor B said that if one was trying to find the right system in some sense, and the goal was discrimination, then having choices based on discrimination as opposed to unsupervised nearness of things was actually better. Professor B also said it didn't hurt to put discrimination at that level of manually annotated speech.", + "title": "Using Discrimination While Tackling Categories", + "relevant_turns": [ + 29, + [ + 94, + 103 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "normal", + "topic": "discrimination", + "speaker": "Professor B" + }, + "summary": "Professor B said that if one was trying to find the right system in some sense, and the goal was discrimination, then having choices based on discrimination as opposed to unsupervised nearness of things was actually better. PhD E said if one wanted to be discriminative, they had to have categories and added that words were more important than phones. Professor B also said it didn't hurt to put discrimination at that level of manually annotated speech.", + "title": "Deciding on Categories for Discrimination", + "relevant_turns": [ + 29, + [ + 94, + 103 + ] + ] + } + ], + "source": [ + "Professor B : OK . Uh . Got anything to tell us ?", + "Grad C : Um . Well , I 've been reading some literature about clustering of data . Just , um , I guess , let me put it in context . OK , so we 're talking about discovering intermediate categories to , um {disfmarker} to classify . And , uh , I was looking at some of the work that , uh , Sangita was doing on these TRAPS things . So she has , um {disfmarker} she has temporal patterns for , um , a certain set of phonemes , from {disfmarker} from TIMIT , right ? the most common phonemes . And each one of them has {disfmarker} has a {disfmarker} a nice pattern over time , a one {disfmarker} one second window . And it has {disfmarker} has these patterns . Um , so she has , um a TRAP for each one of the phonemes , um , times fifteen , for each of the fifteen critical bands . And , um , {vocalsound} she does this agglomerative hierarchical clustering which {disfmarker} which basically , um , is a clustering algorithm that , uh , starts with many , many , many different points {disfmarker} many different clusters {disfmarker} uh , corresponding to the number of data , uh , patterns that you have in the data . And then you have this distance mej metric which , uh , measures how {disfmarker} how closely related they are . And you start , um {vocalsound} by merging the patterns that are most closely related .", + "PhD E : And you create a tree .", + "Grad C : And y yeah , yeah , a dendrogram tree .", + "PhD E : Mm - hmm .", + "Grad C : Um .", + "PhD E : And then you can pick , uh , values anywhere along that tree to fix your set of clusters .", + "Grad C : Right , usually it 's when , um {disfmarker} when the sol similarity measures , um , don't go down as much .", + "PhD E : Mm - hmm .", + "Grad C : And so , uh {disfmarker} so you stop at that point . And what she found was , sh um , was there were five broad , um {disfmarker} broad categories , uh , corresponding to , uh , things like , uh , fricatives and , uh , vocalic , um , and , uh , stops .", + "Professor B : Mm - hmm .", + "Grad C : And , uh , one for silence and {disfmarker} and another one for schwa {disfmarker} schwa sounds . Um , and , um , I was thinking about ways to {disfmarker} to generalize this because w you 're {disfmarker} it 's sort of like a {disfmarker} it 's not a completely automatic way of clustering , because yo beforehand you have these {disfmarker} these TRAPS and you 're saying that {disfmarker} that these frames correspond to this particular phoneme . Um , and that 's {disfmarker} that 's constraining your {disfmarker} your clustering to {disfmarker} to the set of phonemes that you already have . Um , whereas maybe we want to just take {disfmarker} take a look at , um , arbitrary windows in time , um , of varying length , um , and cluster those .", + "PhD E : Mm - hmm .", + "Grad C : And I 'm thinking if we {disfmarker} if we do that , then we would probably , um , at some point in the clustering algorithm find that we 've clustered things like , OK , thi this is a transition , um , this is a relatively stable {disfmarker} stable point .", + "PhD E : Mm - hmm .", + "Grad C : Um , and I 'm hoping to find other things of {disfmarker} of similarity and maybe use these things as the intermediate , um {disfmarker} intermediate categories that , uh , um , I 'll later classify .", + "PhD E : Mm - hmm .", + "Professor B : Are you looking at these in narrow bands ?", + "Grad C : Um , right . F um , I 'm {disfmarker}", + "Professor B : Cuz that 's what you 're gonna be using , right ?", + "Grad C : Yeah , yeah . I {disfmarker} I haven't exactly figured out , um , the exact details for that but , uh , the {disfmarker} the representation of the data that I was thinking of , was using , um , critical band , um , energies , {vocalsound} um , over different lengths of time . So {disfmarker} Yeah .", + "Professor B : Yeah , I mean , it seems somehow that needs th uh , there 's a couple things that I wonder about with this . I mean , so one is {disfmarker} is , {pause} again , looking at the same representation ,", + "Grad C : OK .", + "Professor B : I mean , if you 're going for this sort of thing where you have {pause} uh , little detectors that are looking at narrow bands , then what you 're going to be looking for should be some category that you can find with the narrow bands .", + "Grad C : Mm - hmm .", + "Professor B : That {disfmarker} that seems to be kind of fundamental to it . Um , and then the other thing , uh , is {disfmarker} that I wonder about with it , and {disfmarker} and don't take this in the wrong way , like I {disfmarker} I know what I 'm doing or anything ,", + "Grad C : Right .", + "Professor B : but , I mean . {vocalsound} Um , just wondering really .", + "Grad C : Mm - hmm .", + "Professor B : Um , the sort of standard answer about this sort of thing is that if you 're trying to find {pause} the right system in some sense , whether you 're trying by categories or {disfmarker} or parameters {pause} um , and your goal is discrimination , then having choices based on discrimination as opposed to , um , unsupervised nearness of things , um , is actually better .", + "Grad C : Hmm .", + "Professor B : Um , and I don't know if that {disfmarker} I mean , since you 're dealing with issues of robustness , you know , maybe {disfmarker} maybe this isn't right , but it 'd be something I 'd be concerned about . Because , for instance , you can imagine , uh , uh , i i if you remember from {disfmarker} from , uh {disfmarker} from your {disfmarker} your quals , John Ohala saying that , uh , \" buh \" {comment} and \" puh \" {comment} differed , uh , not really cuz of voicing but because of aspiration . I mean , in as far as wha what 's really there in the acoustics .", + "Grad C : Mm - hmm .", + "Professor B : So , um , if you looked {disfmarker} if you were doing some coarse clustering , you probably would put those two sounds together . And yet , I would gue I would guess that many of your recognition errors were coming from , uh , um , pfft , {comment} screwing up on this distinction .", + "Grad C : Mm - hmm .", + "Professor B : So , in fact , it 's a little hard because recognizers , to first order , sort of work . And the reasons we 're doing the things we 're doing is because they don't work as well as we 'd like . And since they sort of work , uh , it means that they are already doing {disfmarker} if you go and take any recognizer that 's already out there and you say , \" how well is it distinguishing between {pause} schwas and stops ? \"", + "Grad C : Mm - hmm .", + "Professor B : Boy , I bet they 're all doing nearly perfectly on this , right ?", + "Grad C : Mm - hmm .", + "Professor B : So these {disfmarker} these big categories that differ in huge obvious ways , we already know how to do . So , what are we bringing to the party ? I mean , in fact what we wanna do is have something that , particularly in the presence of noise , uh , is better at distinguishing between , uh , categories that are actually close to one another , and hence , would probably be clustered together .", + "Grad C : Mmm .", + "Professor B : So that 's th that 's the hard thing . I mean , I understand that there 's this other constraint that you 're considering , is that you wanna have categories that , uh {disfmarker} that would be straightforward for , say , a human being to mark if you had manual annotation . And it 's something that you really think you can pick up . But I think it 's also essential that you wanna look at what are the {vocalsound} confusions that you 're making and how can you come up with , uh , categories that , uh , can clarify these confusions .", + "Grad C : Mm - hmm . Hmm .", + "Professor B : So , I mean , the standard sort of way of doing that is take a look at the algorithms you 're looking at , but then throw in some discriminative aspect to it . Y y this is more like , you know , how does LDA differ from PCA ? I mean , they 're the same sort of thing . They 're both orthogonalizing .", + "Grad C : Right .", + "Professor B : But , you know {disfmarker} and {disfmarker} and , um , this is a little harder because you 're not just trying to find parameters . You 're actually trying to find the {disfmarker} the {disfmarker} the {disfmarker} the categories themselves . Uh , so a little more like brain surgery , I think on yourself . Uh . So , uh", + "Grad C : Yeah .", + "Professor B : Um , anyway . That 's my {pause} thought .", + "Grad C : OK .", + "Professor B : You 've been thinking about this problem for a long time actually . I mean , well {disfmarker} W actually , you stopped thinking about it for a long time , but you used to think about it {vocalsound} a lot .", + "PhD E : Yeah .", + "Professor B : And you 've been thinking about it more now ,", + "PhD D : Yeah .", + "Professor B : these categories .", + "PhD E : Yeah .", + "Professor B : Mm - hmm .", + "PhD E : I guess {disfmarker} I don't {disfmarker} I don't {disfmarker} um , it 's not clear to me how to reconcile , you know , what you 're saying , which I think is right , with {pause} the way I 've been looking at it . That it 's {disfmarker} it 's {disfmarker} it 's all not very clear to me . But it seems to me that the desire {disfmarker} the desirable feature to have is something that , um , is bottom - up . You know , however we do that .", + "Professor B : Mm - hmm .", + "PhD E : And and so I guess what I don't understand is how to do that and still be discriminative , because to be discriminative you have to have categories and the only categories that we know of to use are sort of these human {disfmarker} human sig significant {disfmarker} categories that are significant to humans , like phonemes , things like that .", + "Professor B : Right .", + "PhD E : But that 's sort of what you want to avoid . And so that feels {disfmarker} I don't know how to get out of this .", + "Professor B : Well , here 's a {disfmarker} here 's a , uh , uh Here 's a generic and possibly useless thought , which is , {vocalsound} um , what do you really {disfmarker} I mean , in a sense the only s s systems that make sense , uh , are ones that {disfmarker} that have something from top - down in th in them . Right ? Because if e even the smallest organism that 's trying to learn to do anything , if it doesn't have any kind of reward for doing {disfmarker} or penal penalty for doing anything , then it 's just going to behave randomly .", + "PhD E : Mm - hmm .", + "Professor B : So whether you 're talking about something being learned through evolution or being learned through experience , it 's gotta have something come down to it that gives its reward or , you know , at least some reinforcement learning ,", + "PhD E : Right .", + "Professor B : right ?", + "PhD E : So the question is , how far down ?", + "Professor B : And", + "PhD E : We could stop at words , but we don't , right ? We go all the way down to phonemes .", + "Professor B : Right , but I me I {disfmarker} I think that maybe in some ways part of the difficulty is {disfmarker} is trying to deal with the {disfmarker} with these phonemes . You know , and {disfmarker} and {disfmarker} and i it 's almost like you want categories if {disfmarker} if our {disfmarker} if our , uh , um , {vocalsound} metric of {disfmarker} of goodness , uh , i if our {disfmarker}", + "PhD E : Mm - hmm .", + "Professor B : correction {disfmarker} if our metric of badness {vocalsound} is word error rate then , um , maybe we should be looking at words .", + "PhD E : Mm - hmm .", + "Professor B : I mean , for {disfmarker} for {disfmarker} for very nice , uh , reasons we 've looked for a while at syllables , and they have a lot of good properties , but i i i if you go all the way to words , I mean , that 's really {disfmarker} I mean , d w In many applications you wanna go further . You wanna go to concepts or something , or have {disfmarker} have {disfmarker} have concepts , actions , this sort of thing .", + "PhD E : Yeah . But words would be a nice {disfmarker}", + "Professor B : But , words aren't bad , yeah . And {disfmarker} and", + "PhD E : Yeah , so the common {disfmarker} right , the common wisdom is you can't do words because there 's too many of them , right ? So you have to have some smaller set that you can use , uh , and {disfmarker} and so everybody goes to phonemes . But the problem is that we {disfmarker} we build models of words in terms of phonemes and these models are {disfmarker} are really cartoon - ish , right ? So when you look at conversational speech , for example , you don't see the phonemes that you {disfmarker} that you have in your word models .", + "Professor B : Yeah . But {disfmarker} but {disfmarker} but we 're not trying for models of words here . See , so her here 's maybe where {disfmarker} If the issue is that we 're trying to come up with , um , some sort of intermediate categories which will then be useful for later stuff , uh , then {pause} maybe it doesn't matter that we can't have enough {disfmarker}", + "PhD E : Mm - hmm . Mm - hmm .", + "Professor B : I mean , what you wanna do is {disfmarker} is build up these categories that are {disfmarker} that are best for word recognition .", + "PhD E : Right . Right .", + "Professor B : And {disfmarker} and somehow if that 's built into the loop of what the categories {disfmarker} I mean , we do this every day in this very gross way of {disfmarker} of running o a thousand experiments", + "PhD E : Right .", + "Professor B : because we have fast computers and picking the thing that has the best word error rate .", + "PhD E : Yeah .", + "Professor B : In some way {disfmarker} I mean , we derive that all the time . In some ways it 's really not {comment} a bad {disfmarker} bad thing to do because it tells you in fact how your adjustments at the very low level affect the {disfmarker} the final goal .", + "PhD E : Mm - hmm . Mm - hmm .", + "Professor B : Um , so maybe there 's a way to even put that in in a much more automatic way ,", + "PhD E : Right .", + "Professor B : where you take , you know , something about the error at the level of the word or some other {disfmarker} it could be syllable {disfmarker} but in some large unit ,", + "PhD E : Uh - huh .", + "Professor B : uh , and uh {disfmarker} yeah , you may not have word models , you have phone models , whatever , but you sort of {pause} don't worry about that , and just somehow feed it back through .", + "PhD E : Mm - hmm .", + "Professor B : You know , so that 's , uh , wh what I called a useless comments because I 'm not really telling you how to do it . But I mean , it 's a {disfmarker} {vocalsound} it 's {disfmarker} it 's , you know {disfmarker} it", + "PhD E : No , but I think the important part in there is that , you know , if you want to be discriminative , you have to have uh , you know , categories .", + "Professor B : Right .", + "PhD E : And I think this {disfmarker} the important categories are the words , and {pause} not the phones .", + "Professor B : Yeah . Yeah .", + "PhD E : Maybe . And so {disfmarker} Right . If you can put the words in to the loop somehow for determining goodness of your sets of clusters {disfmarker} Uh {disfmarker}", + "Professor B : Now , that being said , I think that {disfmarker} that if you have something that is , um {disfmarker} i Once you start dealing with spontaneous speech , all the things you 're saying are {disfmarker} are really true .", + "PhD E : Mm - hmm .", + "Professor B : If you {pause} have read speech that 's been manually annotated , like TIMIT , then , you know , i i you the phones are gonna be right , actually , {vocalsound} for the most part .", + "PhD E : Yeah . Yeah ,", + "Professor B : So {disfmarker} so , uh , it doesn't really hurt them to {disfmarker} to do that , to put in discrimination at that level .", + "PhD E : yeah .", + "Professor B : Um , if you go to spontaneous speech then it 's {disfmarker} it 's trickier and {disfmarker} and {disfmarker} and , uh , the phones are {disfmarker} uh , you know , it 's gonna be based on bad pronunciation models that you have of {disfmarker}", + "PhD E :", + "Professor B : and , um {disfmarker} And it won't allow for the overlapping phenomenon", + "PhD E : Mmm . So it 's almost like there 's this mechanism that we have that , you know , when {disfmarker} when we 're hearing read speech and all the phonemes are there you know , we {disfmarker} we deal with that , but {disfmarker} but when we go to conversational , and then all of a sudden not all the phonemes are there , it doesn't really matter that much to us as humans because we have some kind of mechanism that allows for these word models , whatever those models are , to be {pause} munged , you know , and {disfmarker} and it doesn't really hurt , and I 'm not sure how {disfmarker} {vocalsound} how to build that in . Uh .", + "Professor B : Yeah , I mean , I guess the other thing i is {disfmarker} is to think of a little bit {disfmarker} I mean , we when y when you start looking at these kind of results I think it usually is {disfmarker} is pretty intuitive , but start looking at um , what are the kinds of confusions that you do make , uh , you know , between words if you want or {disfmarker} or {disfmarker} or , uh , even phones in {disfmarker} in {disfmarker} in {disfmarker} in read speech , say , uh , when there is noise . You know , so is it more across place or more across manner ? Or is it cor you know , is it {disfmarker} ?", + "Grad C : Mm - hmm .", + "Professor B : I mean , I know one thing that happens is that you {disfmarker} you {disfmarker} you , uh , you lose the , um , uh , low energy phones . I mean , if there 's added noise then low energy phones {vocalsound} sometimes don't get heard . And if that {disfmarker} if that is {disfmarker} if it {disfmarker} uh , if that turns it into another word or {disfmarker} or different {disfmarker} you know , or another pair of words or something , then it 's more likely to happen . But , um , I don't know , I w I would {disfmarker} I would guess that you 'd {disfmarker}", + "Grad C : Mm - hmm .", + "Professor B : W I don't know . Anyway , that 's {disfmarker}", + "PhD E : I think part of the difficulty is that a l a lot of the robustness that we have is probably coming from a much higher level .", + "Professor B : Mm - hmm .", + "PhD E : You know , we understand the context of the situation when we 're having a conversation . And so if there 's noise in there , you know , our brain fills in and imagines what {disfmarker} what should be there .", + "Professor B : Well that {disfmarker}", + "Grad C : Yeah . We 're {disfmarker} we 're doing some sort of prediction of what {disfmarker}", + "PhD E : Yeah , exactly .", + "Professor B : Oh , sure , that 's really big .", + "Grad C : Yeah .", + "Professor B : Uh , but I mean , even if you do um , uh , diagnostic rhyme test kind of things , you know , where there really isn't an any information like that , uh , people are still better in noise than they {disfmarker} than they are in {disfmarker} in , uh {disfmarker} uh , than the machines are .", + "PhD E : Hmm .", + "Professor B : So , I mean , that 's {disfmarker} i Right . We can't {disfmarker} we can't get it at all without any language models . Language models are there and important but {disfmarker} but , uh {disfmarker} Uh . If we 're not working on that then {vocalsound} we should work on something else and improve it , but {disfmarker} especially if it looks like the potential is there . So {disfmarker} Should we do some digits ?", + "PhD E : Yeah .", + "Professor B : Since we 're here ?", + "PhD E : Go ahead , Morgan .", + "Professor B : OK .", + "PhD E : OK .", + "Professor B : That 's all folks ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 63, + "turns": [ + 194, + 239 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "wrap up , meeting", + "speaker": "" + }, + "summary": "Project Manager looked for a design that worked, Industrial Designer said it was mainly technical-functional design, then Project Manager said marketing came up with user requirements specifications.", + "title": "Discussion About the Wrap Up of the Meeting", + "relevant_turns": [ + [ + 8, + 18 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "normal", + "topic": "wrap up , meeting", + "speaker": "" + }, + "summary": "Project Manager said they looked for a design that worked when they came back, Industrial Designer said it was mainly technical-functional design, and later Project Manager said that marketing came up with user requirements specifications, like friendliness, and price.", + "title": "Discussion About the Wrap Up of the Meeting", + "relevant_turns": [ + [ + 8, + 18 + ] + ] + } + ], + "source": [ + "Marketing : you know , well {disfmarker} maybe we have to move along , okay .", + "Project Manager : yeah , we have to move along , but I think we have some good good points to start with here .", + "Industrial Designer : Yeah , good point .", + "Project Manager : Okay , the next meeting will be in thirty minutes . I think you all {disfmarker} did you get uh notices on your computer for this ? Okay so well , you got the notice um", + "Industrial Designer : Me yeah .", + "User Interface : Yes .", + "Project Manager : {disfmarker} uh . The working design , I guess that's the function I_D_ {disfmarker} uh who is this ? The industrial designer {disfmarker} That's you .", + "Industrial Designer : Yeah . Yeah , it's functional de yeah , exactly , technical .", + "Project Manager : Okay . So , we looking for a working design when we come back .", + "Industrial Designer : Yeah .", + "Project Manager : {vocalsound}", + "Industrial Designer : Uh working design , yeah , it's it's uh mainly technical-functional design .", + "Project Manager : Then {disfmarker} And then the technical funct you are the technical function ,", + "Industrial Designer : Yeah , functional design ,", + "Project Manager : so so you are the working design .", + "Industrial Designer : and you {disfmarker}", + "Project Manager : So you have a working design and then a functional design .", + "User Interface : Okay .", + "Project Manager : And the marketing manager is coming up with some user requirement specification , like friendliness , and what we just discussed in general . That would be your idea . And , of course , price . That it , that it , that the price is a good price . I mean , the price is given , but , that was {disfmarker}", + "Marketing : Mm-hmm . We have to justify that price by having sufficient features to make it sell at that price .", + "Project Manager : That's right . That's right .", + "User Interface : {vocalsound}", + "Project Manager : And , you know , specifi you you will get specific um instructions for that . I think that's the end of the show . Yeah . So um {vocalsound} we have {disfmarker} well , we have a twen two two two three minutes . Um any questions at this point ? Or uh suggestions ?", + "Marketing : Mm .", + "Project Manager : I think {disfmarker} basically basically you will get instructions to work with and if you have any questions uh , uh I guess , you can uh {disfmarker}", + "User Interface : Okay .", + "Industrial Designer : Yeah .", + "Marketing : Okay , I think I have enough to think about 'til our next meeting .", + "Project Manager : Mm-hmm .", + "Industrial Designer : Yeah , even I have .", + "Marketing : How about you people ?", + "Project Manager : Mm-hmm .", + "User Interface : Yes .", + "Industrial Designer : Yeah , even I have , I think , yeah .", + "Marketing : Really ? Okay . 'Kay .", + "Project Manager : Okay .", + "Industrial Designer : Yeah , so let's see .", + "Marketing : Alright , well uh {disfmarker}", + "Project Manager : Then uh we see you in about thirty minutes . And see what we can come up with .", + "User Interface : Yes .", + "Industrial Designer : Hmm .", + "User Interface : Okay .", + "Marketing : Okay , very good .", + "Project Manager : Okay ?", + "User Interface : Yes .", + "Industrial Designer : Yeah ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 5, + "turns": [ + 13, + 143 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "current design , changes", + "speaker": "" + }, + "summary": "Industrial Designer said that the LCD panel would display the chosen functions in four columns. Project Manager asked if I would have a slogan. Industrial Designer said there was plenty of room on the side or bottom for the tagline. User Interface said they would look for buttons to be large enough to be easily pressed with a finger. Industrial Designer said it would be a centimeter for a button. Marketing asked about the colors available. User Interface showed a hazy yellow that lights up when you press a button. User Interface proposed to use the jog-dial as a power button and as a confirmation button for the LCD screen. Industrial Designer proposed that it be 3.5 centimeters wide. User Interface suggested that the button also be used to jump directly to a channel, to turn the volume up or down, and to select advanced features.", + "title": "Layout of Remote Control Functions", + "relevant_turns": [ + [ + 10, + 19 + ], + [ + 20, + 39 + ], + [ + 43, + 58 + ], + [ + 62, + 63 + ], + 70, + [ + 72, + 83 + ], + [ + 85, + 88 + ], + [ + 91, + 93 + ], + 97, + [ + 100, + 115 + ], + [ + 121, + 130 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "high", + "specificity": "normal", + "topic": "current design , changes", + "speaker": "" + }, + "summary": "Industrial Designer said that the LCD panel would display the chosen functions. Industrial Designer said that the slogan that the Project Manager requested would go on the side or at the bottom. Industrial Designer said that each button would measure one centimeter. Marketing asked about the available colors, and User Interface showed him a hazy yellow. User Interface proposed to use the jog-dial to select channels, volume and other advanced configuration options.", + "title": "Layout of Remote Control Functions", + "relevant_turns": [ + [ + 10, + 19 + ], + [ + 20, + 39 + ], + [ + 43, + 58 + ], + [ + 62, + 63 + ], + 70, + [ + 72, + 83 + ], + [ + 85, + 88 + ], + [ + 91, + 93 + ], + 97, + [ + 100, + 115 + ], + [ + 121, + 130 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "button , current design , changes", + "speaker": "" + }, + "summary": "User Interface wanted the buttons to be a comfortable size and for the remote to be the size of the palm of your hand. User Interface proposed to use a jog-dial to select the channels, control the volume and other advanced functions.", + "title": "Button Design", + "relevant_turns": [ + [ + 38, + 56 + ], + [ + 63, + 97 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "button , current design , changes", + "speaker": "" + }, + "summary": "User Interface wanted the buttons to be large enough to be easily pressed with a finger. Industrial Designer said that the buttons would be one centimeter long, so the remote would be ten centimeters high. User Interface proposed to use the jog-dial as a power button and as an accept button for the LCD screen if pressed, but turning, they could choose the channels, turn the volume up or down, and to set advanced features such as contrast and color. Industrial Designer proposed that the button be 3.5 centimeters wide. Project Manager showed what it would look like.", + "title": "Button Design", + "relevant_turns": [ + [ + 38, + 56 + ], + [ + 63, + 97 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "advanced function", + "speaker": "User Interface" + }, + "summary": "Industrial Designer said the LCD panel could simply display in columns or with more complex symbols the functions you would be selecting, such as brightness, contrast and other settings. User Interface indicated that the jog-dial could be rotated to navigate to more advanced feature settings such as contrast, color, brightness, and anything else they wanted to include as advanced features and then pressed to select the desired option. Industrial Designer said that you could even configure audio modes like mid or high range.", + "title": "Advanced Functions", + "relevant_turns": [ + [ + 7, + 19 + ], + [ + 63, + 115 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "advanced function", + "speaker": "User Interface" + }, + "summary": "Industrial Designer said the LCD panel just displays the functions you're selecting. Like showing brightness, contrast, etc. User Interface stated that jog-dial could be used for more advanced functions like contrast, color, brightness, and others.", + "title": "Advanced Functions", + "relevant_turns": [ + [ + 7, + 19 + ], + [ + 63, + 115 + ] + ] + } + ], + "source": [ + "Marketing : Where are they ?", + "Industrial Designer : Um they're in the L_C_D_ panel and the jog-dial ?", + "Marketing : Ah , right .", + "Industrial Designer : Okay 'cause {disfmarker}", + "Project Manager : So w what kind of thing uh is gonna be {disfmarker}", + "Marketing : Great .", + "User Interface : {vocalsound}", + "Industrial Designer : The L_C_D_ panel just displays um functionally what you're doing . If you're using an advanced function right , like um c brightness , contrast , whatever , it will just say {disfmarker}", + "Marketing : Right . Okay .", + "Industrial Designer : You know it's like it only has four columns , it's a very simple L_C_D_ like , whereas many {disfmarker} the minimum amount we need that the user will automatically know like this is brightness or this is contrast .", + "Marketing : Right .", + "Project Manager : Mm-hmm . Okay cool .", + "Marketing : Right , 'kay .", + "Industrial Designer : It might even be one , a bit more complex L_C_D_ panel with pictures like maybe the sun or the , you know , the the symbols of the various functions .", + "Marketing : Okay", + "Project Manager : Oh right okay .", + "Marketing : Mm-hmm , and what is this here ?", + "Project Manager : Cool .", + "Industrial Designer : That's a number pad .", + "Marketing : Okay so the number pad is {disfmarker} 'Kay , great .", + "Project Manager : Where are we gonna have the slogan ?", + "Industrial Designer : Um they're al along this {disfmarker}", + "User Interface : You know , just like right inside there .", + "Industrial Designer : Yeah .", + "Project Manager : Okay cool .", + "Industrial Designer : You have this space here , and then you have this thing on the side as well , or at the bottom .", + "Project Manager : {vocalsound}", + "Industrial Designer : 'Cause slogans are usually quite small , right ,", + "Project Manager : Okay .", + "Industrial Designer : they're not like huge", + "Marketing : Mm .", + "Industrial Designer : so they're s", + "Marketing : Yep .", + "Industrial Designer : Say a button's about", + "Project Manager : Okay .", + "Marketing : Looks good .", + "Industrial Designer : say a button's about this size , right , so you would still have plenty of space for a slogan , say even for that .", + "Marketing : Yep . {vocalsound} Mm-hmm .", + "Project Manager : So if this isn't to scale , what kind of dimensions are you thinking about here ?", + "User Interface : {vocalsound} Well {vocalsound} we want the other buttons to be big enough to push easily with a finger", + "Project Manager : Mm-hmm .", + "User Interface : so we reckon maybe that'll be about the same size as the palm of your hand . {gap}", + "Marketing : Okay .", + "Industrial Designer : Yep so that would be about a centimetre for a button , so one two three four centimetres . Plus maybe half o five", + "Marketing : Mm-hmm .", + "Industrial Designer : six seven eight ,", + "Marketing : About nine in total .", + "Project Manager : Six , seven , eight , nine , ten .", + "Industrial Designer : about yeah nine total .", + "Project Manager : So we're talking about ten centimetres .", + "Marketing : That sounds good . Yeah .", + "Project Manager : That would be good . So ten centimetres in height .", + "Marketing : Yep .", + "Industrial Designer : Nine , ten . Yep .", + "Project Manager : Okay um {vocalsound} .", + "Marketing : That'd be good , in fact a pen is about ten centimetres usually , so that would be {disfmarker} that sounds like a really good size , if you see it there .", + "Project Manager : Yeah . That's great and it's very bright as well . So um okay .", + "Marketing : Mm . Is it possible {disfmarker} uh I'm just gonna bring up the idea of colours . Is these are these the colours that {disfmarker} of production , or is this just what we had available ?", + "User Interface : Well I'm {disfmarker} We're gonna have again the the sort of the foggy um yellow from last time that lit up when you pushed the button .", + "Marketing : Right .", + "Project Manager : Okay so just {disfmarker}", + "User Interface : Um {disfmarker}", + "Project Manager : could you just list all the things that it does s so I can write them in the report .", + "User Interface : But um {vocalsound} this button um , because it's red it's sort of very prominent , we're gonna use it as uh {disfmarker} it can be the power button if you hold it for maybe two seconds it'll send a stand-by signal .", + "Industrial Designer : {vocalsound} Excuse me .", + "Project Manager : Mm-hmm .", + "User Interface : Um apart from that it's gonna be used as a confirm button for the L_C_D_ screen", + "Industrial Designer : Sure .", + "Project Manager : Okay .", + "User Interface : and you use this as a jog-dial .", + "Project Manager : Okay so that's like an okay button , right .", + "Marketing : Mm-hmm .", + "Industrial Designer : Oh we've discussed how h high it is , but how wide is it ? {vocalsound}", + "User Interface : I don't know . {vocalsound}", + "Project Manager : Okay .", + "Marketing : How high is it ?", + "Industrial Designer : No as in the height , but what about the width ?", + "Marketing : Yeah .", + "Project Manager : Oh oh", + "User Interface : Didn't put five centimetres .", + "Project Manager : like depth of the actual thing .", + "Industrial Designer : Do we need five ? I don't think five is {disfmarker}", + "User Interface : Um .", + "Industrial Designer : be about th three and a half .", + "Marketing : Okay .", + "Project Manager : Oh is this k to get an idea of scale from your from your thing there okay .", + "User Interface : Something by there .", + "Industrial Designer : Yeah , yeah .", + "Marketing : Sure .", + "Project Manager : So you can power on and off , what else can you do ?", + "Marketing : Three and a half .", + "User Interface : Um you can skip straight to a channel using these buttons .", + "Project Manager : Okay .", + "User Interface : Um , were gonna have the volume control here , but um because we've got the the L_C_D_ and the jog-dial we just thought we'd um use that as the volume .", + "Project Manager : Okay jog-dial for volume . And what else do you do with the jog-dial ?", + "Marketing : Mm-hmm .", + "User Interface : Um you can use it for um more advanced functions like contrast , colour and {disfmarker}", + "Project Manager : Contrast , brightness ,", + "User Interface : Um yeah .", + "Project Manager : yeah , and anything else ?", + "User Interface : Um just whatever else we wanted to include as the advanced functions , um we didn't actually go through and specify the {disfmarker}", + "Project Manager : Well of the designers what are they ?", + "User Interface : Uh what can a T_V_ do ?", + "Industrial Designer : Okay things like um brightness , contrast ,", + "Project Manager : Uh-huh .", + "Industrial Designer : um maybe tuning the channels .", + "Project Manager : Okay channel tuning .", + "Industrial Designer : Um .", + "Project Manager : That's a good one .", + "Industrial Designer : What else ? Um the various inputs . Are you having a V_C_R_ , are you having {disfmarker} you know which input do you have ?", + "Marketing : Mm-hmm , mm-hmm .", + "Project Manager : Okay auxiliary inputs .", + "Marketing : Mm-hmm ,", + "Industrial Designer : Um .", + "Marketing : probably colour or sharpness .", + "Industrial Designer : Yep , colour , sharpness . Um a lot of these things will have to be um free and open for users to define them .", + "Project Manager : Sharpness . Okay what about uh sound settings", + "Marketing : Mm-hmm .", + "Project Manager : ? Uh d can you change any of those at all ?", + "Marketing : Audio .", + "Industrial Designer : Audio , we have like your basic y your base , your mid-range , your high range .", + "User Interface : Um .", + "Industrial Designer : Um .", + "User Interface : {gap} the the balance hmm .", + "Industrial Designer : Yep , left-right balance , um maybe even pre-programmed sound modes , like um the user could determine like a series of sound modes ,", + "Project Manager : Okay .", + "Industrial Designer : and then what could happen would be um when you click on that then it would go to that setting .", + "Marketing : Mm-hmm .", + "Project Manager : Okay ,", + "Marketing : Mm 'kay .", + "Industrial Designer : Yeah ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 33, + "turns": [ + 7, + 196 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "reduction of buttons , speech recognition", + "speaker": "" + }, + "summary": "Marketing suggested making the remote control more comfortable with a reduction of buttons from the usual ones and asked if people would pay more for speech recognition. Project Manager suggested the removal of all the least used buttons and even having a remote control with no buttons at all by adopting voice recognition. Marketing said speech recognition was something that could be added to the design. Project Manager added that the remote could have speech recognition but they didn't know the relative proportion in the age groups.", + "title": "Reduction of Buttons by Adopting Speech Recognition", + "relevant_turns": [ + [ + 10, + 17 + ], + 27, + [ + 52, + 63 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "high", + "specificity": "high", + "topic": "reduction of buttons , speech recognition", + "speaker": "" + }, + "summary": "Marketing said the remote control would be made more comfortable by the reduction of buttons and asked if people would pay more for speech recognition. Marketing said the speech recognition was possibly something they could add to the design.", + "title": "Discussion on Adding Speech Recognition", + "relevant_turns": [ + [ + 10, + 17 + ], + 27, + [ + 52, + 63 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "reducing buttons", + "speaker": "Marketing , Project Manager" + }, + "summary": "Marketing suggested making the remote control more comfortable by reducing the number of buttons from the usual ones. Project Manager suggested the removal of all the least used buttons and even having a remote control with no buttons at all by adopting voice recognition. Marketing said speech recognition was something that could be added to the design. Project Manager added that the remote could have speech recognition but they didn't know the relative proportion in the age groups.", + "title": "Discussion on Reducing Buttons", + "relevant_turns": [ + [ + 10, + 17 + ], + 27, + [ + 52, + 63 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "normal", + "topic": "reducing buttons", + "speaker": "Marketing , Project Manager" + }, + "summary": "Marketing suggested not making the remote control too complicated but easy to use for first-time users by possibly reducing the number of buttons. Marketing asked if people would pay more for it if had speech recognition and that it was an idea to be added into the design. Marketing talked about the functionality, frequency of use, and relevance of different buttons on the remote. Project Manager said people hardly used many buttons on the remote and that they should be removed altogether. Project Manager wondered if they could get a remote control with no buttons at all by going for voice recognition. Project Manager also said even though they had the usage by age structure, they didn't have the proportion of people using remotes in those particular age groups. Project Manager said speech recognition was a good idea but relative numbers were missing to guide on proper design.", + "title": "Making a Remote Control with Fewer Buttons", + "relevant_turns": [ + [ + 10, + 17 + ], + 27, + [ + 52, + 63 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "remote control , fully depend , speech recognition , no buttons", + "speaker": "" + }, + "summary": "Project Manager said you couldn't fully depend on a remote control with speech recognition and no buttons because the sound from the television could change the channels.", + "title": "Making a Buttonless Remote Control", + "relevant_turns": [ + [ + 66, + 93 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "remote control , fully depend , speech recognition , no buttons", + "speaker": "" + }, + "summary": "Industrial Designer said it would be a problem to fully depend on a remote control with speech recognition and no buttons given many people wouldn't want to be bothered with learning how to use a whole new remote control. Project Manager added that another technical problem was the sound from the television, which could change channels from one to another.", + "title": "Design Challenges of a Buttonless Remote", + "relevant_turns": [ + [ + 66, + 93 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "current remotes", + "speaker": "Marketing" + }, + "summary": "Marketing gave a report on functionality requirements of a remote involving a hundred people to see what was needed and what they needed to see. The report was on how often and necessary people used certain remote buttons. Marketing said the general opinions about current remotes were that they were ugly, so some kind of a new style should be incorporated. Marketing added that if the remotes looked better, a great percentage of people would spend more money on them.", + "title": "Designs of Current Remotes", + "relevant_turns": [ + [ + 8, + 10 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "current remotes", + "speaker": "Marketing" + }, + "summary": "Marketing gave a report on the functionality requirements of a remote to see what was needed and what people needed to see. Marketing said the general opinions about current remotes were that they were ugly and if they looked better, a great percentage of people would spend more money on them.", + "title": "Designing Better Looking Remotes", + "relevant_turns": [ + [ + 8, + 10 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "people", + "speaker": "Marketing" + }, + "summary": "Marketing gave a report on the functional requirements of a remote involving a hundred people to see what was needed and what they needed to see. The report was on how often and necessary people used certain remote buttons. Marketing said the general opinions about current remotes were that they were ugly, so some kind of a new style should be incorporated. Marketing added that if the remotes looked better, a great percentage of people would spend more money on them. Marketing said younger people would pay more for speech recognition and gave more information on people's opinions on functionality, relevance to the remote, and how often they were used.", + "title": "People's Ideas on Remote Controls", + "relevant_turns": [ + 8, + [ + 17, + 19 + ], + 27 + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "people", + "speaker": "Marketing" + }, + "summary": "Marketing gave a report on the functionality requirements of a remote to see what was needed and what people needed to see. Marketing said a great percentage of people would spend more money on them if they looked better and that younger people would pay more for speech recognition.", + "title": "People's Views on Remote Controls", + "relevant_turns": [ + 8, + [ + 17, + 19 + ], + 27 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "buttons", + "speaker": "Project Manager , Marketing" + }, + "summary": "Project Manager suggested making the remote control with dual functions by having voice recognition and still having buttons on it. Marketing added that they could have button control functions and voice control functions for the frequent commands. Project Manager said the advantage of doing away with the buttons altogether, was that it made the remote control cheaper and Marketing agreed.", + "title": "Advantages of Reducing Buttons", + "relevant_turns": [ + [ + 144, + 158 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "high", + "specificity": "normal", + "topic": "buttons", + "speaker": "Project Manager , Marketing" + }, + "summary": "Project Manager suggested making the remote dual function, having voice recognition, and still having buttons on it. Marketing suggested buttons control and the voice functions for different commands.", + "title": "Splitting the Use of Voice and Button Controls", + "relevant_turns": [ + [ + 144, + 158 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "percent", + "speaker": "Marketing" + }, + "summary": "Marketing reported that; seventy-five percent of people found their remote controls ugly, eighty percent would spend more if it looked better, seventy-five percent of users said they zapped a lot and fifty percent only use ten percent of the buttons.", + "title": "Statistics on Remote Control Usage by Percentages", + "relevant_turns": [ + 8, + 144 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "percent", + "speaker": "Marketing" + }, + "summary": "Marketing, functionality requirements, hundred people and covered all the aspects, what they want to see; from functionality, how often, used, how much, necessary and stuff; general opinions about current remotes; seventy five percent of people find their remote controls ugly, so, new style should be incorporated; if it looks better, eighty percent of people said they'd spend more money on it, it'd be more cost effective, put the price up; seventy five percent of users say they zap a lot; fifty percent users only use ten percent of the buttons; it would be fashion and fashion over practicality.", + "title": "Statistics on Remote Control Usage by Percentages", + "relevant_turns": [ + 8, + 144 + ] + } + ], + "source": [ + "Marketing : Uh I don't mind . {gap}", + "Project Manager : P fine .", + "Marketing : Uh can I steal the cable ?", + "Project Manager : Oh sorry , you can indeed .", + "Marketing : Cheers .", + "Project Manager : {vocalsound} {vocalsound} {vocalsound}", + "Marketing : {vocalsound} I got a {disfmarker} how do I start there ?", + "Project Manager : Oh , if you click on the um uh the one that that looks like a projection screen , no the one to the right of that . That one .", + "Marketing : That one . Cool . Well these are functionality requirements from the {disfmarker} our our guys down in the the research lab . Took hundred people and covered all the aspects of what um is needed by people and what they want to see . Um {vocalsound} everything kinda from functionality and how individual functions are {disfmarker} how mu how how often they're used and how much their necessary and stuff . And general opinions about current current remotes . See that , as we kinda noticed , seventy five percent of people find their remote controls ugly . So some kind of a new style should be incorporated that's less ugly {vocalsound} . Uh along with um looking less ugly , if it looks better , eighty percent of people said they'd spend more money on it . Which is a a plus for us , if we can make it look better , it'd be uh more cost effective and we can put the price up . Current remote controls do not match the operating behaviour of the user . I can empl I kinda take that to mean as um {vocalsound} they they don't uh {disfmarker} they , yeah , they only use {disfmarker} they only work for the television or yeah like as in in my flat I've got six remote controls for a stereo system , a digital box , a D_V_D_ player , a video player and T_V_ . If it was uh {disfmarker} I mean th my behaviour is to use multiple things at the same time and multiple remotes aren't really matched well to my behaviour . {vocalsound} Uh again , seventy five percent is {disfmarker} seventy five percent of users say they zap a lot . I took to mean that they just {disfmarker} they use it a lot , they use it regularly rather than standing up and manually change channels or volume {gap} . {vocalsound} And uh yeah , uh I think the big issue is fifty percent users only use ten percent of the buttons , 'cause uh wh if we got a remote that like {disfmarker} well we'll have some buttons taken off by the lack of teletext , but uh oh and we're going to see uh on the {disfmarker} uh that some of the functions like audio settings aren't h hardly ever used and used very {disfmarker} aren't considered relevant by the user . So I think maybe fewer buttons , which also make the design look sleeker , I dunno . Uh um yeah and uh frustrations of like people losing remote control .", + "Project Manager : Mm .", + "Marketing : I dunno maybe some kind of system of you press a button on the T_V_ or maybe that's b it would have to incorporate {gap} , but like some kind of system where you can f use something else to find the remote control . Maybe like it'll beep or something . And um , yep , the uh time taken to learn new remote controls is {disfmarker} Uh don't want to make it too complicated , easy to use for uh new {disfmarker} like first time users and stuff . And uh repetitive strain injury , I suppose we should make it more comfortable and make ma possibly even use {disfmarker} have to make it , yeah , fewer buttons , like I was saying about the whole mice {disfmarker} the mouse idea of it feels more comfortable .", + "Project Manager : Mm .", + "Marketing : Maybe don't even have to hold it as such .", + "Project Manager : Gosh , must be some telly addicts out there if they get R_S_I_ from their television remote , is all I can say .", + "Industrial Designer : {vocalsound}", + "Marketing : {vocalsound}", + "User Interface : {vocalsound}", + "Marketing : But uh yeah . It also asked um if we would {disfmarker} if people would pay more for speech recognition", + "Project Manager : {vocalsound} {gap}", + "Marketing : and younger people say they would . And uh there was another section on our {disfmarker} on the report for uh L_C_D_ displays , but the data wasn't there , so . I don't actually know what the results for that were ,", + "Project Manager : Mm . Right . Mm .", + "Marketing : so . {vocalsound} May be incrementally emitting , but yeah .", + "Project Manager : Yeah , I must say that um the uh {disfmarker} I c can't remember what {vocalsound} um f you know phone service I was using the other day , but that had sorta speech recognition which worked uh remarkably well , so that is indeed a uh um a thought", + "Marketing : And uh {vocalsound} it would cut out the R_S_I_ as well if you {disfmarker} {vocalsound}", + "Project Manager : and it it cuts out uh {disfmarker} I was was gonna say , you can't get a lot of R_S_I_ ,", + "Industrial Designer : {vocalsound}", + "Project Manager : j just get jaw ache . Okay , sorry . {vocalsound}", + "Marketing : Yeah , um {disfmarker} oh yeah , so possibly the speech recognition is possibly something could add into the design . Oh , I've got some other things I couldn't fit onto this presentation . Um . You see this okay ? Almost {disfmarker} no ? It's {disfmarker} sorry it's a bit {gap} . I'll read out to you . Uh functionality , uh like people's opinions on functionality , the relevance to the remote and how often they're used . So um like the power . Using the using the d swi the power switch to switch on T_V_ is a high relevance of nine , but it's not frequently used . You see what I mean ?", + "Project Manager : Yeah . {vocalsound}", + "Marketing : Whereas channel selection , which is very high relevance", + "Project Manager : Mm-hmm .", + "Marketing : is used the most . So m we can maybe even start to cut down on {disfmarker} or I was possibly even thinking of a design that maybe some of the buttons are hidden from everyday use . Maybe like uh a folding ledge or something . So that we can maybe go into the channel settings and the audio settings ,", + "Industrial Designer : Mm .", + "Marketing : which are low relevance", + "Project Manager : {vocalsound} Mm-hmm . I mean {disfmarker}", + "Marketing : and rarely used . And keep the v volume selection and channel selection very easily {disfmarker}", + "User Interface : It could be {disfmarker} oh uh I was just gonna say uh maybe like the flip phones that they use ?", + "Industrial Designer : Mm .", + "User Interface : Have you seen the new mo mobile phones", + "Project Manager : {vocalsound} Yeah .", + "User Interface : that flip out and they have the like texting , and then the numbers on one side ,", + "Marketing : Oh yeah .", + "User Interface : so", + "Project Manager : Mm .", + "User Interface : you could have the most {vocalsound} used buttons on top and flip it out or something .", + "Project Manager : Hmm , hmm .", + "Industrial Designer : Mm .", + "Marketing : Yeah , like the one that like slides back", + "Project Manager : Uh . Should we actually bite the bullet here ?", + "Marketing : and the buttons are concealed underneath .", + "User Interface : Yeah .", + "Industrial Designer : Mm .", + "Project Manager : If people really don't use those buttons to any extent at all um {vocalsound} remove them altogether .", + "Marketing : Just remove them completely ?", + "Project Manager : We we could actually have we could actually have a remote control with um {disfmarker}", + "User Interface : That might be the {disfmarker}", + "Project Manager : I wonder whether we could get the remote control with no buttons at all if we went for voice recognition , given that um the {disfmarker} {vocalsound} Um now the the age structure we were looking at {disfmarker} um I mean w we had usage by age structure , what we didn't have was what proportion of people using remotes were in those particular age groups . Now do we know whether they {disfmarker}", + "Marketing : Uh yeah .", + "Project Manager : Forty {disfmarker} no sorry {disfmarker} for forty five to fifty five age group , uh to put myself right in the middle of it , um u use remote controls to a great extent .", + "Marketing : {vocalsound}", + "Industrial Designer : {vocalsound}", + "Project Manager : Yes we {disfmarker}", + "Marketing : Um no this is for {disfmarker} pay more for speech recognition .", + "Project Manager : That would 've speech recogn right . So , we're looking at {disfmarker} um well again , we don't know the relative proportion {disfmarker} the relative numbers in the age groups .", + "Marketing : Yeah , that's true .", + "Project Manager : If we wanted something different , truly different , then the buttonless remote control w would be it .", + "Industrial Designer : P Well the only problem I can think of with that is if you've got a lot of people that don't wanna be bothered learning how to use new rem remote controls . If you just kind of take away everything that they're used to knowing , that's gonna be quite a change .", + "Project Manager : But if you just lift it up and say , channel one or B_B_C_ {disfmarker}", + "Industrial Designer : It might {disfmarker}", + "Marketing : Or even {disfmarker} I mean you could even just have it left on .", + "User Interface : Maybe i", + "Marketing : You could just put it down once on top your T_V_ and never have to {disfmarker}", + "User Interface : Yeah , have a big kind of like the satellite box or the cable box", + "Project Manager : {vocalsound}", + "User Interface : and have it just go on the T_V_ and then it doesn't matter where in the room you are ,", + "Industrial Designer : Mm .", + "User Interface : you won't lose it .", + "Marketing : Yeah .", + "Project Manager : It c well it {disfmarker} I can I can see technical problems with that in terms of the , you know , the sound from the television ,", + "Industrial Designer : Mm .", + "User Interface : No .", + "Project Manager : because if somebody actually on the television says uh uh , you know , I_T_V_ and you're watching B_B_C_ then then it might um change itself ,", + "Marketing : {vocalsound} B_B_C_ one . {vocalsound}", + "Industrial Designer : Yeah . {vocalsound}", + "User Interface : {vocalsound} Oh . {vocalsound}", + "Industrial Designer : Yeah .", + "Marketing : {vocalsound}", + "Project Manager : so it probably needs to be um {disfmarker} possibly actually need a button on it", + "User Interface : Yeah , that's true .", + "Project Manager : just to activate it .", + "Marketing : Oh yeah .", + "Project Manager : Or or something just to identify that you've lifted it up and it's use . And and then just say , oh I don't know , a thought and and then {disfmarker}", + "User Interface : Yeah .", + "Project Manager : uh I mean that that would certainly be uh truly different . {vocalsound} Um 'cause uh you know audio settings , nought point eight percent . I mean if they weren't there , {vocalsound} would people miss them ?", + "Marketing : Mm-mm .", + "Industrial Designer : But look at the importance of them . The volume settings .", + "Project Manager : {vocalsound}", + "Marketing : Relevance of two out of ten ,", + "Project Manager : Vol volume ,", + "Marketing : yeah .", + "Industrial Designer : Yeah .", + "Project Manager : yes um", + "Industrial Designer : They're not used often", + "Project Manager : th {vocalsound}", + "Industrial Designer : but they are quite important when they're used .", + "Project Manager : w we need to s identify things that {vocalsound} people actually need", + "Industrial Designer : Yeah .", + "Project Manager : and and it's a function of frequency and relevance . And um I would say ignoring ig ignoring power for the moment , um the channel and volume", + "Industrial Designer : Mm .", + "Project Manager : and th w w given given that we've been told to ignore teletext . Uh channel and volume are the only ones that", + "Marketing : Yeah .", + "Project Manager : {vocalsound} uh would appear to be essential .", + "Marketing : Stand out .", + "Project Manager : Um . So {disfmarker} if we can design something that that looks interesting , know , or looks different , um incorporates the the logo and and the colours and um we can still have our interchangeable fascias even if it's {gap} the yellow and grey , um and uh I dunno , buttons or or buttons as an option .", + "Marketing : Uh I just had a thought actually , sorry to interrupt .", + "Project Manager : Do , please .", + "Marketing : Uh you were saying about um it could {disfmarker} technical problems of like uh someone on the television saying a channel number and it changed {disfmarker}", + "Project Manager : Mm-hmm .", + "Marketing : we could maybe have like an activation word .", + "Project Manager : You cer certainly could .", + "Marketing : 'Cause I've seen I've seen this used on computers before , where you just {disfmarker} you address the remote ,", + "Project Manager : {vocalsound} Depe uh i depends whether um {disfmarker}", + "Industrial Designer : Mm .", + "Marketing : you address the computer , and then give it a command .", + "Project Manager : if we want to make this so simple that anybody can walk into the room and lift it up and say", + "Marketing : Oh I see . Oh yeah , I see .", + "Project Manager : B_B_C_ one . Um okay , I mean you could print {disfmarker} actually print it on the uh", + "Marketing : {vocalsound} Mm-hmm , yeah .", + "Project Manager : device itself . Um .", + "Marketing : I mean I'm just thinking of the point of view of peop you could still like lose this remote .", + "Project Manager : S th this I th {vocalsound} that's always gonna be a problem I think .", + "Industrial Designer : {vocalsound}", + "Marketing : Mm .", + "Project Manager : Um and I I I s so I suppose one um {disfmarker} could make it so desirable that if people lose it they immediately go out and buy another one .", + "Industrial Designer : {vocalsound}", + "User Interface : {vocalsound}", + "Marketing : {vocalsound}", + "Project Manager : Anyway , sorry , carry on . Do you want to just carry on with {disfmarker}", + "Marketing : Oh no", + "Project Manager : or {disfmarker}", + "Marketing : I I interrupted you ,", + "Project Manager : no no , no uh b I was in the middle of in the middle of your report there . {vocalsound}", + "Marketing : sorry {vocalsound} . Oh okay . Um well , I was just kinda wrapping up there . Yeah ,", + "Project Manager : Mm okay . {vocalsound}", + "Marketing : I was thinking um , yeah , maybe such things are relevant . We could make things much more f I think the the eighty percent of people would spend more on uh a remote uh that looks better , combined with uh decrease the {disfmarker} or take out the limited functio functions that we don't really use much . {gap} alright take out teletext , but as for channel settings and stuff it might it might um turn people somewhe peop some people that want the whole functionality away . But , since {disfmarker} if we're marketing a more kind of fashionable approach then it'd {disfmarker} it would be fashion and fashion over practicality .", + "Project Manager : Mm-hmm . S s we could {disfmarker} we could make it dual function {gap} voice recognition and {gap} still have buttons on it um", + "Marketing : {vocalsound} Oh , we could , yeah . We c yeah ,", + "Project Manager : 'cause we're {disfmarker}", + "Marketing : we could even have it as like a {disfmarker} yeah the buttons control this and the voice functions control the f things that you would do all the time , so .", + "Project Manager : {vocalsound} Certainly could . Yeah , yeah .", + "Industrial Designer : Mm .", + "Marketing : So uh yeah , if we could uh {disfmarker} power on and channel selection and and volume selection , wouldn't have to really {disfmarker}", + "Project Manager : {gap} The {disfmarker} I mean the the advantage of doing away the buttons altogether is it makes the thing cheaper .", + "Marketing : Yeah and probably it would look better as well .", + "Project Manager : No , it cou certainly opens up the possibility for making it uh , you know , visually very distinctive .", + "Marketing : Yeah . yeah .", + "Project Manager : Um 'cause you know , it does not have to be a oblong box .", + "Industrial Designer : Mm .", + "Marketing : Lined with numbered buttons and {disfmarker}", + "Project Manager : Mm , yeah . Okay , who {disfmarker} sorry , have you have you finished there Andy ?", + "Marketing : Uh yeah , yeah , that's everything .", + "Project Manager : Yep , yep . Um {vocalsound} given that we've already had a extensive discussion uh {disfmarker} {vocalsound} .", + "Industrial Designer : {vocalsound}", + "User Interface : {vocalsound}", + "Marketing : {vocalsound}", + "User Interface : Okay well , I can do mine .", + "Industrial Designer : Hmm .", + "Marketing : Do you want the cable ?", + "User Interface : Yeah , let's see if I can make this work . Um .", + "Industrial Designer : Oh , you have to hit like function and F_ something .", + "User Interface : Oh .", + "Marketing : F_ eight .", + "Industrial Designer : F_ eight .", + "User Interface : Is it doing {disfmarker}", + "Industrial Designer : {vocalsound} Dunno .", + "Marketing : Uh , give it about twenty seconds , or so .", + "User Interface : Okay .", + "Project Manager : Ah , there we go . {vocalsound}", + "Industrial Designer : Oh yeah , it's going .", + "User Interface : Oh okay . {vocalsound} Okay , so this is just about the technical functions .", + "Project Manager : Alright .", + "User Interface : So the method , I looked online for examples of other similar products and then just kind of was trying to brainstorm some possible design ideas and um identify what the necessary things are , what people are {disfmarker} what you really wanna have a remote control do . Um and then there are two different kinds that I found . There's a user centred one and an engineering centred one which I will have pictures of and then we kinda have to decide which one this should be .", + "Project Manager : Mm-hmm .", + "User Interface : {vocalsound} So these are the two different ones . This one um {disfmarker} this is the user centred , it has uh quite a few mm uh um fewer buttons", + "Marketing : {vocalsound}", + "User Interface : and then this is the engineering centred , which has a lot more buttons ,", + "Project Manager : Mm-hmm .", + "User Interface : and probably this is one that people complain about , about having too many buttons that you don't use . So basically , what a remote control is is you {disfmarker} it's to send messages to the television set , you know , turn on , off , switch the channels and the volume and things such as that . And so for this product it's gonna be television only , and then it has to have the uh logos for the company and the colours . And so , for my personal preferences , I think this one is easier to use and has quite a {disfmarker} you know , fewer buttons . Um we want something that sends messages easily to the television and I was kind of wondering about this example that they have . It looks kind of narrow at the top , and I was thinking maybe if it were wider at the top ,", + "Project Manager : Mm , yeah .", + "User Interface : then that would be easier . Um {vocalsound} and so we have to decide what's gonna make our product different . E the unique style , maybe have it light up so it's visible in the dark , um the changeable face-plates , and the lighting up and visible I was {disfmarker} when we were talking about havi losing it , maybe to have a button on the television that you press and it {disfmarker} maybe if it makes a noise or lights up or something like that , so it's easier to find if someone has hidden under the couch or something like that . So that's my presentation . Yeah ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 11, + "turns": [ + 74, + 93 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "Welsh language skills , demand", + "speaker": "" + }, + "summary": "Janet Finch-Saunders AM asked if there have been steps of the Welsh Government plan to build a better understanding of the workforce's Welsh language skills, to target support where capacity needed to be built for future needs of a bilingual Wales. Julie Morgan AM answered they have established a specific programme to develop Welsh Language Skills in childcare and play workforce, to develop workplace Welsh Language skills across the sector, so they were working with that. Nicola Edwards said that recruiting and retaining staff with good Welsh Language Skills added an extra dimension to the recruitment. Suzy Davies AM added that anybody on that education system, would have some Welsh language skills.", + "title": "Discussing Summary About Welsh Language Skills", + "relevant_turns": [ + [ + 0, + 2 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "normal", + "topic": "Welsh language skills , demand", + "speaker": "" + }, + "summary": "Janet Finch-Saunders AM asked if there have been steps of the Welsh Government plan to build a better understanding of the workforce's Welsh language skills, to target support where capacity needs to be built for future needs of a bilingual Wales. Julie Morgan AM answered they have established a specific programme to develop Welsh Language Skills in childcare and play workforce, to develop workplace Welsh Language skills across the sector, so they were working with that. Nicola Edwards said that recruiting and retaining staff with good Welsh Language Skills adds an extra dimension to it because they struggled to find staff with the right skills; So, doing more to attract people with Welsh language skills in the first place and in terms of training courses was a key part of it. Suzy Davies AM added that anybody who's been in the Welsh education system would have some Welsh language skills, obviously to different degrees.", + "title": "Discussing Summary About Welsh Language Skills", + "relevant_turns": [ + [ + 0, + 2 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "demand , Welsh language skills , teaching language , need", + "speaker": "Nicola Edwards" + }, + "summary": "Nicola Edwards said that most people would have some awareness of Welsh, but not necessarily one that would be appropriate because they developed it in school. So, it would not be necessarily appropriate to teach that language to children that don't use Welsh at home. There would be a lot about how to develop children bilingually.", + "title": "Nicola Edwards Talking About Teaching Welsh Language", + "relevant_turns": [ + [ + 5, + 9 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "demand , Welsh language skills , teaching language , need", + "speaker": "Nicola Edwards" + }, + "summary": "Nicola Edwards said that most people developed Welsh in school. So it was hard to teach it to children, especially from English-medium homes.", + "title": "Nicola Edwards Talking About Teaching Welsh Language", + "relevant_turns": [ + [ + 5, + 9 + ] + ] + } + ], + "source": [ + "Janet Finch-Saunders AM : And finally from me, what specific steps have been put in place to take forward the commitments from the Welsh Government's 2017 childcare/play early years workforce plan to build a better understanding of the workforce's Welsh language skills to enable support for the sector to be targeted and to identify where capacity needs to be built for the future to meet the needs of the early years sector in a bilingual Wales?", + "Julie Morgan AM : We think this is very important, and we're pleased that 29 per cent of children taking up the childcare offer are in Welsh or bilingual settings, so we think that's very good. We have established a specific programme to develop Welsh language skills in the childcare and play workforce with the National Centre for Learning Welsh, to develop workplace Welsh language skills across the sector. So, we're actually working with that, and I think you've done something with those recently, haven't you? I don't know if you want to\u2014", + "Nicola Edwards : Yes. So, we have a stakeholder group where we've brought together a variety of people with an interest in the early years, childcare and play sectors, and we had a presentation just last month from the national language centre about the education programmes that they're rolling out, and how this is all coming together, which is quite interesting. We've been working quite carefully to make sure that the variety of work-based learning programmes that we provide and offer are also available in Welsh and bilingually. Recruitment and retention within the childcare and play sector is quite challenging in any\u00a0 case. Recruiting and retaining staff with really good Welsh language skills adds an extra dimension to it, and\u00a0that it's a point that Mudiad Meithrin makes to us quite regularly, that they do struggle to find staff with the right skills. So, upskilling the existing workforce is a key part of it, but also doing more to attract people in with Welsh language skills in the first place in terms of the training courses that we're taking forward, and thinking about that in the context of the targets within Cymraeg 2050 and the aim to get to one million Welsh speakers. So, as the Deputy Minister said, we've got quite a number of children accessing the offer in Welsh-medium or bilingual settings at the moment. We're going to be doing some baselining work against that in terms of local authorities' Welsh in education strategic plans and education places, and what we can then do to increase the number of childcare places in parallel with that so that you can make sure that you start that pathway through learning Welsh, interacting with education and childcare through Welsh at a much earlier stage.", + "Lynne Neagle AM : Suzy, you've got a supplementary.", + "Suzy Davies AM : Just on this early point, anybody who's been through the Welsh education system, which is 20 years now, will have some Welsh language skills, obviously to differing degrees. For the entrants that are coming into childcare training now, there are going to be very few of them, realistically, with no Welsh at all, so what's actually being incorporated into the early years care training to make sure, at that stage, that the Welsh language skills are being developed, as opposed to an add-on later on?", + "Nicola Edwards : You're quite right. Most people coming through the education system will have some awareness of Welsh although I think it's probably important to remember we do also employ people from outside of wales.", + "Suzy Davies AM : Yes, but the majority, being realistic.", + "Nicola Edwards : But they don't necessarily have Welsh that is appropriate. They've got Welsh that they've developed in school. It's not necessarily appropriate for then teaching that language to children, who may be coming from families who don't use Welsh at home. So, that might be the first interaction that child has with the language. So, there's a lot of that in terms of child development and how you develop children bilingually, particularly if they're coming from English-medium homes, and reinforcing the language in language choices. There will also be some people who are, perhaps\u2014we see this quite a lot in the office\u2014quite confident in terms of speaking Welsh but less so in terms of some of the paperwork, the reporting, the writing and the interacting with parents more officially, which we need to think about as well. But it is mainly about getting people to a point where they can transmit that language onwards in a confident and meaningful way.", + "Suzy Davies AM : Okay. And it's ingrained in the early years training.", + "Nicola Edwards : Yes.", + "Suzy Davies AM : Okay. That's fine. Thank you for that. Thank you, Chair.", + "Lynne Neagle AM : Just before we move on, you said that 29 per cent of the take-up of the childcare offer is either through Welsh or is bilingual. Have you got any figures about how many children are accessing it in Welsh only?", + "Nicola Edwards : We will have. It becomes\u2014. With the way we do it, it's because of the way that the setting defines their language category, and that's how we collect it. We do go down to individual child level, although it's anonymised, data collection on a termly basis. So I'll have a look and see if we can send you through the last term.", + "Lynne Neagle AM : Maybe if the committee could have a note, that would be really useful.", + "Nicola Edwards : Yes, that's fine.", + "Lynne Neagle AM : We've got some questions now on childcare from Dawn Bowden.", + "Dawn Bowden AM : Thank you, Chair. Deputy Minister, the evaluation of the childcare offer, when it was published last year, said that there was very little evidence currently available to determine what its impact was. You're going to be producing a second evaluation in November this year; do you expect to see some indications now of the impact?", + "Julie Morgan AM : Well, the evaluation of the first year of the childcare offer was very limited, because the childcare offer wasn't available throughout the whole of Wales. And it was a very early implementation phase. So, obviously it takes time to grow. And the evaluation for year 2, I think, will also show a limited impact for the same reasons. The offer became available across the whole of Wales only last April. So we've only got since last April that it's actually been fully available. And the parental survey was released to parents in June 2019, therefore any impact on parents in the authorities coming on board in the second year will also be negligible. So, it's from the next one, however, we hope that we will get more information.", + "Dawn Bowden AM : So you think, by the time we get to November 2020, you might have a better picture.", + "Julie Morgan AM : The evaluation will be more meaningful, we think, then, yes." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 19, + "turns": [ + 187, + 385 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "evaluation , prototype", + "speaker": "" + }, + "summary": "Marketing talked about the criteria of evaluating the prototype, they formulated it, as a response to sort market research, and also finance. They got a set of criteria based on marketing to add in a financial one. Also, the points to evaluate were the look, the technical innovation, if it was user friendly and etc. Industrial designer said that the product felt good, and the spongy feel could be considered fancy. Marketing spoke about the rating system, false was seven and true was one, and User Interface said that because they didn't get the double curve, it wasn't completely true, but it was pretty close, they got almost everything they could.", + "title": "Team Talking About Evaluation Prototype", + "relevant_turns": [ + [ + 11, + 31 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "high", + "topic": "evaluation , prototype", + "speaker": "" + }, + "summary": "Marketing; design team makes a prototype; evaluate the prototype; criteria; product look and feel fancy; Industrial Designer; single curve; feel of the product's quite good; rubber kinda spongy feel; considered fancy; maybe two; User Interface; haven't got the double curve; can't like say; true; pretty close; got almost everything;", + "title": "Team Talking About Evaluation Prototype", + "relevant_turns": [ + [ + 11, + 31 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "prototype , evaluation", + "speaker": "Industrial Designer" + }, + "summary": "Industrial Designer said that it had a single curve, which made it feel good, and the rubber spongy feel, could be fancy.", + "title": "Industrial Designer Talking About the Prototype Evaluation", + "relevant_turns": [ + [ + 12, + 21 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "high", + "topic": "prototype ; evaluation", + "speaker": "Industrial Designer" + }, + "summary": "Industrial Designer said that they had a single curve, which makes it feel the product quite good, and they have a rubber kinda spongy feel, was in at the time, could be fancy.", + "title": "Industrial Designer Talking About the Prototype Evaluation", + "relevant_turns": [ + [ + 12, + 21 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "attractiveness , product , evaluation , prototype", + "speaker": "User Interface" + }, + "summary": "User Interface thought that the rubber kinda sponge feel maybe should be two, because they didn't get the double curve, so couldn't say if it was completely true but pretty close. About the elements of fashion to attract buyers, User Interface said it got the cherry and sponginess. It was maybe a two.", + "title": "User Interface Thoughts About the Attractiveness of the Product", + "relevant_turns": [ + [ + 18, + 31 + ], + [ + 116, + 131 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "attractiveness , product , evaluation , prototype", + "speaker": "User Interface" + }, + "summary": "User Interface said maybe two, without a double curve, pretty close to true, got the cherry and sponginess. It was maybe two.", + "title": "User Interface Thoughts About the Attractiveness of the Product", + "relevant_turns": [ + [ + 18, + 31 + ], + [ + 116, + 131 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "kinetic power", + "speaker": "Industrial Designer" + }, + "summary": "Industrial Designer told the group that it was deciding between kinetic power or speech recognition, in budget both showing a reasonable amount of speech recognition.", + "title": "Industrial Designer Talking About Kinetic Power", + "relevant_turns": [ + [ + 47, + 56 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "fully", + "specificity": "high", + "topic": "kinetic power", + "speaker": "Industrial Designer" + }, + "summary": "Industrial Designer; deciding between; kinetic power or; speech recognition; either of those for our budget; they both show a reasonable amount of speech recognition; But not the kinetic; Like the power.", + "title": "Industrial Designer Talking About Kinetic Power", + "relevant_turns": [ + [ + 47, + 56 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "technical innovation", + "speaker": "User Interface , Marketing" + }, + "summary": "Marketing said in the speech that some criteria of the evaluation were technical innovation and other characteristics. Then User Interface said that things like solar power, and various things could be in the technical innovation bit of the evaluation, then Marketing said that they should go for a two and asked how much technical innovation demonstrated the product.", + "title": "User Interface and Marketing Talking About Technical Innovation", + "relevant_turns": [ + 11, + [ + 42, + 49 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "technical innovation", + "speaker": "User Interface , Marketing" + }, + "summary": "Marketing said in the speech that some criteria of the evaluation were technical innovation and whether it was easy to use. Then User Interface said that things like solar power, and various things that they could have, might be in the technical innovation bit. Then Marketing said if they should go in a two in that, and someone agreed, then asked how much technical innovation demonstrated the product.", + "title": "User Interface and Marketing Talking About Technical Innovation", + "relevant_turns": [ + 11, + [ + 42, + 49 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "button supplements category", + "speaker": "Project Manager" + }, + "summary": "Project Manager said that if they wanted to lose one point two, it seemed that if they were going for the sample sensors, they needed to go for the cheapest options, like having a battery and having a sample sensor speaker, that would come from the button supplements category.", + "title": "Project Manager Thoughts About Button Supplements Category", + "relevant_turns": [ + [ + 74, + 83 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "button supplements category", + "speaker": "Project Manager" + }, + "summary": "Project Manager said that they should go for the cheapest, like having a sample sensor speaker, from the button supplements category.", + "title": "Project Manager Thoughts About Button Supplements Category", + "relevant_turns": [ + [ + 74, + 83 + ] + ] + } + ], + "source": [ + "Marketing : Shall we shall we evaluate the prototype as we've got it now first , and then sort of make decisions about what needs to be changed after ?", + "Project Manager : Mm-hmm . Makes sense .", + "Industrial Designer : Okay", + "Marketing : Okay . Right um , I have a little thing . So , we've all got a note of {disfmarker} it's thirteen point seven , isn't it , with everything we want on .", + "Project Manager : {gap} . Sorry , do you want that back up ?", + "Marketing : Yeah , I just had a presentation to do . {vocalsound}", + "Project Manager : Right .", + "User Interface : But I do think uh the v uh voice recognition thing would be more impressive than the fact that it's got no battery .", + "Project Manager : Okay , but remember the main {disfmarker} the only reason we were planning on having the voice recognition was so that they could find the remote if it got lost .", + "Marketing : Mm-hmm . Mm . {vocalsound} Right okay um , This is about the evaluation criteria that we use for the the prototype we've got here .", + "User Interface : {vocalsound}", + "Marketing : And so the method is that the design team makes a prototype , and we evaluate the prototype against some criteria that we've formulated . And those ones are gonna be in response to sort of market research , and also finance , I guess . {vocalsound} And do that on a scale from say true being one and false being seven , so if it's neither true nor false , then that's four . So , I got a set of criteria just based on the marketing that we need to add in a financial one as well , at the end . Um so , We have to say whether it's true or false that the product looks and feels fancy . Um {disfmarker} The {disfmarker} whether the product demonstrates technical innovation . Whether it's easy to use . Whether it's incorporating sort of the fashion element to attract the buyer . And whether it's a sort of recognisable Real Reaction product . And I have to go up onto the whiteboard and do this apparently ,", + "Industrial Designer : Okay .", + "Marketing : so {vocalsound} I'll go over here . {vocalsound} Right . So the first one is um , does the product look and feel fancy . So if we do a sort of a one {disfmarker} So {disfmarker}", + "Industrial Designer : Okay , well we have a single curve , which was {gap} maybe like the feel of the product's quite good .", + "Marketing : Yeah .", + "Industrial Designer : So uh {disfmarker}", + "Marketing : Okay .", + "Industrial Designer : Um , then we have the rubber kinda spongy feel , which was in at the time .", + "Marketing : Yeah . Yeah . Yeah .", + "Industrial Designer : Um , {vocalsound} sorry that'd be considered fancy .", + "User Interface : Yeah , I'd maybe give it a a two .", + "Marketing : {vocalsound} Of {disfmarker} but I think {disfmarker} What {disfmarker} Is one false , or is t one true ?", + "User Interface : One's true .", + "Marketing : I forgot . One's true , and okay . Seven's fal", + "User Interface : And a four is neutral .", + "Marketing : Four is neutral , okay . So {disfmarker}", + "Industrial Designer : So maybe {gap} maybe a two .", + "User Interface : Yeah , 'cause we haven't got the double curve , so we can't like say it's completely true .", + "Project Manager : {vocalsound} Go for one . {vocalsound} Yep .", + "Marketing : Right .", + "User Interface : {vocalsound} But it's pretty close . We've got almost everything we can .", + "Marketing : Okay . Right .", + "Project Manager : Okay .", + "Marketing : I gonna put underneath so I've got some more space . So , false is seven , true is one , and {disfmarker} So uh say about a two for fancy ,", + "Industrial Designer : Yeah .", + "User Interface : Yeah .", + "Marketing : you think ?", + "Project Manager : Yeah , why not not ,", + "Marketing : Okay .", + "Project Manager : m m maybe nearer three .", + "Marketing : Okay , well d you do an average at the end , I don't know . Um {disfmarker}", + "Project Manager : Two three . Well , it's just that uh saying something {disfmarker} {vocalsound} remember that when you look down , we've got solar power , we've got uh various other things you could have , and we're not going for these options .", + "Marketing : Uh-huh . This this is just this is just for like the look . Does it sort of look fancy rather than functional . So {disfmarker}", + "Project Manager : Mm-hmm . {vocalsound}", + "User Interface : Yeah , I suppose that might be in the technical innovation bit .", + "Marketing : Yeah , so that {disfmarker} so sh should we go for a a two on that ?", + "Project Manager : Okay .", + "Marketing : 'Kay . And I mean , how much does the product demonstrate technical innovation do you reckon ?", + "Industrial Designer : Um , {gap} deciding between the kinetic power or um the speech recognition , and if we had either of those for our budget , they both show a reasonable amount of speech recognition .", + "Marketing : D yeah . Okay . So , what about the pr The prototype as it is ,", + "Industrial Designer : Um {disfmarker}", + "Marketing : we've got we've got the speech recognition on it , haven't we .", + "Industrial Designer : But not the kinetic .", + "Marketing : But not the kinetic .", + "Industrial Designer : Like the power .", + "Project Manager : No . 'Cause you can't afford that {disfmarker} w we took that out too .", + "Industrial Designer : No , we c ca yeah , we can't afford both .", + "Marketing : Alright , so {disfmarker}", + "Project Manager : Didn't you ? Or {disfmarker}", + "Marketing : So it doesn't {disfmarker} It's pretty {disfmarker} The prototype as it is isn't sort of um fulfilling the {disfmarker}", + "Industrial Designer : No may is {disfmarker} maybe about neutral", + "User Interface : Maybe a three .", + "Industrial Designer : plus it it it's got something , but it hasn't got {disfmarker}", + "Marketing : {vocalsound} Okay . Yeah .", + "Project Manager : Well , wait a minute . In thirteen point seven we do have kinetic .", + "User Interface : I would give it more than a four .", + "Project Manager : The problem is we have to reduce down from there to get it down to twelve point five .", + "Industrial Designer : Right .", + "Project Manager : And one way of doing that would be to take out the kinetic .", + "Industrial Designer : Okay .", + "Project Manager : So , it's very much dependant on what you do with your options . And if you're definitely going for the sample sensor and sample speaker , then {disfmarker} because that {vocalsound}", + "Industrial Designer : 'Kay .", + "Marketing : Right , okay .", + "Project Manager : the other functions we've got in are are more at the {vocalsound} {disfmarker} The special material , the rubber , wood , titanium , et cetera , if you go for that , th that's at the high end 'cause that's point six , whereas down at uh just special colours uh is point two . Now you're trying to lose one point two , so it seems to me that if you're going for the sample sensors {disfmarker} speaker , you're basically then having to go for the cheaper options on everything else .", + "Marketing : Mm-hmm .", + "Industrial Designer : Okay .", + "Project Manager : And and the simple way to do it would be to have a battery , to have your uh sample sensor speaker ,", + "Industrial Designer : Um {disfmarker}", + "Project Manager : and then you're looking to uh take out uh point two ,", + "Marketing : S I'm just gonna check my email . {vocalsound}", + "Project Manager : which would be {disfmarker} come from the button supplements category .", + "Marketing : I'm just gonna check exactly what it said in the email for um the product .", + "User Interface : How much of a difference would it make if we made the case in plastic ? Because we did say that we don't wanna follow the fashion too much . If the buttons are rubber that might be spongy enough .", + "Project Manager : Um , interface type um ,", + "User Interface : And then it stand the test of time better .", + "Project Manager : well plastic rather than rubber . {vocalsound}", + "Marketing : Okay . But I {disfmarker}", + "Project Manager : That that that would make the significant difference . You could either {vocalsound} you could have it {disfmarker} If you have a in plastic rather than rubber , then that would uh enable you to get {disfmarker} you could keep kinetic then , you could keep your sample sensor , and you'd be looking to take out point two . So you could uh fiddle that down your special form at the bottom , or your special colour at the bottom .", + "Industrial Designer : Mm-hmm .", + "Project Manager : And that would enable you to to do it .", + "User Interface : Mm-hmm .", + "Marketing : Okay .", + "Industrial Designer : So it says if we make a slightly more fancy , then we lose points innovation , and if we make it more innovative innovative , then we lose points on it being fancy , so {disfmarker}", + "Project Manager : Yeah .", + "Marketing : Yeah .", + "Project Manager : Ye", + "Marketing : {vocalsound} {gap} , I just read the email again and it sort of says it's evaluate the design sort of as it is , I think , so I think we need to think about finance after we've sort of evaluated that design . I don't know whether we're doing it in the wrong order or something or .", + "Project Manager : Well , okay , but {disfmarker}", + "User Interface : Well , I suppose it's rubber as it is , isn't it .", + "Project Manager : It's rubber as it is , yes .", + "Marketing : So , I mean does this need to go up a bit or something , 'cause we've got both the both the um the speech {disfmarker}", + "Project Manager : We got {disfmarker} we've we've got thirteen point seven", + "User Interface : Yeah .", + "Project Manager : and we've got it in at the moment and if {disfmarker} and basically , we're going to reduce down from that .", + "Marketing : Yeah .", + "Project Manager : But the current one , you'd say would be fancy , would be too {disfmarker} {vocalsound}", + "Industrial Designer : Yeah , yeah .", + "Marketing : Yeah . Um , for for innovation , so we've got the speech the speech thing , and {disfmarker}", + "Project Manager : {vocalsound} Mm-hmm . I would've said about a two as well .", + "Marketing : Do you reckon a two ?", + "User Interface : Yeah , two or three . I'd be happy with a two .", + "Marketing : {vocalsound} Okay . Two .", + "Project Manager : Oh .", + "Marketing : And the next one is {disfmarker} I'll have to get it back up now . {vocalsound}", + "User Interface : {vocalsound}", + "Project Manager : The next on Well , I can just sing about . Easy to use . I would've said yes . I would go for a one on that at this point in time .", + "User Interface : Yeah . Yeah ,", + "Marketing : Okay .", + "User Interface : I would say so as well .", + "Project Manager : Um , incorporates elements of fashion to attract buyer . Well , yeah it certainly has some .", + "Industrial Designer : Um {disfmarker}", + "Project Manager : {vocalsound} {gap} .", + "User Interface : Yeah , it's got the cherry and the sponginess .", + "Industrial Designer : It does , yeah .", + "Marketing : Um {disfmarker}", + "Project Manager : Yep .", + "Marketing : Say about a three maybe ?", + "Project Manager : I don't know .", + "Industrial Designer : {vocalsound} Yeah , m um {disfmarker}", + "User Interface : Maybe two ?", + "Industrial Designer : Yeah , it was just doing it quite well .", + "Project Manager : Yep .", + "Industrial Designer : Um , I think we're gonna have to lose some of these , but the moment , as it stands , it's um {disfmarker}", + "Project Manager : Yeah , I woulda said two would seem reasonable .", + "Marketing : It's a two .", + "Project Manager : The product is a recognisable real {disfmarker} r uh {disfmarker} reaction product ?", + "Marketing : Yeah , this is {disfmarker}", + "Industrial Designer : Uh {gap} the sensor using all of its all of its products , all of its buttons ,", + "Marketing : This {disfmarker}", + "Project Manager : {vocalsound}", + "Industrial Designer : and it's got a fairly big label on the bottom saying where it comes from .", + "User Interface : Yeah , that's a bit rough at the minute . {vocalsound}", + "Marketing : Yeah . {vocalsound} So this is about sort of the corporate image of like new sort of sleek technology and all that sort of thing , as well as having the logo on and all that .", + "Project Manager : Oh .", + "Industrial Designer : Okay .", + "Marketing : So {gap} sort of {disfmarker} Is it sort of a recognisable product .", + "Industrial Designer : {vocalsound}", + "Project Manager : {vocalsound}", + "Marketing : Does it fit in with our other other products , which uh are sort of coffee makers and spacecraft . {vocalsound}", + "Project Manager : {vocalsound} S", + "User Interface : {vocalsound}", + "Marketing : {vocalsound}", + "User Interface : Uh , well it's got the same um speech feature as the coffee machine .", + "Marketing : What do y", + "Industrial Designer : Also it's kind of {gap} spongy rubberiness is maybe bit more kinda comfortable than {disfmarker} kinda sleek and new age .", + "Marketing : Yeah .", + "Industrial Designer : Um , it depends which way you look at it .", + "Marketing : Uh-huh .", + "Project Manager : Okay . So we're going for a two ,", + "Marketing : So {disfmarker}", + "Industrial Designer : Maybe a kind of three ? Uh d", + "Project Manager : {gap} three ?", + "User Interface : Yeah , two or three .", + "Marketing : Two or three ?", + "User Interface : Well , the logo would be more um recognisable on the actual thing . It's just that the pen wouldn't really write on that paper .", + "Project Manager : Sure .", + "Industrial Designer : {vocalsound}", + "User Interface : But um , I think the logo would definitely be recognisable .", + "Marketing : Yeah .", + "User Interface : And it does have attributes that other products do . Two ? Aye . Go for it .", + "Project Manager : Right , okay .", + "Marketing : Two or three . {vocalsound}", + "User Interface : {vocalsound}", + "Project Manager : {vocalsound} Two .", + "Marketing : {vocalsound} How {disfmarker}", + "Project Manager : Right , come on . That's that decided .", + "Marketing : Two . Okay .", + "Project Manager : Right . So {disfmarker}", + "Marketing : Right .", + "Project Manager : So we're now on to changing it to get it to fit in with the budget requirements , and then {disfmarker}", + "Marketing : Yeah .", + "User Interface : What does {disfmarker} what do all them numbers mean then ? Do we add them up and rate {gap} or anything ?", + "Marketing : {vocalsound} Yeah we s yeah , I think we sort of add them up so sort of at an average is gonna be {disfmarker} I'm just gonna do this in my head .", + "Project Manager : About a two .", + "Industrial Designer : {vocalsound}", + "User Interface : {vocalsound}", + "Project Manager : Two .", + "Marketing : One point eight isn't it or something . {vocalsound} I think , anyway . So yeah , pretty close to a two .", + "Industrial Designer : Yeah , so it's {disfmarker}", + "Marketing : So {disfmarker} So it's {disfmarker} I mean it's pretty good at the moment , but it's gonna get worse , isn't it .", + "Project Manager : Yep .", + "Marketing : But we've gotta try and make sure it doesn't get too bad .", + "Project Manager : Two b two b two {gap} , yeah .", + "Industrial Designer : So should we get {disfmarker} So are {gap} definite {disfmarker} Was it {disfmarker} thirteen point seven was the definite price rule if {gap} has .", + "Marketing : {vocalsound}", + "Project Manager : Yes .", + "Industrial Designer : Okay , so we need to {disfmarker}", + "Marketing : Yeah ." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 10, + "turns": [ + 125, + 218 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "water-proof , design , requirements , new remote control", + "speaker": "Project Manager" + }, + "summary": "Project Manager said that could be waterproof as well, and that would be very original because people could use it in the bath. Project Manager thought that they could bulk it with a plastic cover and the waterproof stuff, selling it altogether.", + "title": "Project Manager Thoughts About Waterproof Remote Control", + "relevant_turns": [ + [ + 36, + 59 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "high", + "specificity": "high", + "topic": "water-proof , design , requirements , new remote control", + "speaker": "Project Manager" + }, + "summary": "Project Manager said that it may be important for the remote to resist various shocks, that could be waterproof as well, and that would be very original because people could use it in their bath. After that Project Manager thought that they could bulk it with already that plastic thing and the waterproof stuff as well, maybe selling all that together, so like plastic protection and the waterproof box as well.", + "title": "Project Manager Thoughts About Waterproof Remote Control", + "relevant_turns": [ + [ + 36, + 59 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "solution , water-proof , shock-proof , technical demands , designing requirements , new remote control", + "speaker": "" + }, + "summary": "Project Manager said that it may be important for the remote to resist various shocks. User Interface said waterproof. Project Manager said it was original. User Interface said that if it wasn't waterproof it meant it could be covered in plastic and that it was only one of the shock because there were people that put plastic on the remote because they thought the remote was going to break.", + "title": "Team Talking About Water-Proof and Shock-Proof Requirements", + "relevant_turns": [ + [ + 36, + 61 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "high", + "topic": "solution , water-proof , shock-proof , technical demands , designing requirements , new remote control", + "speaker": "" + }, + "summary": "Project Manager said that it may be important for the remote to resist various shocks that could happen. User Interface said waterproof. Project Manager said it was very original. User Interface said that if it wasn't waterproof it meant that they could cover it in plastic. It was only one of the shock because people were worried that it could break and they put extra plastic around it.", + "title": "Team Talking About Water-Proof and Shock-Proof Requirements", + "relevant_turns": [ + [ + 36, + 61 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "remote tracking , designing requirements , new remote control", + "speaker": "Industrial Designer , Project Manager" + }, + "summary": "Project Manager said that they should have something to find the remote control. Industrial Designer said like a special button on the TV so the remote could make a sound. Project Manager said something like they whistled and the remote beeped. Industrial Designer said whistle tracking. Project Manager said it was a very original idea.", + "title": "Industrial Designer and Project Manager Talking About Remote Tracking", + "relevant_turns": [ + [ + 64, + 84 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "high", + "specificity": "high", + "topic": "remote tracking , designing requirements , new remote control", + "speaker": "Industrial Designer , Project Manager" + }, + "summary": "Project Manager said that they should have something because most of the time it lost the remote control. Industrial Designer said that they should have a special button on the TV so the remote could made a sound. Project Manager said that something like they whistled and the remote control beeped. Industrial Designer said whistle tracking. Project Manager said that was a very good and original idea.", + "title": "Industrial Designer and Project Manager Talking About Remote Tracking", + "relevant_turns": [ + [ + 64, + 84 + ] + ] + } + ], + "source": [ + "User Interface : I is there a matter for a new remote control ?", + "Project Manager : {vocalsound} Yeah if it's trendy , original I d fulfil the user needs .", + "User Interface : Is it uh a single device remote control or is it a multi-device remote control ?", + "Project Manager : We have to discuss that point .", + "User Interface : Ah", + "Project Manager : On {disfmarker}", + "User Interface : this is not defined at all ?", + "Project Manager : yeah you you can suggest points like this . So what what {disfmarker}", + "User Interface : Ah , okay .", + "Project Manager : so we have to decide for example if it can control one device or multiple . So what's {disfmarker} what are your ideas about that ?", + "User Interface : {vocalsound}", + "Project Manager : Maybe I can have the {disfmarker} your opinion from the marketing side ?", + "User Interface : Well uh do we sell other stuff ? Uh if if we bundle the remote control with something uh to sell then it could be a single device , otherwise it could be programmable one otherwise who would buy a remote control from us .", + "Project Manager : Okay , so if it selled uh by its own i it it would rather be for multiple device .", + "User Interface : Yeah .", + "Project Manager : {vocalsound} Do you agree ?", + "Industrial Designer : Mm-hmm .", + "Project Manager : Yeah . So maybe it should be for multiple devices . And uh do you have any ideas um of uh design ideas or any uh uh technical requirement we we should uh fulfil ?", + "Industrial Designer : {vocalsound} I think we shouldn't have too many b for my part . I think {disfmarker}", + "User Interface : No , I couldn I cannot fi think of any requirements right now . {vocalsound}", + "Industrial Designer : If we don't have so many buttons could be nice .", + "Project Manager : {vocalsound} Few buttons . Okay .", + "User Interface : {vocalsound}", + "Project Manager : And do you have it also to be {disfmarker} to be lighted in order to be used in the dark ? Might be a good idea .", + "Industrial Designer : {vocalsound} Yeah .", + "Project Manager : Okay . And do you have any um any uh idea of the trend {disfmarker} the trend in domain , what it shouldn't {disfmarker} it should look like , or things like that ?", + "Industrial Designer : {vocalsound} Something which is not squarey maybe uh , not a box .", + "User Interface : Mm .", + "Project Manager : With rou okay . Like for {disfmarker} okay .", + "User Interface : Something like that , least fits in your hand .", + "Project Manager : Okay .", + "User Interface : {vocalsound} Yeah .", + "Industrial Designer : Yeah .", + "User Interface : The basic requirement .", + "Project Manager : So . Fit in your hand , yeah .", + "User Interface : {vocalsound} Only a buck .", + "Project Manager : And also it have , i it may be {vocalsound} it may be important for the remote control to be uh {disfmarker} To , to resist to various shocks that can happen if it fall .", + "User Interface : {vocalsound}", + "Industrial Designer : Mm-hmm .", + "User Interface : Waterproof . {vocalsound}", + "Project Manager : {vocalsound} Water-proof as well .", + "Industrial Designer : {vocalsound} And I think we should have a device {disfmarker}", + "Project Manager : Maybe it is original because you can uh use it in your uh {disfmarker} in your bath whereas the others can't .", + "User Interface : {vocalsound}", + "Marketing : {vocalsound}", + "Project Manager : Maybe water-proof would be very original .", + "Industrial Designer : Sorry . {gap}", + "Marketing : {vocalsound}", + "Project Manager : Havin having a water-proof remote control so that the people can uh use it in their bath .", + "User Interface : Mm .", + "Project Manager : That could be uh {disfmarker}", + "User Interface : B it seems uh so , but uh if you don't have an waterproof remote control it means you can just cover it with some plastic and you can sort of f", + "Project Manager : Yeah but , it is still something uh you have to buy and that is um not maybe very {disfmarker}", + "User Interface : And , and that's one of the {disfmarker} that's one of the shock {disfmarker} I mean there are people that have a remote control and they are worried that it's going to break and they put some extra plastic around it .", + "Project Manager : Yeah , mayb B", + "User Interface : That's people {gap} they actually do it themselves .", + "Project Manager : But maybe we can bulk it with uh already this plastic thing and uh the waterproof uh stuff as well .", + "Industrial Designer : Yeah . {gap} directly .", + "User Interface : I it will look a bulky in that case .", + "Project Manager : Yeah . Maybe we can sell uh all that together , so so plastic protection and uh and a waterproof box as well .", + "Industrial Designer : Yeah .", + "Project Manager : That might be good uh track to follow .", + "User Interface : Like as an optional thing .", + "Project Manager : Optional or selled with it ?", + "Industrial Designer : {vocalsound} And I I think we should have something , most of the time I I lose my remote control .", + "Project Manager : Yeah .", + "Industrial Designer : We should have s uh special bu button on the T_V_ to make the remote control beeping .", + "Project Manager : Maybe we can have uh {disfmarker} But we don't design the T_V_ .", + "Marketing : {vocalsound}", + "Project Manager : Maybe we can have uh something you whistle and uh the remote control uh beep .", + "Industrial Designer : Ah yeah .", + "Marketing : {vocalsound}", + "User Interface : Barks .", + "Industrial Designer : Yeah . {vocalsound}", + "Project Manager : Yeah , barks , yeah .", + "Industrial Designer : {vocalsound} Barks .", + "Project Manager : So we can uh have a whistle uh remote control ?", + "Industrial Designer : Yeah . Yeah whistle .", + "Project Manager : I don't know , whistle-able ? {vocalsound} Th", + "Industrial Designer : Whistle tracking . {vocalsound}", + "Project Manager : {vocalsound} Whistle tracking yeah . Whistle tracking remote control . That's a good idea , that's very original and that's can uh improve .", + "User Interface : {vocalsound} That's that's quite cool , but uh of course we {disfmarker} you don't normally need uh any audio uh recording stuff on your remote control right ?", + "Project Manager : Yeah d d uh .", + "User Interface : So i it's just going to add t to the cost .", + "Project Manager : Yeah but s still we have to mm we have to {vocalsound} have an advantage over our competitors . I think this is a good advantage .", + "User Interface : {vocalsound} It's cool . I think I like the idea , but I'm not sure about the what you ,", + "Project Manager : Yeah . We have to ask {disfmarker}", + "User Interface : who is giving {disfmarker} who's giving who's giving our budget . Who's {disfmarker}", + "Project Manager : Yeah . We have to ask the quest of that's uh design to the uh Industrial um Designer .", + "User Interface : Yeah . Yeah .", + "Industrial Designer : Yeah . {vocalsound} yeah {vocalsound}", + "Project Manager : {vocalsound} Which is you .", + "User Interface : 'Kay . {vocalsound}", + "Project Manager : {vocalsound} Okay so try to find that for next meeting . {vocalsound}" + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "test", + "file_id": 27, + "turns": [ + 196, + 212 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "breach , protocols", + "speaker": "Hon . Navdeep Bains ( Minister of Innovation , Science and Industry )" + }, + "summary": "Hon. Navdeep Bains said the breach that occurred was completely unacceptable, and that their government had denounced it, so that such a breach didn't occur again because it was not the way to deal with sensitive information. Hon. Navdeep Bains stated that the appropriate protocols would be followed to proceed with the appropriate actions to ensure that such breaches didn't occur going forward.", + "title": "Hon. Navdeep Bains' View on the Breach", + "relevant_turns": [ + [ + 3, + 5 + ], + 10, + 13 + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "fully", + "specificity": "normal", + "topic": "breach , protocols", + "speaker": "Hon . Navdeep Bains ( Minister of Innovation , Science and Industry )" + }, + "summary": "Hon. Navdeep Bains (Minister of Innovation, Science and Industry); The breach that occurred is completely unacceptable; Our government has denounced this breach; That breach was not the way to deal with such sensitive information; Going forward, we will ensure that such a breach does not occur again; There are appropriate protocols in place to look into such breaches. Those protocols will be followed, and the appropriate actions will be taken to ensure that such breaches do not occur going forward.", + "title": "Hon. Navdeep Bains' View on the Breach", + "relevant_turns": [ + [ + 3, + 5 + ], + 10, + 13 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "leak , market", + "speaker": "Mr. Ziad Aboultaif ( Edmonton Manning , CPC )" + }, + "summary": "Mr. Ziad Aboultaif said the markets were shocked and investors worried when leaks came to light before the market opened. Mr. Ziad Aboultaif also inquired about the government's posture regarding the consequences established in section 34 of the Statistics Act., which included a fine, imprisonment, or both.", + "title": "Mr. Ziad Aboultaifs Inquires About the Leak in the Market", + "relevant_turns": [ + 1 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "high", + "topic": "leak , market", + "speaker": "Mr. Ziad Aboultaif ( Edmonton Manning , CPC )" + }, + "summary": "Mr. Ziad Aboultaif explained the markets were shocked when leaks came to light before the market opened. Mr. Ziad Aboultaif mentioned Section 34 of the Statistics Act indicated disclosing information might deserve a fine not exceeding five thousand dollars or to imprisonment not exceeding five years or both, inquiring how the government would proceed.", + "title": "Mr. Ziad Aboultaifs Inquires About the Leak in the Market", + "relevant_turns": [ + 1 + ] + } + ], + "source": [ + "The Acting Chair (Mr. Bruce Stanton) : Okay. We will move to the next questioner, Mr. Aboultaif from Edmonton Manning. Mr. Aboultaif, go ahead with your question.", + "Mr. Ziad Aboultaif (Edmonton Manning, CPC) : Thank you, Mr. Chair. Mr. Chair, last week markets were shocked when leaks regarding the state of our economy came to light before the market even opened. This caused worry to investors at home and abroad about the integrity of our markets and the nature of the leak, which is, in itself, unprecedented. Section 34 of the Statistics Act indicates the following: Every person who, after taking the oath set out in subsection 6, is guity of an offence and liable on summary conviction to a fine not exceeding five thousand dollars or to impreisonment for a term not exceeing five years or both: wilfully discloses or divulges directly or indirectly to any person not entitled under this Act to receive the same any information obtained by him in the course of his employment that might exert an influence on or affect the market value of any stocks, bonds or other security or any product or article, or uses any information described in paragraph for the purpose of speculating in any stocks, bonds or other security or any product or article My question for the minister is this: Does the government consider this case to be subject to paragraph 34 or 34 and a criminal offence, yes or no?", + "The Acting Chair (Mr. Bruce Stanton) : The honourable minister.", + "Hon. Navdeep Bains (Minister of Innovation, Science and Industry) : Mr. Chair, my hon. colleague is absolutely right that the current situation with regard to the COVID crisis is deeply problematic, and we want to make sure that any information we share with the Canadian public with regard to economic measures or labour market numbers follows the appropriate process. The breach that occurred is completely unacceptable. Our government has denounced this breach. That breach was not the way to deal with such sensitive information. The member has alluded to several paragraphs within the Statistics Act. I can assure him that we are looking into this matter and that Statistics Canada is looking into this issue as well. Going forward, we will ensure that such a breach does not occur again, because it's important that we continue to have the confidence of Canadians during this current health care crisis.", + "Mr. Ziad Aboultaif : Okay, I will take that as a yes. So this matter should be investigated, yes or no?", + "Hon. Navdeep Bains : As I have indicated very clearly, what has happened is completely unacceptable. This breach should not have occurred. This matter is being looked into, and we want to assure Canadians going forward that", + "The Acting Chair (Mr. Bruce Stanton) : Back to Mr. Aboultaif.", + "Mr. Ziad Aboultaif : In that case, the minister said the matter will be looked into. Basically, my understanding of this case is that Statistics Canada is going to investigate itself, or does the minister think that the government should refer this to the RCMP?", + "Hon. Navdeep Bains : Sorry, could you repeat that question? I had a bit of an issue and could not hear the question.", + "Mr. Ziad Aboultaif : Will Statistics Canada investigate itself or will the government refer this to the RCMP?", + "Hon. Navdeep Bains : Mr. Chair, there are appropriate protocols in place to look into such breaches. Those protocols will be followed, and the appropriate actions will be taken to ensure that such breaches do not occur going forward.", + "The Acting Chair (Mr. Bruce Stanton) : Mr. Aboultaif, you have about a minute left. Go ahead.", + "Mr. Ziad Aboultaif : The minister indicated that this will be investigated, but during the investigation into the SNC-Lavalin scandal, the Liberal staff refused to co-operate. Will the minister commit today that all Liberal staff will co-operate with this investigation?", + "Hon. Navdeep Bains : Again, we've been clear that it's important that any such breach be taken seriously. What has happened is unacceptable, and we will ensure that the appropriate steps are taken to make sure that such breaches do not occur going forward.", + "The Acting Chair (Mr. Bruce Stanton) : You have time for one short question, Mr. Aboultaif. Go ahead.", + "Mr. Ziad Aboultaif : There's no doubt about the general terms, but I need to make sure that the government will commit that its staff will co-operate. Yes or no?", + "Hon. Navdeep Bains : The process is very clear. The protocols are very clear. The law is very clear, and we will make sure that the process is followed and the law is upheld." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 50, + "turns": [ + 66, + 75 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "legislation , sports infrastructural construction , healthy environment", + "speaker": "" + }, + "summary": "Dawn Bowden AM asked what might be the timescale to have legislation banning energy drinks and what recommendations would they make concerning the lack of changing rooms and toilet facilities in the community sports infrastructure. Dr Frank Atherton said they needed to undertake a detailed consultation on them before having legislation implemented.", + "title": "Legislation and Sports Infrastructural Construction for Healthy Environment", + "relevant_turns": [ + [ + 0, + 2 + ], + 6 + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "high", + "specificity": "high", + "topic": "legislation , sports infrastructural construction , healthy environment", + "speaker": "" + }, + "summary": "Dawn Bowden AM said in the draft plan there were measures suggesting legislation for restricting price promotions and banning energy drinks and wanted to know the timescale of such legislation. Also, the issue of community sports infrastructure had no changing rooms and toilet facilities. Dr Frank Atherton said that there were things they might wish to legislate but needed to undertake quite detailed consultation and mirror what was happening in England and Scotland to some degree around the consultations they were having on energy drinks adding that legislation may well be one of the outcomes of the consultation. On the issue of sports infrastructure, Dr Frank Atherton said they were pleased to see the use of health impact assessment as a tool and they were working on how that would inform policy and how that would be applied in issues such as policy decisions through Government, but also in more downstream issues about how they created the public infrastructure that the public could and should be using.", + "title": "Legislation and Sports Infrastructural Construction for Healthy Environment", + "relevant_turns": [ + [ + 0, + 2 + ], + 6 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "sports infrastructure", + "speaker": "Dawn Bowden AM" + }, + "summary": "When Dawn Bowden AM talked about sports infrastructure, particularly in new schools was that there were no changing rooms and toilet facilities in some of the new schools.", + "title": "Improving the Public Facilities", + "relevant_turns": [ + 5 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "high", + "specificity": "normal", + "topic": "sports infrastructure", + "speaker": "Dawn Bowden AM" + }, + "summary": "Dawn Bowden AM said the money for community sports infrastructure, particularly for new schools hasn't built changing rooms and toilet facilities into the new buildings and suggested when developing schools, they should make sure that they had those kinds of facilities so as to be accessible to the wider public.", + "title": "Improving the Public Facilities", + "relevant_turns": [ + 5 + ] + } + ], + "source": [ + "Lynne Neagle AM : Okay. Thank you. We've got some questions now on healthy environments from Dawn Bowden.", + "Dawn Bowden AM : Thank you, Chair. In the draft plan, some of the measures in there suggest legislating for restricting price promotions and banning energy drinks, and that sort of thing. Do you think that, if we go down that road, there's going to be time within this Assembly to introduce such legislation? And, if not, what do you think might be the timescale for such legislation?", + "Dr Frank Atherton : It may well be that there are things in Wales that we might wish to legislate on, and you've mentioned two of them, and they're good examples. We would, obviously, need to undertake quite detailed consultation on those and, in a way, we need to mirror what's happening in England and in Scotland\u00a0to some degree around the consultations they're having on energy drinks. We also need to influence the issues that are not devolved to us and we seek to do that. As to your question of legislative time, I'm not really in a position to answer that. What I could say is that legislation may well be one of the outcomes of the consultation. There may well be things that we wish to choose to legislate on. The timing of that will have to be subject to other pressures, and I come back to the point that legislation, of course, is one of the tools that we've got\u2014we need to deploy them all.", + "Dawn Bowden AM : Sure, I understand that, that you could do other things. I know\u2014. We've heard from the Government, on other calls for legislation, that the programme's very tight, certainly for this term, so I was just wondering whether we might get that in, but okay. If I turn now to the planning system\u2014and this might not be something that you have great deal of knowledge of; I'd just welcome your view on this, because, when we discussed with stakeholders, we talked about whether the planning system, for instance, could be used to, as an example, restrict hot food takeaways around schools and so on. Would that be a measure that you would support, something like that?", + "Dr Frank Atherton : I think it's definitely something we want to look at and, of course, that question is asked in the consultation, so we would like to know people's views on that. It's an interesting one. I think there is a question\u2014a really important question\u2014about how we can use the planning system more effectively. I've discussed with Nathan on a number of occasions, with planning colleagues in Welsh Government and in local authorities, about the art of the possible, let's say. There may be things that we could think about and we want to get those ideas through the consultation. The specific question around takeaways, particularly takeaways near schools, is often asked. I was very interested to see, up in the north-east, some time ago, that one of the local authorities up there did put a moratorium on the opening of new fast-food venues near to schools, or indeed in areas where levels of obesity and overweight were particularly high. I understand London is now\u2014some London boroughs are now\u2014experimenting with that as well. So, that gave me comfort, because maybe there are powers within local authorities that can be used more effectively.\u00a0I think my view at the moment is that the jury's kind of out on whether those are effective and how effective they're going to be. But the fact that we have some initiatives around the UK does give us an opportunity to study that and to learn from experience perhaps and then, if it is shown to be beneficial, to think about that here in Wales, yes.", + "Dawn Bowden AM : Sure, because it will only be one of a suite of measures anyway. Of itself, it wouldn't address the problem, but, added to other initiatives, I guess it would. Can I just ask you briefly, then, about community sport infrastructure and, in particular, of new schools? So, Welsh Government, as you know, has ploughed a huge amount of money into the twenty-first century schools programme. What we heard when we spoke to stakeholders recently, particularly headteachers, was that, in some of the new schools that have been built, we haven't had changing rooms and toilet facilities, for instance, built into the new buildings. So, if we're going to try and utilise these buildings for general community activity to get kids and the wider public, actually, more active, do you think that's something that we ought to be building in? Again, not your particular direct area of responsibility, but something that you might have an input into, is that, when we're developing schools, we should be making sure that they have those kinds of facilities so that they become accessible to the wider public. Is that something that you would be prepared to make a recommendation around?", + "Dr Frank Atherton : Well, it's certainly a fascinating area and one that I think has a lot of potential. It goes\u2014. You're right to raise it in the context of schools, and I can understand why this committee would, but I think it goes beyond that, actually, into all developments in the public sector and how they're developed and whether we're building health into our environment, which perhaps is your starting point. One of the things that I was really pleased to see in terms of the Public Health (Wales) Act 2017 that was passed a couple of years ago was the use of health impact assessment as a tool, and we're still working on how that will inform policy and how that will be applied in issues such as policy decisions through Government, but also in more downstream issues about how we create the public infrastructure that the public can and should be using. And so I would like to see the use of health impact assessments to a much greater degree to inform those kinds of decisions. If you apply that kind of lens and you take the point, which is inherent in your question, I think, that schools are not just for kids, they're for communities, then you would\u2014it would lead you to a conclusion that you would perhaps design and build them in a different way. So, on a personal basis, I would certainly support your view that we should be looking to use the sports environment in schools in the same way as we use leisure centres. There are all kinds of barriers in there, and I understand all of that, and it's not really my field, exactly as you say, but, as a matter of principle, I think it's a good one to pursue.", + "Dawn Bowden AM : Okay. Thank you. And widening it out to other public services buildings as well.", + "Dr Frank Atherton : Indeed.", + "Dawn Bowden AM : Yes. Okay. Thank you." + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "test", + "file_id": 7, + "turns": [ + 98, + 251 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "industrial design , product", + "speaker": "" + }, + "summary": "The Industrial Designer made a slide presentation to present his new industrial design for the remote control. On a slide, he expressed his will to make it infrared instead of laser. He considered that technology would be better to control the TV and cheaper than laser, with a cost of approximately eight Euros. On the next slides, he explained the remote control would have an infrared bulb and provided some electronic components' explanation. On the last slide, he stated the remote control should be wireless, but this would also raise the question of how to charge it. The User Interface was surprised with the wireless remote-control idea using a wire to charge. The Industrial Designer added it could be both: with a wire or not. The Marketing was very interested in the cost and raised the user's point of view to have a wireless remote control. The project Manager stepped in to ask if a cable between the remote control and the TV would be a good idea and mostly would it be cheaper. The Industrial Designer acknowledged using a wire would be cheaper but less practical. The project Manager focused on the people's point of view if to have it, wireless and believed it would be easier to have a link between the remote control and the television. The Marketing started his presentation. He pointed several issues out: the remote control presented too many buttons, it got often lost in the room, difficult to learn and RSI problems. The Marketing personal preferences were to meet the user needs and to make it fancy to sell more than the concurrent and definitively with fewer buttons. The Project Manager directly asked the User Interface if it would be possible to have fewer buttons and still have the same functionality and a powerful remote control. The User interface answered it would be possible by assigning several functions to the same button.", + "title": "Different Points of Views to Elaborate a Remote Control", + "relevant_turns": [ + [ + 8, + 71 + ], + 84, + [ + 110, + 124 + ], + [ + 129, + 152 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "fully", + "specificity": "high", + "topic": "industrial design , product", + "speaker": "" + }, + "summary": "The Project Manager explained the job was to design and to give an industrial design of the remote control. He expressed the remote control would be infrared control, so the problem would be how to relate the remote control device and the TV. He believed infrared base was better to control TV, and it would also be cheaper as it had less technology than laser. The average prices he believed it would cost was around eight Euros. He thought with a wire it would be cheaper but less practical.", + "title": "How to Elaborate a Remote Control Meeting User's Needs", + "relevant_turns": [ + [ + 8, + 71 + ], + 84, + [ + 110, + 124 + ], + [ + 129, + 152 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "wireless control", + "speaker": "Project Manager , Industrial Designer" + }, + "summary": "The Project Manager disagreed with the Industrial Designer regarding the possibility to make the remote control wireless because he questioned if it would be feasible and if it would be cheaper than with a wire linking the remote control and the television. The Project Manager has expressed his doubts if a wireless remote control was meeting the user's wish.", + "title": "The Project Manager's Points of Disagreement for a Wireless Device", + "relevant_turns": [ + [ + 38, + 78 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "high", + "topic": "wireless control", + "speaker": "Project Manager , Industrial Designer" + }, + "summary": "The Project Manager expressed his disagreement with the Industrial Designer's expose regarding the possibility to make the remote-control wireless. He questioned if it would be feasible, if it would be cheaper than with a wire linking the remote control and the television, which would also avoid losing it in the room. His main concern remained if the wireless remote control would meet the user's wish.", + "title": "The Project Manager's Points of Disagreement for a Wireless Device", + "relevant_turns": [ + [ + 38, + 78 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "problem , less buttons", + "speaker": "User Interface Designer" + }, + "summary": "The User Interface Designer recommended adding several functions to the same buttons. To avoid making it more difficult for the users, it was also suggested making it intuitive. The User Interface Designer explained, not only to add more functions to a button but also to have a switch button allowing to have access to an interactive menu with all functions displayed.", + "title": "The User Interface Designer's Solution to Reduce the Quantity of Buttons", + "relevant_turns": [ + [ + 132, + 152 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "fully", + "specificity": "high", + "topic": "problem , less buttons", + "speaker": "User Interface Designer" + }, + "summary": "The User Interface Designer explained it would be possible to have less buttons by mixing several functions in one button. He also explained by having a switch button, it would allow the user to access a switch menu in which you could categorize the functions into several classes.", + "title": "The User Interface Designer's Solution to Reduce the Quantity of Buttons", + "relevant_turns": [ + 132, + [ + 144, + 152 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "bulb", + "speaker": "Industrial Manager" + }, + "summary": "The Industrial Manager explained on his slide presentation the presence of a bulb on the remote control. According to him, the bulb and an infrared bulb would be somewhere inside the device to make it wireless. The bulb would appear in blue and the infrared bulb would appear in red.", + "title": "Presence of Different Bulbs", + "relevant_turns": [ + [ + 24, + 30 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "fully", + "specificity": "normal", + "topic": "bulb", + "speaker": "Industrial Manager" + }, + "summary": "The Industrial Manager explained the presence of a bulb and an infrared bulb inside the system of the remote control.", + "title": "Presence of Different Bulbs", + "relevant_turns": [ + 24 + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "cheap price", + "speaker": "Project Manager" + }, + "summary": "The Project Manager raised the issue to have less buttons and still have the same functionality and to have powerful remote control. He was also investigating to know if the wireless proposition would be a cheaper technology. He was answered, it would be a cheaper technology than laser.", + "title": "How to Obtain a Cheaper Price", + "relevant_turns": [ + 17, + 50, + [ + 63, + 72 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "fully", + "specificity": "normal", + "topic": "cheap price", + "speaker": "Project Manager" + }, + "summary": "The Project Manager was interested to know if the infrared control was a cheaper technology.", + "title": "How to Obtain a Cheaper Price", + "relevant_turns": [ + 17, + 50, + [ + 63, + 72 + ] + ] + } + ], + "source": [ + "Project Manager : So , next I propose the Industrial User Interface to present things .", + "Industrial Designer : Okay , okay .", + "Project Manager : So you you're {disfmarker}", + "Industrial Designer : Participant two . Yeah .", + "Project Manager : Um . Okay .", + "Marketing : {gap}", + "Industrial Designer : {vocalsound} The rationale must be {vocalsound} design , or {disfmarker}", + "Project Manager : So , Baba is the uh the Industrial Designer . Okay .", + "Industrial Designer : So we can move to the next slide . As you all know , you know m my job is to design you know uh to give an industrial design of the remote control . So the re basically the remote control will be , you know , infrared control , so the problem is how to relate the", + "Project Manager : Mm-hmm .", + "Industrial Designer : how to relate the remote control device , like for example this one I h I'm holding in my hand and the T_V_ . So , this one is leather bu based", + "Marketing : Mm .", + "Industrial Designer : but {disfmarker} I propose a nifra infrared base {vocalsound} you know , so so for me I think that it is better {vocalsound} it's bet it's better to control T_V_", + "Project Manager : {vocalsound}", + "Marketing : {vocalsound}", + "Industrial Designer : so you know , so it's it will be cheaper and it is less technology than , you know {disfmarker} For the cheap price we have , for the cheap price we want to {disfmarker}", + "Marketing : True .", + "Project Manager : So you mean that infrared control is a cheap technology ?", + "Industrial Designer : I think it's cheaper than laser , so {vocalsound} .", + "Marketing : Okay .", + "Project Manager : Yeah . Do y you know the requirements for the remote control ? Twelve , nearly thirteen ,", + "Marketing : What the cost is ?", + "Project Manager : yeah . The cost {disfmarker}", + "Marketing : Twelve , twelve a half .", + "Industrial Designer : Yeah , I think for the cost we want {disfmarker} for the cost we want {vocalsound} {disfmarker} it's better to have uh uh Let's see . Yeah . You can move to the next slide , so . So the di the differen the findings you know what you find inside the re i the the system here inside it is just , you know a bulb and an infrared bulb , so here for example the infrared bulb will be here", + "Project Manager : Mm-hmm .", + "Industrial Designer : and the bulb it will be somewhere inside .", + "Marketing : That might just {disfmarker} So .", + "Industrial Designer : You can go to the next slide .", + "Project Manager : Okay .", + "Industrial Designer : I have some kind of pictures you know , here . You have the b the bulb , it is a blue the blue stuff here and the infrared and the infrared bulb it is the red stuff", + "Project Manager : Yeah .", + "Industrial Designer : you know and so and you have the other subcomponent that are not really here so important , so .", + "Project Manager : What is this ?", + "Industrial Designer : This is in fact some other component that are in between the electrical de the electronic device .", + "Project Manager : Okay .", + "Industrial Designer : Look . But here what I wanted to emphasise it is just you know the bulb and {gap} .", + "Project Manager : Okay .", + "Industrial Designer : So and the next slide , it is the last one it's {disfmarker} So it's {disfmarker} I think it should be wire {vocalsound} wireless re remote con {vocalsound} Because you know , it's easier to manage and you know because you f the b the the battery problem can hold you know will you use a battery or the a wire to connected you . Or maybe some kind of thing that we can have both , but you know , I at my side prefer a wireless .", + "Project Manager : Okay .", + "Marketing : Okay .", + "Industrial Designer : Okay , so if you have some question I didn't answer ?", + "Marketing : What's the average price of this technology then ?", + "Industrial Designer : Well the avera the average prices I think that this technology will cost , I dunno , around eight Euros , so . Or at least you know , the", + "User Interface : So what , the wireless remote control ? There's a wire {vocalsound} with remote control ? {vocalsound}", + "Industrial Designer : {vocalsound} You'd {disfmarker} yes , you can . It's so so bres you have to decide how how you will you know , put some energy inside , so you can think about wireless or you know it's it's a question that we can raise , so . We can think that you know , with the wire , you know , without a wire . We can have both also .", + "User Interface : Okay .", + "Project Manager : So you think that uh {vocalsound} a cable between the remote control {vocalsound} and the T_V_ {vocalsound} {disfmarker} won't be a good idea .", + "Industrial Designer : {vocalsound}", + "User Interface : {vocalsound} Okay . Okay .", + "Project Manager : {vocalsound} No it wou maybe it will be cheaper {vocalsound} I dunno , I just may maybe you making a solu", + "Marketing : But this is what you would like to ask the user first and I don't think the user would be ready to have a {disfmarker}", + "Industrial Designer : {vocalsound}", + "Project Manager : {vocalsound} Yeah ,", + "User Interface : {vocalsound} Wireless remote control {vocalsound} .", + "Project Manager : but {disfmarker}", + "Marketing : I don't think {disfmarker} well , yeah , I don't think he would ,", + "Industrial Designer : Yeah , but some pa I always want to have you know ,", + "Project Manager : {vocalsound}", + "Marketing : but in a sense {disfmarker}", + "Industrial Designer : sometime I want to have wire because you know .", + "Project Manager : Yeah but as Industrial Designer , do you think that it will be feasible to have uh linked or to have link between the remote control and the television ?", + "Industrial Designer : {gap} {vocalsound}", + "Project Manager : {vocalsound} I'm just asking you . Do you think it will be cheaper ?", + "Industrial Designer : Uh , {vocalsound} I don't {vocalsound} think it will be too much .", + "User Interface : {vocalsound}", + "Industrial Designer : {vocalsound} {vocalsound}", + "Project Manager : {vocalsound} Could you answer please ? {vocalsound}", + "User Interface : Okay .", + "Industrial Designer : Have to think about the question , you know , 'cause it's {disfmarker} I think that you know you can always you know {disfmarker}", + "Project Manager : {vocalsound} Okay .", + "Industrial Designer : {vocalsound} I think wha wha with the wire it's mm cheaper but you know the wireless it's more practical , so .", + "Project Manager : Yeah , but I think the wireless problem is more the um David Jordan's problem .", + "User Interface : Mm-hmm .", + "Marketing : The wire ?", + "Project Manager : As it's {disfmarker} yeah .", + "Marketing : Yeah . True .", + "Industrial Designer : Okay , yeah .", + "Project Manager : I think it's more your problem . Mayb maybe you have just to to kind of research or try to ask people if they will like something wireless or not .", + "User Interface : Mm-hmm .", + "Marketing : Uh that's my job . That's the {disfmarker}", + "Project Manager : {vocalsound} Okay , {gap} I'm sorry .", + "Marketing : Now the {disfmarker}", + "Project Manager : So {disfmarker}", + "Industrial Designer : Yeah but , it should be an agreement , you know , because {disfmarker} even if you can think of the wireless , it is it's it is the job of the {vocalsound} the the g Graphical User Designer , but you know . If it is a lot cheaper and if you want to reach for example some the the money you have , if you want to use , {vocalsound} so {vocalsound} it can be good to have a wireless , it it is a question .", + "Project Manager : {vocalsound} So", + "User Interface : Okay .", + "Project Manager : just think of um the usability .", + "User Interface : Design a wireless remote control . {vocalsound}", + "Project Manager : Yeah . Just think of the problem . If when you have wireless remote control and if you lose it ?", + "User Interface : Yeah .", + "Marketing : Yeah .", + "Project Manager : I think it's would be easier to have {vocalsound} a link between the remote control and the television ,", + "Marketing : Well that's actually one of the point , yeah ? True .", + "Project Manager : yeah .", + "Marketing : This you will see in my presentation then .", + "Marketing : So it's it's interesting information , I think . And then um yeah , the remote controls like the one you've shown previously it's not so {disfmarker} doesn't fit the user requirements sometime , because it's too many buttons and so on . So we should change this as well . And uh users are actually zapping a lot , so they're using the device intensively , that's something to take into account as well . And um , you know , ten percent of the buttons are actually used in the remote control . And uh this is one of the main point for me . But I'll come back to it later . 'Kay . Could you go next slide ? Uh , so as you said uh ,", + "Project Manager : Mm-hmm .", + "Marketing : remote controls are often lost somewhere in the room .", + "Project Manager : {vocalsound}", + "Marketing : So this is from the experiments we've done ,", + "Project Manager : {vocalsound} {vocalsound}", + "Marketing : so if we could solve this problem this would be interesting for the user , I think . Um it takes too much time to learn how to use the remote control for thirty five percent of the people . And uh remote control are really bad for R_S_I_ problems for twenty six percent of the users .", + "Project Manager : {vocalsound} What is R_S_I_ ?", + "Marketing : R_S_I_ is like , when you're using the same um {disfmarker} doing the same movement several times , then you get injured .", + "Industrial Designer : {vocalsound} Yeah .", + "Project Manager : Ah um okay . {vocalsound}", + "Marketing : Okay ? So , those numbers are less important then the previous one , but still it has to be taken to count . So last slide . Um so my pres personal preferences for this problem is we have to meet the user needs . If we can make it look fancy then we might sell more than our uh concurrent , okay .", + "Industrial Designer : Okay .", + "Project Manager : Mm-hmm .", + "Marketing : And definitely if it could have less buttons , still maybe the same number of um functions , but less buttons ,", + "User Interface : Functions .", + "Marketing : this would definitely be a good way of selling more . Okay .", + "Industrial Designer : Okay .", + "Marketing : So {disfmarker}", + "Project Manager : Mm okay . And just to have uh an idea , do you think you as the User Interface Designer to would it be possible to have less buttons and still have the same functionality and to have powerful remote control , you think it's possible ?", + "User Interface : Yeah .", + "Project Manager : Sure ? Yeah ?", + "User Interface : Yeah , I think possible . Because we can {disfmarker} We can uh mix uh several function in one button .", + "Project Manager : Yeah .", + "User Interface : So lets you {disfmarker} then you have less buttons .", + "Project Manager : Yeah , but do you think it will be easy to use ?", + "User Interface : But I'm not sure {disfmarker}", + "Project Manager : Because if you have many functions just for one button it would be quite difficult for the user to know .", + "Marketing : Yeah , remember the user is not happy to read the", + "Industrial Designer : The manuals .", + "Project Manager : Yeah ,", + "Marketing : manual .", + "Project Manager : I think the {disfmarker}", + "Marketing : It's {disfmarker}", + "User Interface : No you you can have a switch menu , so you can", + "Project Manager : Yeah , but it has to be intuitive .", + "User Interface : well for example {disfmarker} Yeah , I think so . Like for for example you can uh you can category the function i i into several classes . Then for um you can have a switch menu , so you put the switch menu to it it tend to this kind of this category of functions .", + "Project Manager : Yeah , okay . Okay ,", + "User Interface : Then you you put the switch button ,", + "Project Manager : but {disfmarker}", + "User Interface : then it switch to another category of functions . Yeah . For example , if you have remote control you you can rem you can control your T_V_ and also you can control your uh recorder .", + "Industrial Designer : With a {disfmarker}", + "User Interface : So there's a different functions , but i if you you {disfmarker} there's a button you can switch between control T_V_ and control your recorder . So we can has less buttons .", + "Project Manager : Yeah , but {disfmarker}" + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 16, + "turns": [ + 87, + 98 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "default materials", + "speaker": "Industrial Designer" + }, + "summary": "Industrial Designer said that they should use default materials, like simple plastics, to keep things simple, so it would be robust. After that, it said that they should focus on aesthetics, the design, and user interface, because the high-tech materials would be sky-high.", + "title": "Industrial Designer Opinion about Default Materials", + "relevant_turns": [ + 9 + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "high", + "topic": "default materials", + "speaker": "Industrial Designer" + }, + "summary": "Industrial Designer said that they should use default materials, like simple plastics, to keep the inner workings simple, so it would be robust. After that, it said that they should focus on aesthetics, the design, and the user interface because if they were going to use high-tech materials the price would be sky-high. After all, if they use high-tech materials, it would come back in every product, because it would be needed to design the remote just once, the son that was the idea of the Industrial Designer.", + "title": "Industrial Designer Opinion about Default Materials", + "relevant_turns": [ + 9 + ] + } + ], + "source": [ + "Project Manager : Uh maybe we can first um listen to your presentation ?", + "Marketing : We would have to look into that .", + "Project Manager : Uh {disfmarker} And then we {gap} have a little discussion about the requirements and uh design .", + "User Interface : Uh .", + "Industrial Designer : That's {gap} . Okay .", + "Marketing : Yeah .", + "Project Manager : {vocalsound}", + "Marketing : {vocalsound}", + "Project Manager : I think it's going to {disfmarker} Uh it's not too much . Okay . {vocalsound}", + "Industrial Designer : Okay I've got a presentation about the working design . Um first about how it works . It's really simple of course . Everybody knows how a remote works . The user presses a button . The remote determines what button it is , uses the infrared to send a signal to the T_V_ . The T_V_ switches to the frequency , or what function it is . So we've got um the the plate . It gots conductive disks for every button . When the user presses a button , a signal got sent , goes to the LED and transmits tranmi transmits its to the T_V_ . It's a very simple device , technically speaking . So this is a schematic overview . You've got the buttons . The power source . And uh when a button gets pressed , its goes to the chip . The chip uh controls the infrared bulb and perf perhaps a normal bulb . When you press a button you can actually see your pressed button . Well um I think we should use default materials , simple plastics . Keep the inner workings simple , so it's robust . Uh I think we should focus on aesthetics , the design and the user interface , because if you're going to use high-tech materials the price is going to go sky-high . And uh you only have to design a remote once , and if you use high-tech materials it come back in every product . So it's , in my idea , it's uh it's gonna be smart to invest in di in design and not in uh in the product itself . That's it .", + "Project Manager : Okay . Thank you . Okay .", + "Marketing : {vocalsound}" + ] + }, + { + "metadata": { + "dataset": "qmsum", + "split": "train", + "file_id": 79, + "turns": [ + 246, + 362 + ] + }, + "references": [ + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "command interface , user interface types", + "speaker": "User Interface" + }, + "summary": "User Interfaces thought they were going to go with the command interface, to make it simple. They could incorporate some of the graphical user points. They would have more money if they kept it simple. User Interface also said the remote control would be cheaper to design. They could learn from the mistakes of other complicated user interfaces.", + "title": "User Interface's Thoughts on the Command Interface Design", + "relevant_turns": [ + [ + 22, + 30 + ], + [ + 37, + 43 + ] + ] + }, + { + "control_attribute": { + "length": "long", + "extractiveness": "normal", + "specificity": "normal", + "topic": "command interface , user interface types", + "speaker": "User Interface" + }, + "summary": "User Interface spoke of having a little sound, instead of saying volume, they could have a little speaker. The remote control would be less complicated, controls would be more user-friendly and this made them decide on the command interface being the most useful for a remote. They had to keep in mind when designing their user-friendly remote that their functions, colours, and forms were not always helpful. All interfaces were different and it did not improve the use of the product, so they needed to come up with a more easy-to-understand user interface.", + "title": "User Interface's Thoughts on the Command Interface Design", + "relevant_turns": [ + [ + 22, + 30 + ], + [ + 37, + 43 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "buttons", + "speaker": "User Interface , Industrial Designer , Project Manager" + }, + "summary": "User Interface shared thoughts on the actual symbols that were on the buttons of the remote control, also mentioned the clatter of buttons consisted of different interfaces. Industrial Designer talked of the buttons with all the different colours for different choices and things. Project Manager asked if they should stick to the same colour for all the buttons to give it a simplistic look, and thought that the buttons would all light if one of them was touched. Industrial Designer said some parts could be transparent around the buttons. User Interface was thinking of covers on phones, when changed the little buttons that controlled stuff, they would be behind the rubber, so one could change buttons when changing the faces.", + "title": "Deciding on the Buttons Design", + "relevant_turns": [ + [ + 29, + 31 + ], + [ + 39, + 48 + ], + [ + 54, + 60 + ], + [ + 73, + 85 + ], + [ + 92, + 106 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "high", + "topic": "buttons", + "speaker": "User Interface , Industrial Designer , Project Manager" + }, + "summary": "User Interface said they did not have to decide on one colour, each face could have its own colour of buttons. Project Manager said one could feel the buttons if they were raised up. Industrial Designer said one could take off the hardcover when there were the buttons and then get to the circuit, but did not think it would matter that the buttons were bigger through the top casing.", + "title": "Deciding on the Buttons Design", + "relevant_turns": [ + [ + 29, + 31 + ], + [ + 39, + 48 + ], + [ + 54, + 60 + ], + [ + 73, + 85 + ], + [ + 92, + 106 + ] + ] + }, + { + "control_attribute": { + "length": "normal", + "extractiveness": "normal", + "specificity": "normal", + "topic": "design", + "speaker": "User Interface , Marketing" + }, + "summary": "User Interface spoke about what they had decided on the command interface regarding it being the most useful part of the remote. User Interface talked of it being a new technology and when designing the more user-friendly remote control they had to keep in mind that a lot of interfaces consisted of a clatter of buttons that could have aspects that were not useful. Marketing thought because of colour clashing they could go with the design plat thing.", + "title": "Deciding on the Design of the Remote Control", + "relevant_turns": [ + [ + 37, + 63 + ] + ] + }, + { + "control_attribute": { + "length": "short", + "extractiveness": "normal", + "specificity": "normal", + "topic": "design", + "speaker": "User Interface , Marketing" + }, + "summary": "User Interface said the remote control would be cheaper to design and they would have more money in the budget for them to target the design of the area interface. Marketing said that depending on the result of the design they may have had to stick to just black buttons.", + "title": "Deciding on the Design of the Remote Control", + "relevant_turns": [ + [ + 37, + 63 + ] + ] + } + ], + "source": [ + "Industrial Designer : But if we're having a simplified display anyway , w that , we probably won't have to focus so much on that .", + "Project Manager : Yeah , we'll be doing {disfmarker}", + "Industrial Designer : It'll be more the on the numbers and the volume .", + "User Interface : Yeah .", + "Project Manager : Yeah . It'd be more a command interface , and then {disfmarker}", + "Industrial Designer : I suppose we need to think of symbols for like the volume , display , and stuff like that .", + "User Interface : Yeah .", + "Project Manager : Yeah .", + "Marketing : So it's just draf graphical for the pointing aspect ?", + "Industrial Designer : I {disfmarker}", + "Marketing : The infrared is like , that's considered a {disfmarker}", + "Project Manager : Hmm ?", + "User Interface : No I think it's to do with the actual symbols that are on the , that's on the buttons of the remote control , and per", + "Marketing : Okay . So when it says pointing device that doesn't include {disfmarker}", + "Industrial Designer : For inp", + "User Interface : Well it could be a wee scroller thing , and something could come up on the screen .", + "Project Manager : Yeah . I think they're talking about L_C_D_ type things .", + "Industrial Designer : Mm .", + "Marketing : Okay .", + "User Interface : Yeah .", + "Marketing : Okay .", + "Project Manager : Yeah .", + "User Interface : But um I think we're gonna go with the command interface anyway ,", + "Project Manager : Yeah .", + "User Interface : to make it more simplistic . But the , we could incorporate some of the graphical user um points ,", + "Marketing : Mm-hmm .", + "User Interface : as in {disfmarker} just to make it m um nicer to look at maybe . {vocalsound}", + "Project Manager : What do you mean ?", + "User Interface : Like {vocalsound} I can't think of an example , but {disfmarker} Sort of like little pictures rather than {disfmarker}", + "Project Manager : Oh yeah , like how the buttons {disfmarker}", + "User Interface : Like a little sound . Instead of saying volume , like a little speaker or something .", + "Project Manager : Yeah , as a button though .", + "User Interface : Yeah , something y", + "Marketing : Mm .", + "Project Manager : So , it's a keyboard in the shape of it , right ?", + "User Interface : Yeah m perha yeah . Yeah . Maybe .", + "Project Manager : Okay . Yeah . I like that idea .", + "User Interface : Um , the co uh {disfmarker} we've decided that the command interface would be the most useful for a remote control . As it would be less complicated , and the controls would be more user-friendly . Um , the remote control would be cheaper to design , so that we'd have more money in the budget to , um , target the design area of the interface . You know , make it more trendy and original . We'll have more money if we keep it simple .", + "Project Manager : Yeah . I'm sure i like kinetic energy would probably dip into the budget . A bit more too , yeah .", + "Industrial Designer : Yeah . {vocalsound}", + "User Interface : Yeah . Seeing as it's quite a new technology . Um {disfmarker} {vocalsound} We , we also have to keep in mind when we're designing our , um , more user-friendly remote control , that a lot of interfaces consist of a clutter of buttons , that , um , that their functions , colours and forms aren't always helpful .", + "Industrial Designer : Yeah . That's true . That's in like the buttons with all the different like colours for different choices and things .", + "User Interface : Yeah .", + "Industrial Designer : It can be a bit , yeah , overwhelming . {vocalsound}", + "User Interface : Yeah . And that all interfaces are different . So , um , that doesn't improve the use of the produ product , so we need to come up with something that's easy to understand . And maybe learn from the mistakes of other interfaces that can be too complicated for people to use .", + "Project Manager : Mm-hmm .", + "Industrial Designer : Yep .", + "User Interface : Does anyone have any questions ?", + "Project Manager : Do you think that we should keep all the buttons to one same colour , just to keep it , give it a simplistic look .", + "User Interface : Mm .", + "Marketing : I think if we go with the um design plate thing , we'll have to . Just because of colour clashing ,", + "Project Manager : Yeah .", + "Marketing : and if we wanted to ,", + "Project Manager : Yeah .", + "Marketing : so and , and we might , I mean , depending on what comes out of the design , we might have to stick to just black buttons .", + "User Interface : But um {disfmarker}", + "Project Manager : But what about the lighting up effect ?", + "Marketing : You mean different colours for the lighting or {disfmarker}", + "Project Manager : Um , well , um , I thought we had um decided that we would {disfmarker} if you touched one of the buttons they'd all light up . And so if they were black , it wouldn't be possible for them to light up .", + "Marketing : Mm-hmm . Oh I see what you're saying .", + "Project Manager : If they were white they would glow , probably .", + "Marketing : Well y", + "Project Manager : If they were made out of rubber .", + "Marketing : Oh so you're picturing the light is coming from the back . I kinda pictured it as kind of coming from the sides and lighting it up frontwards .", + "Industrial Designer : Oh .", + "Project Manager : Oh .", + "Marketing : But , but I guess , you mean from the back .", + "Project Manager : Where would the light come from ?", + "Marketing : Okay .", + "Industrial Designer : I'd assume , like , an internal light , that comes through .", + "Marketing : Okay .", + "Project Manager : Yeah .", + "User Interface : Yeah .", + "Industrial Designer : So there would have to , have to be some parts maybe transparent around the buttons , or something .", + "Project Manager : Yeah ,", + "Marketing : Right .", + "Project Manager : and well rubber is a more translucent product too ,", + "Industrial Designer : Yeah , yeah .", + "Project Manager : so we have that taken care of .", + "Industrial Designer : It should be able to {disfmarker}", + "Marketing : Mm-hmm .", + "Industrial Designer : mm-hmm .", + "User Interface : In the phone that I was thinking of as well , when you change the um covers of it , the , the little buttons that actually , you know , that contro control stuff , are behind the rubber .", + "Industrial Designer : Li yeah .", + "User Interface : So you can change the buttons when you're changing the faces . Do you know what I mean ?", + "Marketing : {vocalsound} Oh .", + "Project Manager : Oh .", + "User Interface : 'Cause it's just the wee control ,", + "Marketing : Yeah . They , they insert over .", + "User Interface : yeah , thing that's behind it .", + "Marketing : Okay .", + "Project Manager : Mm .", + "User Interface : So {disfmarker} I mean , we don't have to decide on one colour . Each face could have its own colour of buttons maybe ?", + "Industrial Designer : Mm-hmm .", + "Project Manager : Well , if they're raised up buttons . So that you can feel them .", + "User Interface : Yeah .", + "Project Manager : We were talking about it being more um , a lot more tangible .", + "Marketing : T", + "Project Manager : Um , it might be more difficult to do . If they're , if they're sticking up .", + "User Interface : Yeah .", + "Project Manager : If it's flat then , like o like on a cellphone or a mobile phone , it's like all very flat , and you just have to sort of press down on these tiny little buttons , but {disfmarker}", + "User Interface : Yeah .", + "Project Manager : Yeah .", + "Industrial Designer : I think it would be possible . I don't think it would make that much difference . I mean , the uh the dimensions of it . 'Cause if it's just like constructed in the same way as like the front cover of a mobile phone . You can like take off the hard cover and then there's the like say the buttons . And then you get to the circuit . I don't think it would matter that the buttons were bigger through the , the top casing . I'm sure you could f work it out to fit in the casing , without causing too much difficulty .", + "Project Manager : Yeah . Okay .", + "Industrial Designer : I'm sure that'd be fine . {vocalsound}", + "User Interface : Yeah .", + "Project Manager : Alright . If it's do-able we can do .", + "User Interface : {vocalsound}", + "Project Manager : Yeah , sounds good to me .", + "Industrial Designer : {vocalsound}", + "User Interface : So that's everything , then ?", + "Industrial Designer : Okay .", + "Project Manager : Alright , thank you .", + "Marketing : Okay is that my turn then ?", + "Project Manager : That means you're up . Yeah .", + "User Interface : Yeah ." + ] + } +] \ No newline at end of file