Jump to content


Photo

Added date?


  • Please log in to reply
29 replies to this topic

#1 chjohans OFFLINE  

chjohans

    Advanced Member

  • Members
  • 361 posts
  • Local time: 06:44 AM

Posted 27 April 2014 - 09:45 AM

I'm using MCM to manage my metadata, and it writes the tag <Added> (example: <Added>20.06.13 16:38:48</Added) to movie.xml. But MB seems to disregard this and just consider the date/time the server picks up the file the "added" date. So whenever I delete and rebuild my .db files (happens a few times when "fine tuning" things) it will consider all files as just added.

 

Please, can you read and use the <Added> tag from movie.xml?

 

Also, it appears that after MB initially reads movie.xml it does not read it again, or at least it seems like it does not detect changes in that file. Is this by design, and if so why?

 

My MB3 server is configured not to download any metadata, that is the way I want it as I'm using MCM for all metadata management.



#2 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 156896 posts
  • Local time: 06:44 PM

Posted 27 April 2014 - 10:05 AM

we do both of those things, so more information is needed.

http://mediabrowser....port-a-problem/



#3 chjohans OFFLINE  

chjohans

    Advanced Member

  • Members
  • 361 posts
  • Local time: 06:44 AM

Posted 01 May 2014 - 06:29 PM

Ok let's take the issue with the <Added> tag from movie.xml not being read/used first, I'll get back to you on the other issue. But this is the most important to me as all my movies now has the wrong "added date". I just picked a random movie and as you can see from the attached screenshot "Date added" is 24/2/2014, that is certainly not what the movie.xml for the same movie says. See the attached zip file, as you can see the <Added> tag says "<Added>09.05.10 1:49:24</Added>"

 

Is this a bug, or am I missing something here?

 

How do I get MB3 to show the date in my "Added" tag from movie.xml as the "Added date" ?

 

MB3 does not update "Added date" if I do a "Refresh all" from the same metadata view. Doing a "Refresh all" did not seem to write anything in the server log either.

 

I'm running MB3 Version 3.0.5211.41935

Attached Files



#4 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 156896 posts
  • Local time: 06:44 PM

Posted 01 May 2014 - 08:58 PM

it is most likely not parsing that date format. we use

 

6/15/2008 

 

or 

 

6/15/2008 9:15:07 PM

 

Because that is the default format that is used by other applications that also manage these files.



#5 chjohans OFFLINE  

chjohans

    Advanced Member

  • Members
  • 361 posts
  • Local time: 06:44 AM

Posted 01 May 2014 - 07:12 PM

I thought you (maybe not you personally but MB3 devs) had agreed on these things with Pete over at MCM?

 

Is the MB community for some reason no longer interested in supporting MCM?

 

Could you please suggest a solution to this? Who should do something to get this fixed?



#6 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 156896 posts
  • Local time: 06:44 PM

Posted 01 May 2014 - 07:14 PM

are you sure you didn't change your date format in mcm? because i don't see any other mcm users mentioning this.



#7 chjohans OFFLINE  

chjohans

    Advanced Member

  • Members
  • 361 posts
  • Local time: 06:44 AM

Posted 01 May 2014 - 07:37 PM

I did not change any date format settings in MCM, and I'm pretty sure that option is not even there. I just went through all the MCM setting pages and I could not see any date settings anywhere.

 

A possible explanation could have been that MCM somehow writes the date based on my regional settings in Windows. That would explain the 24h time, but my date settiing uses / and not . in the date string. So that does not explain it either.

 

I've posted this in the MCM forum as well.

 

It seems to me that supporting MCM is not really a priority, and likewise it seems like it's not really a priority for MCM to support MB3.



#8 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 156896 posts
  • Local time: 06:44 PM

Posted 01 May 2014 - 07:54 PM

We've never said that. We want to support external tools that create metadata.

 

That being said, we do parse the date based on system locale settings. It is only written using the format i provided. I think if there were a widespread issue with this value you'd see it reflected here in the community by other mcm users.



#9 chjohans OFFLINE  

chjohans

    Advanced Member

  • Members
  • 361 posts
  • Local time: 06:44 AM

Posted 01 May 2014 - 07:12 PM

Could you please elaborate on that? You said you parse the date based on system locale settings, that is my regional settings in Windows? it is generally a a very bad idea to base parsing of time and date strings on regional settings, it should be based on a fixed format.

 

Maybe it's not a "widespread issue" because the majority is using US regional settings? Then what about the "minority" who does not?

 

This is my windows date and time format:
Short date: d/M/yyyy
Long date: dddd, d MMMM, yyyy
Short time: HH:mm
Long time: HH:mm:ss
First day of week: Monday

 

Could you please help me get to the bottom of this issue?



#10 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 156896 posts
  • Local time: 06:44 PM

Posted 01 May 2014 - 07:20 PM

actually this was tested with users in different regions. yea i agree it's a bad idea to save it that way. i originally had it saving in iso utc but that threw the values off when parsed by other programs. so i collected information and found that everyone was saving using system locale settings, so that's what i changed media browser to do. moving away from that would be a good thing but would require coordination from a lot of different people.



#11 chjohans OFFLINE  

chjohans

    Advanced Member

  • Members
  • 361 posts
  • Local time: 06:44 AM

Posted 01 May 2014 - 07:50 PM

Well it does not work for me. I am just writing metadata with MCM and expecting MB3 to read them, and it does not work. Or spesifically the <Added> tag is not being read correctly.

 

Are you saying there is nothing that can be done to fix this?



#12 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 156896 posts
  • Local time: 06:44 PM

Posted 01 May 2014 - 07:52 PM

No. You can start by collecting precise information on how mcm saves that value, since you've already posted a topic there.



#13 Tolerant OFFLINE  

Tolerant

    Advanced Member

  • Members
  • 387 posts
  • Local time: 06:44 PM

Posted 01 May 2014 - 08:02 PM

I have to wonder why your date has "." in it, mine doesn't and I am a MCM user.

 

Your tag: <Added>09.05.10 1:49:24</Added>

My Tag: <Added>5/1/2014 12:00:00 AM</Added>

 

See the difference? Maybe you can test this by clearing the metadata, with only ONE program running (ie. turn off MB3's server and fetch with MCM) then examine the metadata. Then do the same in reverse. Clear the metadata, turn off MCM and fetch with MB3 and examine the metadata.

 

Ok Chojans, I turned off MB3's real time monitoring and fetching from internet, saved. Went to MCM and removed metadata from a movie and then fetched Metadata and immediately opened the metadata file for editing, this is what I have for date:

<Added>5/1/2014 4:26:20 PM</Added>

 

That would lead me to think something is wrong on your end and it is not MCM's date format.


Edited by Tolerant, 01 May 2014 - 04:28 PM.


#14 Tolerant OFFLINE  

Tolerant

    Advanced Member

  • Members
  • 387 posts
  • Local time: 06:44 PM

Posted 01 May 2014 - 08:49 PM

From a user on the MCM forums, would this be an accurate assumption?

 

From the little testing I have done, it looks like MBS is populating their Date added field in the editor with the file creation date even though the movie.xml reflects something different.

But will write their information to the same field <Added> if you refresh or save in MBS.

Say I have a file Created 11/28/2012 11:53PM and I add it to MCM today I would get a <Added> field of 5/1/2014 1:24:56 PM but MBS doesn't appear to really be reading the <Added> field and shows file creation date in Their Date Added field in editor.  Which I have a feeling is actually their library.db info until you refresh or save than it goes into the movie.xml as the <Added> Field.  

This is my best guess from this test.


#15 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 156896 posts
  • Local time: 06:44 PM

Posted 01 May 2014 - 08:53 PM

Not really. When we first discover an item, it initially uses the date from the file, but then after that if the Added attribute exists then that value will be used instead. What's happening here in this case is the server is failing to parse the date format in his movie.xml file.



#16 Happy2Play OFFLINE  

Happy2Play

    Trial and Error

  • Moderators
  • 19145 posts
  • Local time: 03:44 PM
  • LocationWashington State

Posted 01 May 2014 - 07:42 PM

Here is an example of MBS not reading movie.xml <Added> field and reading the File Creation date instead.  I modified the creation date had MCM fetch metadata the placed movie in collection so MBS could see. 

 

Note the Date Added field is not the <Added> field from movie.xml

 

Spoiler

 

5362be28e16c3_Untitled.png


Edited by Happy2Play, 01 May 2014 - 05:44 PM.


#17 ebr ONLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 51972 posts
  • Local time: 06:44 PM

Posted 01 May 2014 - 07:58 PM

We seem to be talking in circles here.  We know that your Added tag is not getting read and we know why it isn't getting read - it is because it is in a format we don't understand.

 

What we need to know is how is it getting saved in that format?  Other MCM users don't have that format so there must be some setting somewhere that is causing the odd format.



#18 Happy2Play OFFLINE  

Happy2Play

    Trial and Error

  • Moderators
  • 19145 posts
  • Local time: 03:44 PM
  • LocationWashington State

Posted 01 May 2014 - 08:03 PM

But if I hit save or refresh MBS writes the exact same format to that field.  I guess the question still is why is MBS not reading the <Added> field at all.


Edited by Happy2Play, 01 May 2014 - 06:05 PM.


#19 ebr ONLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 51972 posts
  • Local time: 06:44 PM

Posted 01 May 2014 - 08:05 PM

But if I hit save or refresh MBS writes the exact same format to that field.

 

So that tells me it has something to do with the date/locale settings on the machine/browser.



#20 Happy2Play OFFLINE  

Happy2Play

    Trial and Error

  • Moderators
  • 19145 posts
  • Local time: 03:44 PM
  • LocationWashington State

Posted 01 May 2014 - 08:13 PM

I understand chjohans issue is slightly different with regional setting possibly, but as Luke states "if the Added attribute exists then that value will be used instead" but clearly this is not happening from the screenshot and data provided






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users