Okay. Good morning everybody. Welcome back to those of you that were already in the BEM and beaten and welcome from those of you that are just joining now. The next session is about the product roadmap, and that's where we will be discussing for the next hour.

Thank you for being here. I'm Christian Garza for those of you who know me and I'm working in the protein engineering team as products manager. Today, we will touch on six points. First we will have a brief look to

the past nine months to remind you of the video features that we have released. Then we'll take a quick look at the features. There is something about my audio settings. Okay. Okay, that's fine.

Then we will take a quick look at the features and products that you can expect to be released soon by our team. And I also want to show you the process that we have been using to get these features out into the pipeline. The product engineering team is a new team, and we have set up a

significant number of workflows and procedures to get picture outs in an efficient way. So I would like to give you a concise look into one of those processes. The results of that process are not only reflected in the products that we have released over the last nine months,

but there are other KPIs involved, and I will show you how we have been doing using that process based on those KPIs. One of the main objectives of this new process is the members involvement. This is a user driven process and

I will talk about the role that many of you have already been playing in the delivery of new features. And finally, we will allow you to keep driving us forward, and we will look at our backlog of the last year and let you voice your thoughts about what is important from that backlog, looking to the next year.

So that final part is where this session becomes a working session so we're going to make it work a little bit. So we hope you enjoy that part. As you see there's a very packed schedule. So I'm going to start moving on with the next part.

This presentation is called the product roadmap, and for that I mean the public roadmap that you can all see in the dataset homepage. Since 2019 this has been one of the main ways we publicly display the products and features that dataset is working on. And not only that, but the roadmap portal is one of the main places

in which stakeholders can provide suggestions to the dataset roadmap and to the product team. So, to gouge a little bit how familiar are all of you with the product roadmap and the public roadmap, I would like to just set a few questions.

We're going to ask you to go against Mentimeter and I'm pretty sure someone will be able to drop the link in the chat box. Thank you. Thank you so much. And if you go to that link, we will have a couple of questions just to start the day with this.

And the first question is, and again in question. And that is, am I aware of the features and products to be released, according to the 2021 roadmap for this year. Yeah, so you can go to a link. How much you agree or disagree with that statement.

And I'm going to give you a few minutes to actually enter the box. Yeah, thank you. I think the number codes at the top of the screen, Alicia, I think it's 65442079, but it should be included in the link, as Jess just mentioned.

Thank you, Lena.

I think we have half of the people present in the, in the call has already cast their vote. So if we are kind of in the middle. That's not that bad but not as good as we were expected so I'm going to move to the next question we have a second question related to this.

And this one is in the last year, in which ways, you personally, I mean, or your team have provide suggestions or request for search for functionality or features to data side. And I have put a series of options from which in the past we have received suggestions for features, but I would like to know I mean, what has been your experience.

Okay, we have a kind of mixed responses great I mean email is probably the main being is kind of the main medium that we have at the moment, to every website which is really good.

We are really interested in leading to that way. We also have some people that has not submitted any suggestions and that's also something for that this call is for so we would like to encourage you to do that but we can, we can talk about that in a minute.

I think I'm going to stop it there. We have probably enough data at the moment. And the last question is precisely about the data side homepage and the roadmap is like have you provided. How often have you provided BS via the site portal. Okay. And I think I think we have like a more

cute response on this one that is like, based on also the private response to the presence of the question is more skewed so was it, they have not been using the program up so this is good and bad but I mean like, hopefully we will.

Hopefully we will manage to stay in that direction. I will let another two seconds and then we'll go to the next slide. Okay. Okay. Okay, let's move to the next part, we have already understood a little bit of how are you be working but let's talk a little bit.

Now, while we have been the changes that have been doing the last couple of months. So, in the last nine months, there have been many changes and if you're listening data side. This year, you saw the release of schema 4.4, which is now implemented in many of the data side API's.

Together with that, we have, we are exposing more leaks than ever before in data side comments with features such as the quarter list, and the open access achievement but the users of data side comments have access to connection data and information

of the paragraph, like they didn't have before. And finally, during the last nine months, a significant emphasis emphasis has been on supporting internal business and processes, and as well as member communications therefore we center for a big time or attention improving or Salesforce integration.

And you can see the results of this improvements. Now you can manage many, a lot of your contact information for your organization directly into Fabrica, without needing to sign off or subscribe for additional many lists and anything like that.

I'm sure that you already know that, particularly the people that have been looking at the roadmap. So let's talk about what is coming ahead and what you will see in the near future, hopefully. One of the first things that you can expect in the future is of course, more functionality in data side comments,

specifically orchid claiming. All common users will be able to claim works as defined in comments directly into the orchid record. Additionally, users will be able to find repositories in the comments interface. This is something that was available previously in other public interfaces of data side, but now will be also in data side comments.

Accessing metadata in Schema 4.4 will also be made easier, as we will improve the support for Schema 4 .4 features. So there will be better ways to access the metadata in with the new features of Schema 4.4. And finally, we are also aimed to help repository administrations in three specific areas. The first one is improving preface accession workflows.

This is something that we have tried to improve over the last year and we have come up with a solution for that. There will be some improvements in the preface accession. Another area we want

to help administrators or administrators is a patch to stunning for inactive repositories. So this is having close. And we are want to help to provide solution in that direction. And the final one I know one that is everybody's really excited about that bulk URL updates for the device directly from fabric so you don't have to use an API to migrate your domain for your

device if you wish to. The plan, as you might see is ambitious but we feel confident that the process that we have can get us there in due time. So let's talk a little bit about that process. We call our approach.

The development journey. We work in a dual track workflow, in which half of the team works on validating new features with users, and the other half of the team works on building these features into software and services.

This work, of course, is interactive and aims to be user driven. And we have specific stages in which we involve the membership. Many of you have already already

know that we use the roadmap as correctly you have answered the questions today to collect insights. And that's the part that you see at the bottom left of this on this floor. And that's what you're presented by these three people over there. The part of the world that not many of you might be familiar with is the validation with a section

validation section with users which is something that I have marked with different orange dots here in the, in this diagram. Here in this section we buy a specific stakeholders, people that actually will use the features that we're building

that will help us to validate that the features that we're designing address, definitely and for sure member needs. And I want to talk a little bit further about in that section, and about that part, and how we have been doing so far there. So, this year so far, 37 stakeholders have contributed time to the validation of new products or features.

Some of them might be in this same call. This is not limited to members, I must say, it also includes stakeholders from other registration agencies and organizations such as, such as EDU or E3 data and others.

I must say that 37 stakeholders is not a meaningless figure here, and this, this is as many stakeholders as all the steering groups combined. So there's been an excellent effort from the community of stakeholders to help us to validate new features so you can be sure that everything that we have, we will be releasing over the next couple months, and in the future, it has, it has been checked to

address user needs. I must mention that many of these new features have come out from community suggestions and insights that we have captured, and as you saw in that workflow there is a section in that workflow in which we also collect insights and suggestions from members.

Collecting and taking action over these insights and suggestions is what makes us a views and revenue organization. And in the last nine months alone, the community has provided around 150 sites of suggestions to feature changes.

That is more in suggestions that we have collected in the previous two years combined. So as you can see, this way that we have been using with the product roadmap on the website, the product suggestion has been significantly successful. We have been doing very

well in the last nine months to actually understand what you really need to get addressed. For, and just once again I saw that not everybody is looking at the looks of the roadmap, but for those who are familiar with the way we collect suggestions and insights,

you can visit the roadmap page on our main website, and there you can submit a new suggestion or support existing features with the click of a button. There are also survey links that will tell you to a specific surveys that can help you to provide more detail about suggestions and support other suggestions.

Here I put an example of a feature that previously mentioned this, about the UI update, and you can see the elaborate links to which some people in our community have provided suggestions about the new features. You probably might be asking like who are these people who are taking time to send suggestions or support

existing features, and well, I can tell you that they come from all types of organizations and geographical locations. In the last nine months, we have captured insights from 38 organizations in total. I also want to mention that also these 38 organizations have provided 158 suggestions this year.

The data side staff has been also working towards identifying and collecting new insights through various channels. The team this year alone has collected an additional 63 insights from the community. Now, most of the organizations that send suggestions are present in the tab that you can see on the right.

So, if your name, the name of your organization or organization that works under your membership is on this list, we say thank you. Today, you are in the driving seat of the data side roadmap. The suggestions you send us are invaluable and they help us to keep the pulse in the community.

Today at the member meeting, we are covering three regions around the globe, and we can actually see how membership has been participated from these three different regions have been participating on driving the data side roadmap. This session covers today's session. Well, I mean, this one in particular, the one where we are

covers Europe, the Middle East, the Africa and Africa region, as well as the Asia Pacific region. To very contrast the regions in terms of not only geography, but how they contribute to the roadmap. The Europe, Middle East and African region is definitely a driving seat of the roadmap, as

they provide 56% of the sites provided by all members during the last nine months. On the other hand, a more modest contribution has come from the APAC region. And although humble, this contribution is also significant, as the membership from the same position

is only 2% of the total membership, so I don't want to get anybody discouraged. We all submit more information, but we would like to encourage you to keep participating and provide new ideas to the roadmap. This helps the product engineering team to validate new features, but also helps the whole data side to be aware of your needs.

And with that in mind, the rest of the session will be used to do exactly that, to listen to what would you like us to do in 2022. And we have prepared a small workshop exercise to get an idea of what's important for you in 2021.

And this is when this call becomes a working call with Ride Avengers and FYI. As I mentioned, we have collected 156 suggestions from you this year. Not all of them have made it to the 2021 roadmap. Some of them, we have just put them in a backlog because we have many things planned for 2021.

And as we approach the end of the year, we want to know what's relevant from that backlog to be carried over to 2022. And we would like to get your perspective on that. And that's what this exercise is about.

And to do that, we would like to make you bold for this roadmap that you think we should carry over to the 2022 roadmap. So these are the items that I have not made it to this year's roadmap, but they can make it to the next one if you think they are really important. We have put all those items into virtual sticky notes, and we have made a virtual whiteboard for this exercise.

We want to do three simple things. Visit the virtual board. Read all the items in that board in silence on your time.

That probably would take us around 10 minutes, and we will give you a few minutes to do that. And then vote for the things that you think we should be carried over to the 2022 backlog. As simple as that. Just go to the board, read, and vote. Those three steps.

I think someone will drop the link on the screen, but I think Sara has dropped the link in the chat box as well. And I'm going to leave a few minutes for everybody to go there to the board, and then I will give you further instructions.

And I think I can see how many of you are already there. I think we have seven people, but I will leave it a little more time. Thank you everybody for voting. I'm going to mention just the top most voted items. I think we have metadata quality tool. This is about improving the metadata.

The second most voted thing is linked to other profiles, like GitHub, to personal accounts. We also have bulk upload in Fabrica. That's another one highly voted, and I think there are a few with the same number of votes here. Merges that portal into Fabrica or Commons. Also, notifications about the resolution failures is another one that has many votes.

And a few other ones. We will be sharing the results of all this later. I think everybody can see my screen where the top voted things appear on the left hand side. Maybe Sara you can help me to confirm that.

Yes, we can see. Thank you. Thanks. Okay, so this is really useful information. It's going to help the product engineering team to prioritize for the year ahead.

And so I thank you for that. So let's continue with this, this session. Once again, I mean we are practically closing at the end of this session. So but once again I'm going to ask you to go to Mentimeter for the last part of this, there are three

final questions for you, and I'm going to once again bother Sara, sorry Sara did you just drop the link in the box. We have three final questions just to send you home before that. The link is the screen, but it's also down there. The chat box.

I think you saw the, you have over the last couple sessions, the last two we have been talking about the strategy, the roadmap, even the metadata schema in the previous session, and the plans we have, the backlog that we have. So you might already have opinions, not only on the things that we should be doing, but also on what we should not be doing.

So therefore the first question is, what are we doing product wise that you think we shouldn't be doing. We would like to get your opinion on that. So pop your answer in Mentimeter and help us figure out what you think what we shouldn't be doing product wise.

There is a little bit hard question but I'll let you there a bit about that one. I think nobody has cast their vote yet. Oh well we have one.

First I send the link to just the panelists. Okay, so sorry. All right. Okay, that's the link for everybody. Our apologies for that. So then we have a little bit more time to.

I think so far we only have two comments on this so I guess there are not many things we shouldn't be doing. Okay.

I don't know if I should leave another minute. I think we only have two people that have voted. Yeah. Okay, so it should be doing everything.

Okay. The second question is, is a bit different. Okay, we have a third vote. I think. And we would like to know about what you like the most about those we would like to know what you want.

Well you like the most about data side, and the second question therefore is what is the best selling feature of data side, it doesn't have to be like a product or a feature into our services, it could be a quality that we have. But you could say what's the best selling feature data side, and pop it up and pop it into the responses there.

If someone finds a, they got the restriction to to hard. Feel free to drop them in the chat box, that will be that will be. Okay, I think we have like many quality, many qualities here that we should

be that you found, like a good selling feature data side that's very useful. Thank you very much for that but I think that the one highlight here is that we are collaborative.

Excellent. I'm going to move them to the, to the last question. And it's not something. And the last question is actually not something for you to answer here. But it's something I want, something that you can answer, either on the roadmap website or on the Google form that was sharing the chat box before and days.

Well, we should be working on that we are not currently are planning to work on. And as I said, you don't have to answer that here. But you can go to a roadmap and there's a Google form as well that has been sharing there. And you can drop it at

any time over the last other than the next days, months, whenever you feel like if there is you know about something that they decide, you know that they would like us to work on but we are not, or not currently planning to, you can drop a message there. And we'll be really happy to, to look at that.

As I said, there is a roadmap website, when you can drop the suggestions, there is a Google form and there are links between both of them so I think it's automatically collected, nothing to worry about, about like we are missing anything. And I think with last that last question.

We reached the end of this session, so I thank you all for your time and your participation this has been incredibly useful I hope you have enjoyed it and had a good time. And I wish you an excellent rest of the member meeting, so thank you. Thank you everybody. Are there any questions, I guess we can close the session.