Jump to content

Home movies - 'date added' metadata present, but 'year' missing


Recommended Posts

Posted (edited)

Hi,

 

I have a folder full of home videos, filmed with a camcorder.

In my library I see and play them all.

 

What is missing, though, is the 'year' metadata field.

If I click on any single video/ edit metadata, I see it has a 'Date added' field, which looks right.

It does NOT have a 'year' field, though.

 

That's very unpractical, because as a result I cannot use the filter function to show me only the videos of 2017 for example.

 

How can I have the 'year' field automatically populated using the info contained in the 'date added' field?

 

Thanks

Edited by Gui76
Posted (edited)

The "year" field should be below the "release date" when you scroll down in the edit metadata box.

 

5d88987114736_metadata.jpg

Edited by arche
Posted

Hi,

 

I see the fields when I scroll down, but they are blank

 

Example of the metadata extracted by emby, as shown in the "Edit metadata" window:

Date added: 12.06.2010, 19:46:03
Release date: dd.mm.yyyy
Year:
Posted

We don't currently do this but perhaps we should for home videos...

Posted

Yea it's not a bad idea, although sometimes these will have embedded metadata for the date it was taken.

Posted

with my home videos, 'Date added' is the date at which I recorded the movie. The one I care about.

Depending on how the videos were generated it might be different, indeed.

 

To make sure it works all the time, what about doing something like this

if (year is provided by the video) or (year is not null - has been set by the user for example) -> do not touch
else if ('release date' is provided by the video) -> extract the year from there, and set the year field accordingly
else if ('date added' is provided by the video) -> extract the year from there, and set the year field accordingly
Posted

Great!

 

How do you guys do to track those kind of future improvements? Want me to raise a feature request somewhere?

 

Regarding implementation details, I thought of maybe another way to solve such "problems", but in a more generic manner.

 

Today, if the "year" field is set, the user will be able to use a filter to say "year == 2017", which would already be awesome.

The even better way would be to modify the filter screen itself, and for fields which are dates, to have the possibility to specify a comparison operator as well.

So the user would be able to make a filter for "date created >= 01.01.2017"

Ideally, queries supporting simple wildcards like "date created == *.07.2017" or "*.*.2017" would also be supported, but that might be too complicated to implement, not sure.

This would obviously be a bigger change, but IMHO worth it as improved filter capabilities like that would allow users to make more powerful queries, in general.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...