![]() ![]() Let’s put a reverse proxy between Drupal and the Nuxeo Platform for that, it also fits well with the first requirement and will even give a caching solution if needed. However with that solution, the Drupal viewers will see direct links to content in the Nuxeo Platform, so authentication still has to be managed somehow. The Nuxeo Platform creates extensible picture conversions that can be linked and accessed directly ( ), it’s very convenient. A simple solution is to create a dedicated Drupal user in the Nuxeo Platform with restricted read access.Īnd then we want to display images. Having the same permissions for all users accessing content from the Nuxeo Platform through Drupal is therefore a requirement. ![]() You do not want the article authors to choose images that wouldn’t be accessible to the viewers. Two main constraints drive the choices for a solution here.įirst aspect: permissions and authentication have to be simple. There are many ways you can access the Nuxeo Platform from external systems. Screenshot of the Drupal page displaying a picture from the Nuxeo Platform Drupal does as well, therefore it should be simple to integrate the two. Now the next question is, how do you make that happen? The Nuxeo Platform is extensible and it has full APIs for, among other things, integration with outside systems. More importantly these assets will be stored in a central repository enabling you to share them between several external systems. Doesn’t a page look better when there is an image in the article? Of course, that image should live in the Nuxeo Platform because it provides advanced management capabilities, such as asset rights management, validation, lifecycle management, automated rendition, and syndication management for media files. Let’s imagine you use Drupal, a well known open-source CMS, to publish articles to a wide audience via the Web. It goes without saying that a central repository is more useful when you can use it with other systems. The more I think about it, the more I like the idea.In many projects, the Nuxeo Platform is used as a central repository especially for Digital Assets, such as pictures and other media assets. If price weren't an issue I'd grab that up and call it good, but price is an issue. Look, I've looked at QT9, it's a great program, but it's pricey for a one man band and there's a lot there I wouldn't need. I guess you folks call that "tracebility". Set up correctly I'd be able to look at every job I'd ever used a particular gage on, every machine I'd ever used to make a particular part and so on. I like narrative notes for example, Drupal would index these and make them searchable. ![]() I think it's something that could start out with just a little more functionality than a spreadsheet but grow into something much more useful over time. I'm also concerned about security, but I think that could be sorted out, maybe a random domain, maybe even a IP whitelist for access. Signatures are something I was wondering about, but if only a logged in user can make a change, then I think that might be able to be leveraged to create an acceptable "signature" In any case, is there any reason multiple versions of a document couldn't be saved in the database with only one being current? It would simple enough to set up a search that would only return the current version and another search that would return all versions, enabling you to display only current, but access when needed past versions. ![]() Maybe even add some functionality they don't have that would be valuable in my particular case.Īs Marc says, I believe that Drupal keeps a record of changes, by whom and when that with an add on could be added to the record. While I was watching some demos of some commercial QMS software, It occurred to me I might be able to duplicate some of that functionality with Drupal. I've had some minor experience with Drupal, sort tinkered around with it as a hobby. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |