null
Hey Morgan,
Perfect- my preliminary testing is going well - take a look at the attached images. I can create jobs and upload files without any issues. I think I need to set the file type to something other than "other" it doesn't seem to create previews of these files right now. I'm just using the folder names as they are in EnterMedia currently and I am not sure what you want for tags precisely but that should be quite easy to adjust. Definitely need to meet to go over a few finer details - matching the job names and customers as you mentioned, stuff like that. But fundamentally, I don't see any roadblocks or issues with this at this point. I can search through the existing clients/locations etc also already.
Just let me know when you can meet and we can review.
Meeting confirmed for Thursday. I will do a bit more digging around, good chance we'll be ready to start a sync shortly after that
Ian, op-b instance ready in m42, there is also an update script in the private repo you can use.
Progress update: now setting mimetypes so previews look correct - am able to set tags also. Added pagination support for all of this also. Just adding some utility methods , Thursday we can talk for about how to match up properly, I am thnking we might need a really basic UI to let you choose if we're not certain which collection matches which location precisely. All looking well
Same link, you only need to login with a real zoom account (I had to create one)
JobTread Integration Progress – Sept 16, 2025
Core Additions
Independent API wrappers: Clean separation for listing accounts, locations, jobs, and tags.
Pagination support: Implemented loop with nextPage handling for accounts/locations/jobs.
MIME type handling: Correct type set during createUploadRequest, fixing file previews.
File tags support: Query and attach fileTags when creating files.
Testing & Fixes
Verified full upload + sync flow (createUploadRequest → createFile) with MIME + tag IDs.
Confirmed paged listing works consistently.
Fixed Velocity template issues with unescaped JSON.
UI
First pass of Sync UI:
Accounts → Locations → Jobs displayed in Bootstrap tables (replaced accordions).
Tags displayed with color-coded badges.
Layout optimized for clarity + client demo.
Structural / Deployment
Reorganized all integration code into a single folder for easier deployment and maintenance.
Introduced caching via CacheManager for accounts.
Refactored populateLocations / populateJobs into data-driven helpers using BaseData.
Next steps - Meet with OP on Thursday and align on how we match customers and name
Just an update - had some more communications with Morgan and team, Morgan is on holidays till next week but expect some CSV files and data from Ethan soon
From Friday: Ian, I got the sheet but the data was not merged at all. I'm working on getting a new sheet today if possible. Will keep you updated. - so hopefully we'll be back in action by next week if not later today.
Can we put a team meeting on the calendar to discuss what is remaining?
Sure, Morgan was out of office all week and is back Monday, we still need the spreadsheet from them, so nothing really has happened this week. But I'm happy to meet any time. (that message was info from an email to keep you in the loop, not something I was working on - we're waiting on that spreadsheet).
Some notes - just emailed: Hey guys,
Just reaching out quickly as it would be great to wrap up at least the code side of these this week even if the data itself still needs some cleanup - I just added the little bit of code needed to create the file tags on my side - I can confirm I can do that with no problem. I can also create accounts , really any data in the system, it's not hard. Did you want to have a quick meeting to review status?
Thanks! - hopefully we can wrap up a test run of everything this week!
I have the spreadsheet now, I am working on seeing how to match it up effectively with the current data in the OP instance
Worked with the spreadsheet, tested Job number matching and met with Morgan to discuss the data. Need to fix some search issues where identical job numbers are not matching - elastic analyzer issues most likely. Will try different stemmers tomorrow see if we can get a better match or just brute force it in memory. Not a big deal. Next steps - generate a report of job numbers that exist on OP entermedia that are not in the spreadsheet and then finalize some details on where to put some info in jobtread that exists in EnterMedia - copywrite info specifically and some tags. Will finish the "audit" report tomorrow so OP can review any discrepancies
Spreadsheet is added to entermedia-clients also along with other prep code.
Spreadsheet audit has been sent to Morgan et al - waiting now for guidance on how to proceed with the missing properties and some other small details on where certain metadata fields goes