[Automatic captions by Autotekst using OpenAI Whisper V3. May contain recognition errors.]
Yes, hi!
My name is Espen Jones.
I work as a developer and team leader for Netschema.
So I'm going to talk a little bit about what we've been doing since the beginning, and a little bit about the plans for the future.
I've chosen to take this whole presentation in Netschema, mostly because I can, but also because I'm going to hold a lot of demos.
We have been working a lot with technical migrations.
It's not fun to talk about it, because it takes a long time, but it makes a lot of things possible in the long run.
We have been doing this for a while, and Dagfinn is aware of it.
We have achieved a lot in recent years due to the technical work we have done.
So we have achieved a lot of cool things.
At the same time, there are a lot of things that are happening in the background, but that will give wins in the long run.
I think we talked about it a lot last year, a new release for Tøste.
It's still something we're working on, but we're very close to the end of that adventure.
We're making major improvements in architecture and technical solutions.
We'll get back to what's happening around API, but I'll take that at the end.
So I thought I'd just run on with the demo, show some big and small things that have come to NetShema lately.
Let's see, I can start first.
I'll just show you some small things.
We have started to introduce some filters in my schema list.
There aren't that many here now, but that's something we'll be working on.
You can filter on an open-stinct status, and whether the schema is a test schema, an educated schema, or a dictation schema.
Here we are collecting data.
What is it useful for people to do here?
But here we have the opportunity to explore.
Let's see if we can find some good data.
That's fine.
A new thing that has come up is the graph of the answers for kids.
The graph is just when there has been a response to this scheme, then you can see how the data collection is going.
Here you can also adjust the spread you want to look at, or the grouping.
Set it down to weeks to see a more accurate result.
Maybe what we have worked the most with is the report.
This was one of the things we focused a lot on when we created a new admin in NetShema, was to get a report that was
to adapt and give a good overview of the data.
And this is very useful for those who do not necessarily need to do big machine computing on their dataset, but just need a short and simple overview of the data that has come in.
This makes it a good opportunity to share the data in a nice format easily.
So this was pretty much the same as the report we released last year.
What we have seen the need for is
People need to adjust what they want to see in the report and where they want to see it.
If you have free text fields with long lists, it is very annoying to read through and useless to print out or share.
You can individually remove all elements in the report.
Or you can add energy.
I don't want any text fields or text lists.
A report that is only based on data we can make graphs from, which is typically number input, multiple choice, matrices and so on.
But I can still go in and delete a radio button if I want to, or add a text question if I want to.
It is also possible to change the view in the report, line height and text size.
This will also appear when you download a PDF version of the report.
A very fresh feature we have found now is that there is a possibility to filter in the dataset directly in the report.
So I can for example say, was it a weight in kilograms?
If I write in a number here now, I choose greater than and a little lower.
Then all questions will be filtered on that question.
So people who delivered a answer with over 44 kg now, will get their answer filtered out from the whole report.
It shows here how many questions out of the total set are shown.
In this case, we have 520 of 726.
If I turn the filter on and off here, we can see how the dataset changes based on this filter.
You can add as many as you want.
They will then filter with both filters at the same time.
This filter also applies to where you load the PDF.
A feature we introduced a moment ago was the ability to connect schemas together.
I don't know how many of you are familiar with it, but we have a functionality where you can have a respondent in it, so that you can, in your dataset, connect answers based on extensions in different schemas.
So here I have an extension.
A question here.
Now I move on to the next diagram, and deliver my answer here.
The problem now is that this is in the net diagram, and also when you export it in two different datasets.
You can easily, with the help of automation in your TST project or on your machine, merge these two into a dataset.
But in the net diagram, you can't do that.
But what we have now introduced in the report,
Let's find the right schema.
Since this schema has a forwarding, you can choose to include the answer set in the same report.
So now I have my questions from schema number 1 and from schema number 2 in the same answer set.
Filters will also work across datasets, as long as they have a key that connects them together.
Something like this.
Other things, we have made some small changes in the format and schema.
It is now possible to randomize answer alternatives, so that they come in a random row.
I took an example here where this did not give any meaning at all, but it is still fun, and it will come out clearly if you try to look at it.
Right.
And this would be completely random.
It just makes a random generation in Netlizer every time a new respondent opens up the scheme.
So there is no normal distribution or anything like that, but with a large dataset, it would be a good natural distribution.
We have also added a functionality to be able to put in some pictures.
So if I now choose a single choice,
So we've got a new button down here, put in a picture.
Then we have a little selection of much-used question answers.
You can just right-click.
So if I choose quality here, what it contains, probably a tip, and just right-click.
Then the question is limited, and you can adjust it according to your own needs, as you wish.
We're starting to introduce this now, and we'll be working on it a lot more, and we'd like to have feedback on the usefulness value from you.
But right now it's at least on single-choice and multiple choice, so you have some options to choose from.
Another small thing is related to copying of schedules.
We have received a lot of feedback.
If you share your rights on a diagram and try to copy it, it happens that you want to have the same rights, the same group that wrote it, or if you make a copy and use it yourself, you will not have it.
It is difficult to understand what is happening now.
When you copy a diagram, whether it is a forwarding or something you have shared, you will get a prompt asking if you want to have these things or not.
So then you check for it if you want to have the extension with you, or remove it if you don't want to have it with you.
We've got a QR code for data collection.
You can download it right from InventSvarsiden.
It's a fully generated QR code that takes you
After a lot of talking to users, we have also added a functionality to be able to shape it as you want.
So you can choose everything you want to have colors.
You are free to do exactly what you want, but they will tell you if you do a combination that is not entirely accurate.
Here you get a poor contrast, and then it is most likely that it will not work, depending on the light and the environment you are in.
The codebook, a little change here, is that we can
A lot of people have filled out a large codebook in a large scheme and made a small mistake, and then it has been very difficult to change it.
Now we have a search and install function.
I can type in var, which is my prefix for all the variables here, and type in var instead.
It will install everything.
Same when you do auto-filling and codebook, so you can type in the prefix you want.
and then use it instead of what, when it fills out all the codes on Kvalir.
One last thing, which is a thing we have a very big problem with, which I have tried to solve for a long time, but which is heavy and difficult, and that is constraints.
Shit, now I have a diagram that has good constraints.
This is not happening.
Anyway, we'll try to get a more visualized overview of the readings you're doing.
This is one more thing we're trying to do.
Test a little, look at the feedback we get, and try to make extra adjustments there.
We're not quite there yet, but we feel like this could be the right way to go on a problem that has been heavy and difficult.
I think that was the new cool features I can show you.
I had one last thing I wanted to talk about.
That was... Help from you.
I mentioned that we are working with a new API regime.
If anyone here is using our API today, or feels that this is something they want to try,
So we're making a completely new API regime now, which is much better to use.
If you want to help us test it out, send an email to netschema at ujo.no.
Then we'll be very happy about it.
We're going to start testing now before summer, I think.
Is that right, Kai?
Yes.
We're making a netschema at usit.ujo.no.
We also have a user panel, where you can just log in for those who want to.
The URL is here, and there is also a QR code you can scan.
We need users to be willing to participate in user tests and to get in more detailed information than we just get on an e-mail with a request for a feature or a feedback message.
The more people we have here, who are users of the network, who want us to
go in that direction, it is of great help for us and for you.
Anyone have any questions?
Smart.
Very good.
Here.
So the concept was that here it is just a visualization of the routing you have set up.
But it's more to get an overview.
And you can also make simple changes.
You just have to say that you don't want this to be a dependency for a long time, that's the question.
I'm not doing this now, because this is an important topic.
So we look at the possibilities.
If this works well, we can implement the possibility of making larger changes in this format, such as asking questions, making complete changes to the question, and so on.
But this is where we are now.
And then we take it from there.
So those of you who can test it, please take a look at this and give us feedback on what works and what doesn't work for you.
Does it also work if you route people to other schemes?
I don't think so.
But that's a good idea, given the other things we've done between schemes, that we can do that.
It's complicated stuff, but it's structured data that we can get to quite a lot.
That's absolutely something we could think of.
You showed a lot of new things in the report, which I think is very fun.
It's not always that easy to do that kind of analysis and just find everything that was measured and had to be met physically.
For example, and just all e-mail addresses to them.
Things like that are sometimes difficult to get out.
Now it looked very simple.
Any thoughts on providing any answers within TSD?
Yes, we have started with... It was probably in place last time, I think.
But we have a data portal, both in TSD and EdeCloud.
If you have logged in, you will find it on nettskjema.tst.no and nettskjema.eduklad.no.
I will show it later.
Yes, we will get back to that.
This is a kind of collaboration to get the same visualization experience as in the nettskjema in tst.eduklad.
We do not have a specific plan for this report right now, but it is something we will try to achieve.
At least when you come a little further when the report is where we want it to be.
And to be able to access the data in the same functional way.
That was the right answer.
We work for that.
What you didn't mention was the transcription of dictation recordings.
I'm glad there was something about it in the transcription presentation.
But you have taken some of it.
We have recently done some work on that.
Connecting and integrating between the Dictaphone app and NetSchema.
I think this was announced last week.
Those who have used Dictaphone might think this looks new.
The idea is that instead of using the schema to connect it, we use a QR code.
You can scan it with your phone.
And it will automatically link you to the dictation map and set up the schedule in the right way.
And for those who have not used it, the result page looks like this.
You can then open the full transcription.
You can press play, the sound works here.
A very warm welcome, Jens Stoltenberg, NATO Secretary General.
I think I'm allowed to play these things.
Jens Stoltenberg, you have used the example of an EU meeting with Charles Law.
This is probably just a... But then you can also jump around in the recording, based on the text you see.
So it's very useful if you have a big recording and need a specific part.
So it's something like a search in Lithuania.
Yes, you're right.
Let's see if we look.
I'm sorry.
And you see that it is set up to translate into Norwegian, the transcription here in this case, and even Jens Stoltenberg's English becomes fluent Norwegian, in fact, with Whisper.
I remember checking the logs.
One dictaphone was delivered to NetSkjema in a minute, on average, all day long.
Enormous use of NetSkjema dictaphone, and it has taken time since we automatically started transcribing this to our own GPU servers in Fox.
More about that later today.
Any other questions about NetSkjema?
Leon?
The question is whether you can make your own paintings on such space alternatives.
I thought about that too.
No, Per, you can't do that.
It's something we're thinking about and want to do, but it's much more demanding than just standing for the paintings.
With the thought that if we make changes, we have to be able to handle it in a good way, and so on.
But that's something we're going to offer at one point, but not today and not next week.
That's it, and then later than that.
Longer, in two weeks.
Does it work in English?
What?
Mala, do you have Mala?
Mala in English and new Norwegian.
Awesome.
That's a lot, very good.
Applause to Mr. Jones.