RE: [OSGeo-Discuss] any ideas on how to Monitor and Review 'random' files?
Another solution could be better, but that's in a realm where I don't excel. The files themselves has and probably can be added attributes/metadata. The scoop of the problem then moves to what attributes to add, where and when. I'll assume that an application program can access a ftp storage (if that's the type of file share that's used) and do a read of the file-attributes .. again, I only tried to up/download via ftp, but it ought to be no swet to read from such a place.I have done reading of attributes programmatically, but the mess of the approach I chose is not recommendable, but that could be due to the complex format (tiff) and that my focus was elsewhere. I'm sure that others here has a proper bid on how to deal with attributes/metadata. .. it ought to be fairly 'easy'. Once you've got that information, sorting it should be no deal weather or not it's done in a web-script or an ordinary application program. Carsten ___ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
RE: [OSGeo-Discuss] any ideas on how to Monitor and Review 'random' files?
I forget the obvious.If such a thing as 'explorer' (the visual directory/file-reader that is the core of all the pc's I've ever used) exists, it can be used to add and edit attributes, and sort files by it. .. there you go ___ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
[OSGeo-Discuss] any ideas on how to Monitor and Review 'random' files?
We are doing some brainstorming in order to come up with possible ideas of how to address a problem, so any thoughts, comments, or suggestions are welcome. The problem is outlined below. = Within a corporate environment the users have workstations running Microsoft Vista. All users have access to some network file shares, but different groups of users have access to different file shares. All file shares are using the NTFS filesystem. A group of users - call them the Workers - have a common file share that they use during the course of their business. When an event takes place, and for some time after, various Workers will add event-related files to the shared location. How such files are organized is up to the Workers. There is no technical mechanism (i.e. filesystem monitoring software) or procedural mechanism (i.e. business process) that currently exists that results in 'monitoring' the addition of, or changes to, the event-related files. A different user - call them the Reviewer - who works in a different part of the corporate organization, has a need to 'review and organize' some of the event-related files that are provided by the Workers. This process typically takes place 'after the event', however, event-related files might be added by the Workers well after the event took place (e.g. months or years later), so the Workers could be making updates during the same time period that the Reviewer is doing their 'reviewing and organizing'. For a particular event the Reviewer may want to review the event-related files, 'organize' them, and be informed when Workers add more files for that event. Eventually there may be a need to make a copy of some of the event-related files, based on criteria specified by the Reviewer. It may be possible to add software to the Reviewer's workstation to assist with this process, but it will be less likely to be able to deal with the Workers' workstations, and very unlikely to be able to deal with the servers hosting the file shares. Although this isn't really about geospatial processing, there are some geospatial files involved in this process. As an example: - an event takes place - call it ABC123 - a Worker who has files related to ABC123 will put the original files, or copies, on a file share (e.g. some raster maps, some shape files, some word processing documents, some emails, some JPEG photos, KMZ files, etc.) - other Workers will also have files related to ABC123, and they will also put them on the file share - the above process continues while the event ABC123 is 'active' - over time the initial set of ABC123 files will stabilize, and there may not be any new files added very often - the Reviewer gets involved sometime after the event, and starts with the set of files that exist at that point for event ABC123 - the Reviewer may want to 'organize' the files for event ABC123, however that might be able to be accomplished by 'organizing' file metadata, rather than having to make copies of the ABC123 files and organizing the copies - when files for event ABC123 are updated (e.g. a Worker adds a One Year After report for event ABC123), the Reviewer wants to be able to know that there has been an update - at some point the 'organized files' for event ABC123 (and possibly some 'notes' or 'metadata' about those files) will need to be copied from the Workers' file share to another file share, in order to preserve a copy of the files and to provide a location to use for processing the files as they are loaded into a 'document management system' that the Reviewer uses (the last step of loading files into the document management system is already in place, and isn't part of the brainstorming exercise) -- Dave Patton Victoria, B.C. Degree Confluence Project: Canadian Coordinator Technical Coordinator http://www.confluence.org/ Personal website: http://members.shaw.ca/davepatton/ ___ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
RE: [OSGeo-Discuss] any ideas on how to Monitor and Review 'random' files?
Date: Fri, 17 Feb 2012 05:24:48 -0800 From: da...@confluence.org To: discuss@lists.osgeo.org Subject: [OSGeo-Discuss] any ideas on how to Monitor and Review 'random' files? We are doing some brainstorming in order to come up with possible ideas of how to address a problem, so any thoughts, comments, or suggestions are welcome. The problem is outlined below. = Within a corporate environment the users have workstations running Microsoft Vista. All users have access to some network file shares, but different groups of users have access to different file shares. All file shares are using the NTFS filesystem. A group of users - call them the Workers - have a common file share that they use during the course of their business. When an event takes place, and for some time after, various Workers will add event-related files to the shared location. How such files are organized is up to the Workers. There is no technical mechanism (i.e. filesystem monitoring software) or procedural mechanism (i.e. business process) that currently exists that results in 'monitoring' the addition of, or changes to, the event-related files. I recall an item in the visual basic idé (the visual programming environment) called a 'file-system-watcher'.I never used it, so I cann't comment an further. A different user - call them the Reviewer - who works in a different part of the corporate organization, has a need to 'review and organize' some of the event-related files that are provided by the Workers. This process typically takes place 'after the event', however, event-related files might be added by the Workers well after the event took place (e.g. months or years later), so the Workers could be making updates during the same time period that the Reviewer is doing their 'reviewing and organizing'. For a particular event the Reviewer may want to review the event-related files, 'organize' them, and be informed when Workers add more files for that event. Eventually there may be a need to make a copy of some of the event-related files, based on criteria specified by the Reviewer. It may be possible to add software to the Reviewer's workstation to assist with this process, but it will be less likely to be able to deal with the Workers' workstations, and very unlikely to be able to deal with the servers hosting the file shares. is that to be understood as .. they can view or download from, but not say make any scripts on the server ? Although this isn't really about geospatial processing, there are some geospatial files involved in this process. As an example: - an event takes place - call it ABC123 - a Worker who has files related to ABC123 will put the original files, or copies, on a file share (e.g. some raster maps, some shape files, some word processing documents, some emails, some JPEG photos, KMZ files, etc.) - other Workers will also have files related to ABC123, and they will also put them on the file share - the above process continues while the event ABC123 is 'active' - over time the initial set of ABC123 files will stabilize, and there may not be any new files added very often - the Reviewer gets involved sometime after the event, and starts with the set of files that exist at that point for event ABC123 - the Reviewer may want to 'organize' the files for event ABC123, however that might be able to be accomplished by 'organizing' file metadata, rather than having to make copies of the ABC123 files and organizing the copies - when files for event ABC123 are updated (e.g. a Worker adds a One Year After report for event ABC123), the Reviewer wants to be able to know that there has been an update - at some point the 'organized files' for event ABC123 (and possibly some 'notes' or 'metadata' about those files) will need to be copied from the Workers' file share to another file share, in order to preserve a copy of the files and to provide a location to use for processing the files as they are loaded into a 'document management system' that the Reviewer uses (the last step of loading files into the document management system is already in place, and isn't part of the brainstorming exercise) It's not a straightforward problem, so, I could imagine that I would tackle it by my process of working. Coding is the heaven of 'divide and concur' .. building a long list of involved files for starters would bring something to .. divide (read: organize). A way would be to mandate a process of registering files (ie by way of a form on a php/html-driven page). I'll not attempt to feed my brain with the whole setup of your problem, but currently I'm sort of taking a run at dealing with an eqvivalent problem-set: administering a twitter-page (never been twittering thou - just exersizing my skills in html, css, javascript php before the real
Re: [OSGeo-Discuss] any ideas on how to Monitor and Review 'random' files?
My take is that the major item not readily available is a notification mechanism, to be triggered when something changes, with users registering themselves with some kind of call-back function. I dunno what's avaiable in desktop software libraries for this, but I see html5 providing such a mechanism in its 'local storage' feature. Like see http://www.quirksmode.org/blog/archives/2009/06/html5_storage_t.html and http://html5demos.com/storage-events. BTW, I believe the OP is looking for handling not a random file (hardly that!) but an 'arbitrary' user-selected one. AS ___ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
RE: [OSGeo-Discuss] any ideas on how to Monitor and Review 'random' files?
My take is that the major item not readily available is a notification mechanism, to be triggered when something changes, with users registering themselves with some kind of call-back function. I dunno what's avaiable in desktop software libraries for this, but I see html5 providing such a mechanism in its 'local storage' feature. Like see http://www.quirksmode.org/blog/archives/2009/06/html5_storage_t.html and http://html5demos.com/storage-events. Yes. LocalStorage is handy and easy to work with -but- though it's available storage on user's pc's, it's only makes sense in the scoop of a visited page. (does that make sense?).. I'll elaborate: Unless you are managing a html-page that a user ownloads, you cannot access the localStorage of that pc [in my understanding]. The access happens through scripts on the page.About events .. administering the erection of a html-page with it's scripts, on a server, does not really provide server-side events - except for the return response of a xmlhttprequest or similar, send from the client. But, this could be enough. (look up AJAX for the xmlhttprequest ) The ping-ing back and forth takes simple code .. it won't be cluttered up until you want to use it for something sensible ;o) BTW, I believe the OP is looking for handling not a random file (hardly that!) but an 'arbitrary' user-selected one. ___ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
Re: [OSGeo-Discuss] any ideas on how to Monitor and Review 'random' files?
On 2012/02/17 11:36 AM, Carsten Troelsgaard wrote: It may be possible to add software to the Reviewer's workstation to assist with this process, but it will be less likely to be able to deal with the Workers' workstations, and very unlikely to be able to deal with the servers hosting the file shares. is that to be understood as .. they can view or download from, but not say make any scripts on the server ? The servers that host the file shares used by the Workers and/or the Reviewer are not available at all to the Workers/Reviewer. All they have access to is the file shares, which they use as mapped drives. The file servers are managed by a central part of the organization, so even the IT staff that supports the Workers/Reviewer does not have access to the file servers. -- Dave Patton Victoria, B.C. Degree Confluence Project: Canadian Coordinator Technical Coordinator http://www.confluence.org/ Personal website: http://members.shaw.ca/davepatton/ ___ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
Re: [OSGeo-Discuss] any ideas on how to Monitor and Review 'random' files?
On 2012/02/17 11:51 AM, Arnie Shore wrote: BTW, I believe the OP is looking for handling not a random file (hardly that!) but an 'arbitrary' user-selected one. Arnie is correct - I should have perhaps said 'arbitrary'. The point is that the Reviewer can't necessarily anticipate how the 'files of interest' will have been 'organized' by the Workers. -- Dave Patton Victoria, B.C. Degree Confluence Project: Canadian Coordinator Technical Coordinator http://www.confluence.org/ Personal website: http://members.shaw.ca/davepatton/ ___ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
RE: [OSGeo-Discuss] any ideas on how to Monitor and Review 'random' files?
Dave, If the only common denominator of all involved is the company you work for, you'll need a gophor.Joke aside. If noone in your organisation can build you a .html that everyone involved can access, you do have a problem.To put resonable scripting on the page and on the server it's downloaded from is your key to the problem - as I can tell -. The page does not need to be hosted on the same server as the files, or for that matter have access to them. But I don't see how you can do anything without information about the files and a central place to process that information. If I'm off the mark, then please let me know. Bwt the file-system watcher I mentioned is probably an object that lives within application programming (a .dll) ... easy to program, a nightmare to distribute. I can imagine a dilemma: Putting events (if it's possible) on the arrival/movements of the files could be risky business to write code for. Teaching your staff to use a page that factually is only an appendix to the real work of processing those files could be a not very rewarding task either ... Carsten It may be possible to add software to the Reviewer's workstation to assist with this process, but it will be less likely to be able to deal with the Workers' workstations, and very unlikely to be able to deal with the servers hosting the file shares. is that to be understood as .. they can view or download from, but not say make any scripts on the server ? The servers that host the file shares used by the Workers and/or the Reviewer are not available at all to the Workers/Reviewer. All they have access to is the file shares, which they use as mapped drives. The file servers are managed by a central part of the organization, so even the IT staff that supports the Workers/Reviewer does not have access to the file servers. -- Dave Patton Victoria, B.C. ___ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
Re: [OSGeo-Discuss] any ideas on how to Monitor and Review 'random' files?
Nibbling away: Carsten's quite correct, re server-side work needing to be done. Now I believe an approach based on xmpp might provide a solution; Googling for XMPP and collaboration finds several interesting possibly suitable approaches. Especially interesting, IMO, is http://www.ibm.com/developerworks/xml/tutorials/x-realtimeXMPPtut/section3.html AS On 2/17/12, Dave Patton da...@confluence.org wrote: On 2012/02/17 11:51 AM, Arnie Shore wrote: BTW, I believe the OP is looking for handling not a random file (hardly that!) but an 'arbitrary' user-selected one. Arnie is correct - I should have perhaps said 'arbitrary'. The point is that the Reviewer can't necessarily anticipate how the 'files of interest' will have been 'organized' by the Workers. -- Dave Patton Victoria, B.C. Degree Confluence Project: Canadian Coordinator Technical Coordinator http://www.confluence.org/ Personal website: http://members.shaw.ca/davepatton/ ___ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss ___ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
RE: [OSGeo-Discuss] any ideas on how to Monitor and Review 'random' files?
At a quick glimps it looks as what I just accomplished today. The page that is downloaded keeps pinging back to the server to give it a chance to post back information.Next step is to find out how the server-internals works. It's a bit of a nusence that I probably will have to consider it 'dead' (not running a thread) .. instead of collecting information in arrays, I'll have to write everything into the proper files (open/read/ calculate something/write/close) for every ping ... all before getting to juggle the 'true' problem-complex. I wouldn't have got anywhere without some years of application-programming. I'll hit the sack / cheers Nibbling away: Carsten's quite correct, re server-side work needing to be done. Now I believe an approach based on xmpp might provide a solution; Googling for XMPP and collaboration finds several interesting possibly suitable approaches. Especially interesting, IMO, is http://www.ibm.com/developerworks/xml/tutorials/x-realtimeXMPPtut/section3.html AS On 2/17/12, Dave Patton da...@confluence.org wrote: On 2012/02/17 11:51 AM, Arnie Shore wrote: BTW, I believe the OP is looking for handling not a random file (hardly that!) but an 'arbitrary' user-selected one. Arnie is correct - I should have perhaps said 'arbitrary'. The point is that the Reviewer can't necessarily anticipate how the 'files of interest' will have been 'organized' by the Workers. ___ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
RE: [OSGeo-Discuss] any ideas on how to Monitor and Review 'random' files?
Dave, There's no pc-lab like the pillow.Writing the complex code may be more conviniently done in an 'ordinary' application .. letting the web stuff be one big gophor. 'That' application can have a file-system watcher and a silent thread running and possibly responde on changes. And lots more on 'your' pc. Carsten ___ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
