You can handle video jobs in Storykit by moving or duplicating them – and when duplicating you can choose the option of "Duplicate to…" which sends a complete copy of the job including assets and storyboards to another client or campaign in the system – or to multiple at the same time, making some exciting workflows possible.
Campaign level access to the functions
If you have campaign access (and not client or agency access), you have access to the "Duplicate" function which allows you to duplicate a job in the same place as it currently resides.
Client level access to the functions
If you have client access (not agency access), you can use both the "Duplicate" and the "Move" functions. The "Duplicate" always duplicates the job to the same location and the "Move" function lets you move that duplicated job to the campaign of your choice.
Agency level access to the functions
If you have agency access, you can use both the "Duplicate" and the "Duplicate to…" functions – and the "Move" of course. The "Duplicate" always duplicates the job to the same location whereas the "Duplicate to…" lets you duplicate and also multi-duplicate the job to other clients within your agency. This means that if you can "send" a job to one or more than one client at the same time.
Working with the functions: Move
When moving a video job, everything associated with the job is moved. You can move a job to any campaign within the client it resides if you have client or agency access. If you have campaign access, this option will not be available.
Moving a job from the "inbox" level on client to a specific campaign (client and agency access levels):
Working with the functions: Duplicate and Duplicate to…
Whatever user level you are on in Storykit you can duplicate a video job – either to the same place or to duplicate it to other clients that you have access to with agency level access. This opens up a lot of productivity and possibilities.
When duplicating a video job everything apart from generated files – and some distribution items – are duplicated with it, which means that you create a "clean" copy with all assets and storyboards reserved.
There are two "Duplicate" options, "Duplicate" and "Duplicate to…," which we will go through below.
When using the "Duplicate to…" function, the job is duplicated to another client, and when using the "Duplicate" function it is duplicated in the same place.
A job that is created via the "Duplicate to…" function will end up in that client's root level as what we call an inbox job. From there it can be moved, renamed, deleted and so on.
Duplicating a job in the same location (all access levels):
Duplicating a job to multiple clients at the same time(agency access level):
One thing that makes communication around duplicated jobs a lot easier is to use Job Notes. These are messages that you as a user input about a job and that is accessible straight from the list of job. So you can communicate important information about that job without other users even having to open it.
Input Job Notes
You input the note in the Job Notes field on the Overview tab.
Read Job Notes
In any job list, the Job Note is now visible when hovering over the note icon.
Of course, you can also read the note in the Job Notes field on the Overview tab in the job itself.
Creating localized versions from a master version
One handy way of using the duplicate and move functions is when you are running a multi-language operation, not least when you have a multinational organization where local markets are responsible for distribution and to some extent messaging.
If you are set up in an agency fashion, that being with different markets and functions as clients under the agency entity, this means that you can reap all the benefits from the "Duplicate to…" function when working with video that needs to be translated and to some extent edited differently for different markets. This workflow is assuming that the person doing the duplicating has agency access.
- Create your "golden master."
You'll create your master version, the finished and approved storyboard, somewhere in the system – let's assume this would be in a client called "Corporate HQ."
- Make a "translation copy" of that storyboard
When you have a fully finished and approved version of your storyboard, duplicate that storyboard and name it – for instance – "For translation: Script Name" and perhaps rename the master version "Master Version: Script Name (do not remove)." These are just soft suggestions, but having a strict naming convention helps out a lot.
- Prepare your "translation copy" for work
In the "translation copy" you can now both add meta information in the shape of "Slide Notes" for each and every slide that you want to inform the local organization on, this could be things like telling them that they would need to find another image if possible or thoughts about intro title and so on. What you also can do at this stage is to make affordances for localization – for instance removing assets that you demand of the local markets to replace.
- Add other data you want to duplicate
This is also an excellent opportunity to add KITCORE data, which can come in handy and yield some crucial insight when you can start comparing these kinds of storytelling dimensions over multiple markets.
- Duplicate your job to all markets
Use the menu option "Duplicate to…" to invoke the list of clients that you can access, check the ones that are relevant and apply that. This job will now appear at the root level (inbox level) of the client, and your colleagues can move it from the root into whatever campaign they are using for this purpose. They now have their own version of this job and can get on with translation and localization right away.
Of course, this kind of workflow does not have to be exclusive for translation and localization – it could also be beneficial if you have local branches of your business and want to be able to make the title and the contact information a bit more local. This would be very relevant if you have some kind of central storytelling activity, but very locally anchored business outlets that need to communicate locally. That would be a great way of drastically increasing the output of quality storytelling at a local level.
Creating a library of templates
Another way you could – and perhaps should – use the duplicate jobs function is to build your own set of templates. This template will "just" be another job, but its usefulness comes from how you choose to prepare it. And that preparation could be a very planned and strategic process where you have identified a number of different storytelling measure that you need to take – but it could also be the reverse, when you have more or less stumbled on something that works and in a controlled way would like to repeat that over and over again.
Here's how we suggest you go about creating your own library of templates.
- Make a campaign and name it "Templates."
Create a campaign within your client or one of your clients, depending on your access level and what you want to use it for. Name it accordingly, once again – a good naming convention is always good to have.
- Create templates directly in that campaign
If you have a specific format or a certain kind of storytelling you want to apply, create that job and don't forget to add KITCORE data to make it drive even more data and insight over time. It's hard to say how much you want to "template" this – and that's the beauty of this way of working. A template can range from something very loosely held to a fully defined job where you more or less has to substitute an image and an update a couple of text fields.
- Create templates from already produced jobs
This is just a variation on a theme, but don't miss the opportunity to make more of what you've already created. So if you have a video job and one or more storyboards that have worked well for you in some sense, see if you can create a copy (with the "Duplicate" or "Duplicate to… "functions) and then move that into your Templates campaign.
- Make functioning templates from jobs by stripping out stuff.
To make your jobs into well-functioning and streamlined templates with just the right amount of content and information not to overwhelm anyone who uses it, you should strip out all unnecessary information and add as much structure as you can. So make sure that the KITCORE data aligns with the stories you want to tell with this template. And if you're working out of an already published job, make sure to strip out text and images that are not to be used from the storyboard. And as far as assets go – go into the asset browser and delete the non-used assets from there.
- …but also add stuff.
You should be thorough when creating a template. Make sure that you add slide notes to the slides that need it in the storyboard(s). But also consider if you need to add some template assets that can come in handy when working with the template. It could be different persons of interest, environmental shots or backgrounds or logos, and graphics that are often used. And since this template job will be the one you work from and duplicate out – all changes you do to it will be in play the next time you duplicate it.
Depending on whether you have agency access or client access, you may have to work with templates in two different ways. If you have agency access you can use the "Duplicate to…" function to send a copy of the template any client in your agency, and multiple at the same time. And then they can be handled with the Move function within the client. If you have client access, you first Duplicate the template job, and the use Move to move it to whatever campaign you want.