Author Topic: PM6 catalog database design  (Read 450 times)

Offline syncrasy

  • Newcomer
  • *
  • Posts: 19
    • View Profile
PM6 catalog database design
« on: January 27, 2019, 05:49:54 AM »
Kirk, this question is obviously late in the game, but since you're still working on PM6 + catalog, I wanted to double check that the catalog's database will be a "proper" database.

I would be coming to the PM universe as a Media Pro refugee. Phase One wants us to migrate to their Capture One software for cataloguing purposes, but it turns out that Capture One uses an overly simplistic and unprofessional database design (e.g., keywords are concatenated rather than being kept in a separate metadata table; album membership is a property of the main image rather than each variant; etc.). These shortcomings make CO unusable as a DAM and are explained in more detail over on the Phase One forums:

"Media Pro refugees: What are our DAM demands?"

Of course I don't expect PM6's catalog to have every DAM feature from this list, but can you at least reassure us that PM's catalog will be based on a professional database design? (i.e., multiple tables for individual properties.)

Thanks.
« Last Edit: January 27, 2019, 07:04:18 AM by syncrasy »

Offline Kirk Baker

  • Senior Software Engineer
  • Camera Bits Staff
  • Superhero Member
  • *****
  • Posts: 19401
    • View Profile
    • Camera Bits, Inc.
Re: PM6 catalog database design
« Reply #1 on: January 27, 2019, 08:42:06 AM »
Of course I don't expect PM6's catalog to have every DAM feature from this list, but can you at least reassure us that PM's catalog will be based on a professional database design? (i.e., multiple tables for individual properties.)

Yes.  No such compromises have been made.

-Kirk