 All right. Well, it's 1045. I guess we can get started here So my name is Jim McKinnis I'm from activation technologies in Vancouver, Canada and my presentation today is al fresco Drupal's document Management solution just before I get started but who here is familiar with al fresco So quite a few people here from fresco. It's great So she seemed to have two title pages here, so I'll just move on to that So just a little bit about app innovation So app innovation. So as I said, we're out of Vancouver, Canada. We have offices in Atlanta and London We essentially our software company for hire doing pretty much a lot of the things that you see here on the side here in particular We focus of most of our developments on these three technologies here Drupal and al fresco Which I'll be talking about today and something that's called spark core spark core Just so you know, it's it's an HTML5 JavaScript MVC framework which is pretty mature actually came out of Apple and Essentially, these are kind of what we specialize in It's moving right along. So just to give a little bit of background on al fresco here So a fresco It's now considered to be the largest private pure play open-source software company in the world She wouldn't have put the slide just kind of got cut off here so it's People are familiar with al fresco. It's essentially document repository system they are actually out of Atlanta as well and and they and They're kind of like I guess if you could About a SharePoint if you want with Microsoft SharePoint. It's kind of a replacement for that It's also kind of a replacement for what people used to do or guess still do with just a file server You know just putting you know if you have a file server with you know all your documents on a file server Which people used to do a lot and still do it's kind of like kind of like that concept on steroids So here we go see how three million downloads so I won't go through all the marketing here on on the al fresco slide So some of the key features of al fresco So as I said it provides a content management document repository provides free text indexing queries on that repository using solar so you drop a document into the repository it'll do a free index it and using solar and you can search it using solar using basically keywords keyword searching on those documents and then it also provides is a very Nice piece of al fresco is that it provides a number of ways that you can actually access this data so for sure you can log into a web a website and Upload it that way through the web, but you can also Interact with this document repository using either FTP iMap SIFS The SIFS has an SMB kind of mounting them as a drive CMOS which I'll get into quite a bit more later and the few other ways of actually getting at this data these document repositories It has a very strong workflow mechanism so for essentially managing documents and actually the workflow of a document approvals those kind of things how documents get approved and It also provides very very good strong versioning of your documents as well So straight out of the box it provides a lot of these great features Unlike Drupal, which doesn't really do a lot for you out of the box out of the box Al fresco does quite a bit for you out of the box So just gonna step back and just give a brief quick overview of al fresco here from the video A video that I have whoops, that was that Not appearing on the screen Okay, so here I'm just logging into a fresco share so you see once you log in you're presented with your dashboard Kind of tells you kind of where you are in the world right now Now the most interesting thing here is really the repository, so I'm gonna go up there and click on that repository button up there And as you see we presented with a directory structure Much like what you'd expect from a directory structure So we're just going to dig into a user area here Into a gym folder And you can see that these are just documents that have been stored on the a fresco system So beginning got beginners guide to Drupal So I didn't show example here, but this is just uploaded straight into the system via the UI previously So it gives you a preview of the document you can preview a document any kind of document really this is a PDF Doesn't matter if it's a word document or anything like that Download download it right there and then you can also view it in the browser if you want. I'm sorry. What's that? Yeah, of course Okay, so what I'm also gonna get into here is just show a little quickly a workflow So you log it so you click on the workflow and you've got a number of choices of the different types of workflows that you can do here I'm just going to do the second one here Which is the the group one and once that's selected it puts you into the screen that allows you to essentially set up your workflow and and add the groups that you want to actually approve this and if we come down I'll have to select This I need here a group a Group of approvers. It's coming soon. Okay, and we move it over All right, and now I would have received an email for that telling me that there's a new document It's being uploaded to a fresco and a new workflow is being created on it and that I need to go and Do my approvals on that document So now I'll go back to my dashboard And you see down here on my tasks. I now have My new tasks that I need to Review this document. That's just being uploaded. So I go in there and I can Take a look at it and you can see here that here's the metadata That's associated with this and if you come down further as I come down you can see what the moment There's only one version But if I would upload another version or make edits I would get a list of versions here that I could go back to if I need to leave That's almost the end of our video on the fresco In fact, I believe it is Okay back to where I was sorry about that. Okay All right, so just a little bit more on kind of what a fresco what it's built on so a fresco is As I said, it's open-source system That's built on Java using spring so spring if you're if you're not familiar with that spring is a it's an MVC Java framework And then a hybrid Nate is kind of an ORM for Java It's kind of like that and then it's really I mean a fresco is really kind of taking together almost the best of Kind of what's out there and in open-source Java and really pulling it together and a solar another fabulous open-source Java project there Jbpm Jbpm is came out of J boss. It's that's what takes care of the workflows. It's a business project management as it's What that stands for open office believe it or not is actually back there are running away Open office is is used when you when earlier when we saw the preview of the image That's what open office is being used for and it's It can convert Anything basically to a PDF is to say what it does and and so you can view it as a PDF And then there's also many other open source Systems that have been integrated into it that give you as the IMAP in this and the CFs and the FTP and a whole bunch of other nice things So here's a kind of a product architecture slide formal fresco So this kind of shows you kind of the whole kind of all the layers that exist here at the bottom You can see that we have LDAP so it does support LDAP out of the box Obviously uses the file system database typically it uses My sequel but you can use whichever database you wish the file system though I mean as far as the database itself though It none of the documents are stored in the database database is really just for metadata and kind of associated data The file system is really what they they use for actually that the real repository where the documents are actually stored and then We have the other the layer in between and really the most interesting thing I'm going to talk about here as it relates to Drupal and I won't get stay too much on this slide I'll just move forward Okay, so now bring this all together. So that's all fresco, right? Very quick introduction to a fresco. Now, how do we how do we bring what we just saw there that document repository? We kind of workflow Very very solid document repository very solid workflow. How do we integrate that in with Drupal now Drupal? I mean no matter what what great things it is good at and it's many great things that it's good at It's not particularly good with document repositories very large document repositories in particular Not that great with hierarchical data like file structure type data Not that solid on workflows in compared to Al fresco however Where well fresco seriously breaks down and what Drupal really shines is Just just in the ability to really kind of build the kind of user race the kind of website that you really want So the thing about a fresco is is that it's got this great back-end repository It's got that user interface that I showed you but it's not very flexible in the user interface It's really not something that you would really want to use As you know a front-end, you know public-facing kind of website It's more of an intranet type of tool it's it's It's not really designed for much in the way of UI kind of customization However Drupal obviously everybody knows that you know pretty much anything you can dream up You can probably pretty much do a Drupal on that end Now bringing it all together. I'm going to talk about two two ways that we can actually bring all of these great features of Al fresco into Drupal and vice versa bring all of those great features of Drupal in with Al fresco and the two ways that I'm going to discuss about how that's done is one called see miss Which is a public standard and the other one is called canopy Which is something that us at of we at Al fresco have developed and are currently working on and and expect to Open source in the very near future Okay, so see miss. So see miss what it stands for is the content management interoperability service and Essentially it provides a standard mechanism for connecting document management repositories basically content management systems and Specifically focused on repositories and this is a standard That's being worked on by a number of organizations out there Obviously a fresco are big players on it as well as be a SharePoint supports it as well Life array, I believe might even support it But there's a number of number of institutions and organizations out there that are really pushing on the standard So it's how it works. It's essentially it's a it's a service It's like a web service using soap or atom restful services It buys full crud and search capabilities And is available out of the box in al fresco And is available in Drupal client side using the CMOS module. So there's a standard module out there for doing CMOS and As I said, it's it's it's it simply provides the the client-side interface to it Does not provide the server interface Okay, so very simple diagram here, but really kind of mostly to kind of illustrate a later diagram So the thing about how how this all works is that with CMOS and integrated with al fresco on The al fresco side everything more or less lives on the al fresco side as far as all the documents everything just lives there and When you when you interact with it using CMOS, you really just using Drupal as more or less as a pass-through, right? So documents just remain in al fresco if you have a PDF file It just stays there and you have a link more or less on the Drupal side to it And if you want to download it, it just won't as Grab it from al fresco pulls it through Drupal and just sends it back to your browser So it's really just a pass-through is what's going on right there Now some of the some of the services that CMOS provides are well fold the navigation Folder document create and delete upload and download of documents search So versioning check out check-in and metadata. So now obviously My particular discussion here is about al fresco, but in general. This is what CMOS provides So if you want to support CMOS, you have to more or less provide these these services Okay, so the Drupal CMOS module it's available from the site. It's also you can probably find it easy through Google It's available for Drupal 6 and 7 although Drupal 7 is still a development release and Actually in general I Would say that the kind of the whole thing is pretty much a development release I mean it's really more of a proof of concept at this point the CMOS module and It's not really a fully realized product at this point And I'll show you a quick demo of that shortly here and explain for some of the reasons why that is Okay, so I have got multiple Methods of doing this today Alright So as you can see here, this is Drupal 6 at this point and this one has the actual CMOS module installed So what we're going to do is we're going to take a look at something kind of the nicest feature I would is this browser so as you see that this is the same directory structure that we had when we were in Alfresco and I'm going to go through the documents there. That's my gym folder and Then you see there. There's our beginners guide to Drupal that document that we saw so this is just coming straight out of that of fresco and Displaying it for us and there's the list of kind of metadata associated with it if I come back So yeah, so I didn't click on it But if I were to click on it, it would just download the same way it did when I was in fresco So now I'm going to show you kind of the cck cck module that it provides So we can create document content types that actually have a supported document type of or a field type of an afresco document And this is all part of the part of the the CMOS module And as you can see here that this field here is a CMOS attachment And so what it's going to do is that it's going to store in a node And a custom node, which is what we've got right here A description as well as a link This is not really what the what the internal link looks like that it's storing But it is going to maintain a link to that document within the node So it's essentially a way of actually having a node That's associated with a document and that document is actually stored in alfresco. It's not actually stored in Drupal Yeah, so that's the end of that Okay, so as I was talking about earlier the the CMOS modules as I say is is really more of a proof of concept It's it's missing quite a few things So one of the major things that it's missing has got no dynamic authentication So the way it is right now is pretty much hard-coded in terms of If you what the what the user is so within the module itself you have to actually specify a username and password But it's going to use so admin admin say all right, which is fine and all But that's not really the way you want to work The way you really want to work is if you log into a fresco to Drupal as Jim You want it to log into a fresco as Jim. All right, so that's a major piece. That's missing there Another major thing is that that so you saw the cck field. It's it's interesting But what I didn't show you there is is really how clumsy it is on the authoring side It doesn't actually provide you with a very good interface to try to find out what we'll find those documents and actually Locate them and actually create that link you kind of have to actually know the actual Earl and paste it in Which is not very nice So that's something that's missing there and it's kind of an oversight, but it's really just a proof of concept I believe the whole module is at this point Currently only supports HTTP basic authentication. In fact, this is this is true of both Drupal and Alfresco So when you're on when you're doing the rest service Or you're doing the authentication rather when over the service it it only does basic authentication can't do OAuth can't do anything more sophisticated than that unless you you want to write custom code to allow to do that and It's just kind of on the good side is that we are actively working on trying to resolve a lot of these shortcomings of this module and Expect to contribute that back to the community In hopefully a short short amount of time here Okay, so on to canopy so that was see miss. So just to kind of recap on see miss So see miss as I say everything stored in Alfresco stays in Alfresco It's kind of a pass-through mechanism coming through through Drupal You know you have to create custom node types content types to to interact with it in you know in kind of an interesting way Now what we've done in the app no ration is that we've created this this new new New way of integrating these two platforms that we're calling canopy and the way it works There's the content is actually gets a replicated To between the two systems so for example if you're on the fresco side You can actually create a document sink it to Push a sync button that we've added to a fresco and it will actually sink it to Drupal, but sink it to Drupal into an actual content type like like an existing content type like an article say or Or a blog post or something like that something that's meaningful to Drupal a lot more meaningful than than what see miss is providing And then it also provides it also allows you to do Manage the workflow for documents on the a fresco side and and publish them to the front side Now here's here's that they're kind of the reverse diagram of what I had earlier now What you're seeing here is is that on the a fresco side we have we've created a custom UI This is kind of the modifications that we've done we've created a custom plug-in for the UI that allows you to actually sync Documents to formal fresco to Drupal and it not only allows you to sync to Drupal allows you to string to multiple Drupal sites So you can actually choose, you know site a site B site see whatever Depending on where it is that you actually want this document to get posted to And it actually comes from like just normal, you know, I'll fresco content types And then same thing on the receive side here We've had we created what's called and so in fresco the way that you can actually kind of expand The system is using what's called web scripts now web scripts There's a lot of ways you can expand the system you can use Java if you're familiar with spring and hibernate You can you can go that route, but that can be you know somewhat gnarly at times But they have this other system called web scripts and web scripts is Java script provides Java script to actually doing creating your own Rest API and things like that you can do that in Java script You can also use web scripts to actually expand the user interface as well And then on the Drupal side we have essentially two custom modules More or less ascend and receive so the receive which is probably Probably the most interesting kind of component of all of this because this is the one that takes Information from a fresco and actually puts it into recognizable content types in Drupal Like I was talking about with blog post or articles or things like that and then the custom send Kind of obviously it makes sense It's the reverse of that takes takes common normal Drupal content types and actually syncs them into Al fresco recognizable content types Okay, so canopy technology. Well, I guess I kind of talked about that there But yeah, so on the Drupal side it's custom module provide JSON rest interface So this is completely on JSON JSON rest No Adam no XML and all that stuff And I'll fresco side the same thing custom JSON on that side For the UI sync and then web scripts using the JavaScript Okay, so now I'm gonna do another quick video of that Okay, so here we go so so essentially so sorry that went up kind of quick So that was essentially kind of creating we're creating an article here on the Drupal side So we're doing the title pulling in an author and As you can see it's just a standard Drupal 6 in this case Create article we'll grab the content here and Create a file name for it and we're gonna upload an image to it And we're gonna ask to not be published because we want to actually start a workflow on it Let me we've saved it Okay, so we've saved it here on the Drupal side and it looks as you'd expect it to look And then we're gonna flip over to Your fresco side Okay, so we'll log into a fresco here And for our canopy piece We've created it so that you guys should do get a preview of your website your Drupal website right in al fresco And you can see that right there now the most important thing is we want to go to the repository So now the way this works on the fresco side is how we've done it is that Depending on where for where you are at a folder structure that kind of defines what content types It's gonna it's gonna interact with so in this direction essentially what happened is that it created a folder that was the date of when that was published and So there it is there, that's just a text the plain text of it and the images are there I'm sure we actually show the images, but what we are going to do is we're going to start a workflow on that So now that hasn't been published on the Drupal side But what we've done is we've uploaded it created on the Drupal side It's been unpublished and it's gone into canopy here into a fresco here And now we're going to start a workflow on it on that side So we're gonna ask one person to kind of review that document there. Sorry for me turning my head here I'm just not getting it on my screen here So we've started a workflow there and then actually that's the end of that part of it But now I'll go into the next component All right, right. So now what we're going to do here is we're going to do the reverse, right? So after the workflow, we're actually going to create a document here on on the on the a fresco side So we just uploaded some HTML an image Into a fresco here and we can review it And we're gonna add some metadata to it as well So that's one of the things that also gets replicated between the two systems is the metadata as well Now this one we are going to publish it Yeah, so now you see up here where that where the mouse is so there's a button there called publish to live now That's essentially the the UI customization that we've made is adding that so now if we come back here We do a refresh you'll see that that'll be there war makes 10 years is now the top article there And that just got synced from from all a fresco So you can see that there's a there's a lot of different kind of uses that you can make of this It's certainly workflow. I mean managing workflows a big thing I mean certainly another thing about that as well is as we all know I mean Drupal all the great things that you know, you can do with Drupal. It's The back end the back and admin is certainly something that's you know, you know There's some lacking there on the back and admin so obviously this this allows you to use all fresco I shouldn't stop that To actually do the back end admin for you that allows you to do the back end admin using a fresco and Obviously manage your workflows manage all your content manage, you know, whoever needs to you know Deal with or review all this documents all these all of these things and and then once it's already you push it out to a website And as I said, you can push it out to numerous websites at the same time or you can say I want to I want this piece of content going to site a I want this other piece of content going to be see Etc etc Okay, I want to stop that video All right, so just a flight on the future of canopy. So at the moment We expect to open source canopy by the end of the year now There's a few things that we would like to do before we do that One is we're right at the moment. We don't support fully support Drupal 7. So that's a big thing that we want to try and do Error handling isn't that great at the moment. That's something that we absolutely need to show up quite a bit on that front The configuration so as I was talking about, you know, the way that you map Content types between the two systems is pretty clunky at this time It's you have to kind of do some pretty gnarly XML and maybe even some code Well, not maybe you actually do have to do some some code changes For that we'd rather have a user interface for that and that is something that we will be working on is is building a user interface Just like Seamus actually we have the same problem with Seamus in the terms of the user account integration Again, we are kind of like, you know admin admin kind of stuff going on but we obviously don't want that going on we want to be the case that if you log in as You know Jim on one side that you're Jim on the other side, right? We definitely want to do that and then a major piece that we want to try and do is is integrate the workflow So integrate the workflow of al fresco into Drupal so that you can provide almost like the way almost similar to the way the Seamus works the way it integrates the repository. We want to try and integrate that workflow into Drupal a Lot of the clients that we talked to who are interested in this. I mean, that's a really a big thing for them I mean one of the problems with al fresco as I said earlier that it's it's not that easy to customize But not only that I mean a lot of people don't really like using the interface They they prefer they prefer what what can be done in Drupal in terms of the interface the flexibility that they get So not just are they they do not like the How it works how it looks they they just don't like using it very often okay, so one The other nice thing about al fresco about kind of using al fresco is that out of the box? It does give you obviously the repository, but also gives you solar so solar is kind of built into it and The I think there was a presentation here earlier on solar People are familiar with what solar is. I'll just give a brief description of that. So solar is Essentially, you know your own personal Google is really what it is more or less it's essentially a Free text Lucene indexer that allows that essentially you just put in a document And it'll index that document for you keyword index it and then provide you with keyword searching on those documents And you can't actually kind of build your own Google with it if you if you're so inclined But it's a really great tool really great tool to really just expand the searching abilities of Drupal itself now Yeah, that's what I just mentioned Yeah, so this essentially so the one way that you can actually make use of solar in From Drupal is actually through that CMOS module. So the CMOS module has a search mechanism and That search mechanism on the fresco side is done through solar is what's going on So you could actually access it all completely 100% through through CMOS or you can actually just access the solar database It's or the so yeah the solar database straight from a fresco. Sorry Drupal using the Drupal solar module So as if it was just a standalone solar a nice thing about that is that can give you like a nice federated kind of search So whereby you actually can search the solar database so you can actually index stuff That's just exclusively lives on your Drupal site into the solar you also get Everything that's on the fresco in the solar right but then on the Drupal side You can do a search against that solar and you're searching you're basically doing a federated search You're searching everything right you're searching yourself you're searching this and you potentially you could be searching other things as well Very nice system solar on its own is absolutely fantastic But you know integrated with a fresco. It's a really nice combination And it's actually just recently that they that a fresco chose to use solar Version 4.0 is the latest version of solar And just to actually speak a little bit about kind of how a fresco works in terms of their They're kind of software licensing and things like that on how they make money It's a little bit different than how Drupal works. So the way Drupal works is Is essentially there's one code base for Drupal, right? That's it, you know, there's no free version There's no and then a paid version, right? It's not like red hat, right? It's not like you know Sentos and red hat, right? It's just Drupal. There's just one version, you know six seven eight whatever right now in a career makes money through the cloud services, right to make money through Professional services and things like that, but they don't really make money From selling a commercial version of Drupal, right? That doesn't exist So but the way that a fresco works is that way it's more like the sentos red hat model So whereby there's the community version and then there's the enterprise version is how it works So the community version is you know, the open source free version And it's it's it's kind of the same model as sentos red hat in the sense that it's considered to be kind of the bleeding edge Part of it. You don't get a lot of bug fixes going on. You don't get things like that But it's free, right? It's but it's I mean compared with enterprise it pretty much does everything that enterprise does Now the enterprise version obviously you get you get, you know the support from a fresco you get Bug fixes you get the latest Kind of vetted technology the thing about the community version is is that it is community It's like, you know, the community can contribute to it And you know, that's that's a great and all but it doesn't get it doesn't necessarily mean that you know You're gonna get quality code and you don't doesn't necessarily mean that it's gonna be vetted and reviewed very well Okay, so that's actually my last slide there and so the final one here and just Added note there that my HR person wanted to mention that we are hiring And if you do want to check out our site observation comms last jobs. We are looking to hire people in Vancouver, Atlanta and London and even remotely we're looking for top quality of fresco people and top quality Drupal people Just check out our website. There it is right there So that's it So I guess we can move on to questions Do we have any questions? Yeah, right here Yes, yes, it would It replicates them. Yeah, that's correct. It absolutely does. Yeah. Now in the case of a PDF typically How how we would do it if you if you're integrating something into an article or blog It's better to upload you can upload like an HTML file into a fresco And that can be your content in a fresco and that really simplifies obviously the sink because you know HTML is pretty easy to sit to sink PDF. I mean we do do conversion there But you know, you know how good that can be right, you know converting PDFs to to HTML So for the most part that would get that would get replicated that PDF file would get replicated completely on the Drupal site. Yeah Yeah Absolutely not. No. No effect. We've what we've usually done is For that scenario is that very often we've done sites where we've hosted Drupal on the cloud on the Acura cloud And then because the Acura cloud is is Amazon, right? It's built on Amazon in particular the the West Virginia No, Virginia Data center is where Amazon's Virginia data centers where they have it So we typically what we do is we we do the cloud and then we get something at Amazon at that same data center All right, and then we integrate them that way I mean that that's great because we're in the same data center. It doesn't have to be that way though I mean it could be somewhere other somewhere else in the world. It doesn't matter at all. Yeah Yep We usually recommend we usually do recommend the enterprise version Mainly because of support. I mean one of the things that I mean a fresh we are You know what's awful for hire our company's a software for hire company, right? We build software We don't really support software, right? I mean, that's one of the nice things about about working with Acura is that they do a lot of that support for us, right? They have that thing that that going on that's the same thing with all fresco, right? That's what you get when you when you do the enterprise, right? It's nice for us because you know after that You know we're somewhat hands-off obviously we would you know if there's some crisis obviously we deal with it But but we are more or less hands-off at that point Just the way we are with Acura when we when we finish a project that we host there Yeah, right here Correct. Yes, absolutely. I mean we are we are working on actually integrating those workflows into Drupal So that you could actually just complete I mean that's and that's a that's a huge request that we get from from from clients as well Is that you know, there'll be a lot of clients that they're interested in this in this type of integration? But we get a lot of clients that say I don't even want to see of fresco, right? We get a lot of that as well So so yes, that is definitely something that that we want to do and we are actually actively working on right now Yeah, right here Yeah, the main reason to replicate is is so I mean we didn't really like on the Drupal side For example, we didn't want to do anything funky like say with the data model or anything like that We just wanted we just wanted Drupal to have Assets or nodes that it can put that it understands, right? That was really the reason why we decided to replicate So that that way You know, you don't have to you don't have to do anything just works, right? It's just a it's just a small portion You know of the application the small module that can take the data and just Insert it into a node type well understood node type and then everything in Drupal that's associated Supposed to work with that node type just works the way it is out of the box no brainer So that's really the main reason why we decided to do that and in the way the data is stored in a fresco It's not in a format that Drupal that Drupal could understand So that's obviously another reason why we do it did it as well Yeah, yeah Yeah, well it depends it all depends I mean like I mean I might have made it seem from this presentation that you know Seamus sucks, but I didn't that's not the case. That's that's definitely not the case I mean, there's there's many many clients that we work with where it is the solution Seamus is what they want that mean that is the solution that they want So I mean it all depends on what it exactly is that you want to do with this integration Maybe Seamus can do it for you But other than that, I don't know. Maybe you do need to wait to the end of the year until we can open sources but At the and again the Seamus as I saying is not quite there yet either the Seamus module on the Drupal side isn't quite there yet either but It's it's it's far enough along It's and it's a simple enough kind of module that you can you can usually bend it and adapt it to the way that you ways that you want Yeah Yeah, so what did you get the first part of the question? Oh, okay. I'm sorry So he was asking If he wants if he wants to do an integration like this Does he have to wait till the end of the year? Until we until we open source it Which is a good question So as I mentioned that you know very often Seamus Is the solution and can is a great solution for you as I say many of our clients that is is the solution for them but apart from that I Mean I suppose that is the case maybe that's something it's a great question actually and it makes me think that maybe Maybe we should be peacemaking this thing out and maybe not wait for the whole ball of wax before we actually release it Out to out to the public. So it's a very good point actually and maybe that is something that we need to reconsider Yeah Yeah, right here Yeah Yeah Yeah, yeah, I'll fest go Yeah, there's a there's a number of ways you can do it. Yeah ftp's one sifts is one, but in reality LDAP well LDAP's not a way to do it Yeah, well there is there is a Yeah, well there is actually a module Plugging I guess you could say For all fresco Which has the the very sexy name of batch loader And and and what it allows you to do is is actually Just basically just suck suck files in straight from the file system into it And that's actually kind of the more the recommended way of doing massive amounts of data Like if you want to like terabytes and terabytes and terabytes of data, that's the way to do it Yeah, so hopefully Google would help you out in that batch loader because that's a very catchy name Yep nodes They say notes or nodes nodes. Yes, absolutely That's a great idea. Yeah Well, I mean we've just kind of recently kind of gone on onto the the Drupal 7 on a kind of part of it When we first started the fresco's Drupal 7 was still, you know, not ready for prime time And so we didn't really pay a lot of attention to that But actually that's a great idea, especially with you know, how important it's going to be in 7 and 8 so it's a great idea I mean, I think it's just some Absolutely, that's right. Absolutely That's a great idea Other questions that's interesting Yeah, it's just Drupal 8 it's not going to have versioning built in right Drupal 8. I don't think so so that would be an interesting thing of how that would work with Drupal with How that might work with the fresco is how the versioning works in that in-light editing But I don't see why why it shouldn't work. I mean, it's it's I Know that they're looking at look at the aloha editor for that for supporting that and and you know I've experimented a little bit with that and Sorry Yes, I'm very familiar with that actually We're actually doing a fair amount of work with that We're probably gonna be one of the first organizations to actually try to build something with that something real right now It's pretty buggy, but We've been working with Angie you probably know Angie On that that but we haven't really considered like how that how that affects canopy at this point But obviously we need to think about that No doubt Yeah Yeah, absolutely. Absolutely Yeah, you had a question back here I would like to use Yeah, so that is something that It doesn't support at the moment if you get it from the website, but we actually have modified it for a client to do that Just put that We want to do a little bit more work on that we'll contribute it back But at the moment out of the box. No, it's it's like it's hard-coded. It's like admin admin, right? You know, it's like it's one user at the moment no matter what you usually log in as on the Drupal site It's just going to do admin admin or whatever user you want Yes, absolutely like you like that that is replicated or is meaningful on the fresco side as well. Yes, absolutely Absolutely. Yeah, absolutely. Yeah, you definitely can Yeah, in fact, I don't even think the standard actually even specifies it, but It's it just takes the authentic. It's just authentication. So if you authenticate as that user Well fresco if you if you authenticate seamless as say the gym user you only get access to the gym stuff, right? Yeah Not a whole lot of experience actually doing that It shouldn't be that difficult to do I boost your point actually even support seem as I could be wrong But I might actually even support seem as yeah. Yeah. Yeah. Yeah, so so you might be able to do something there Probably not the best way to do it actually do seem as but Yeah, I'm not that familiar with your point in terms of like what kind of export kind of you can what kind of exports You can do but I imagine that it shouldn't be that very good One of the worst migrations I ever did with with a fresco was somebody actually wanted to pretty large organization actually wanted to Replicate their exchange server in a fresco like all of their direct. They had these massive directory structures in exchange That they wanted to move into a fresco and then have people actually connect to it with their outlook, right? It's unbelievable and this was like terabytes and terabytes of data So that was certainly the most painful that I'd have experienced and believe me I'm sure SharePoint would be much simpler than that that migration. Yeah, right here An eternal trip for a fresco is what I'm not familiar with that actually yeah, no no, I'm not familiar with that Any other questions. Yeah, right here just open so it's probably just gonna be similar to like a canoe kind of license It's gonna be open source. That's similar to Drupal. Yeah. Yeah Maybe even Apache actually we might go any other questions Okay, I guess that's it. Thank you