On 02-06-20 15:03, Avon wrote to g00r00 <=-
For now I hatch via Mystic but not easily announce that hatched content
to the world.
I still use my own hatching system. Announcing would be easy, just some text massaging and running mutil. :)
On 02-06-20 19:15, Avon wrote to Vk3jed <=-
On 06 Feb 2020 at 03:01p, Vk3jed pondered and said...
I still use my own hatching system. Announcing would be easy, just some text massaging and running mutil. :)
Mine is a mix of batch file and other tools also but to have it all in Mystic would be grand...
Hi g00r00
Would you be open to creating something that a sysop could customise with their own header and footer and perhaps a few keywords to add/remove some elements of the hatched file info from the output of the template when
it is posted?
Mine is a mix of batch file and other tools also but to have it all i Mystic would be grand...
I like having all my stuff outside, where I have control. ;)
So far we have:
- TIC hatch announcements (MUTIL)
- Auto deactivated echomail nodes based on days (MUTIL)
If you think those are good ideas let me know, and also let me know what else you think we can add.
As far as hatch reporting, how does that typically work? Do you generate reports based on the "last X days" or do you generate reports that
include any file that was hatched but not yet announced?
Area : FSX_MUTL : Mystic BBS Utils, Mods etc.-----------------------------------------------------------------------------
Reporting is one area that I am not familiar with so I will be looking
for direction for all of these things!
If there were a database that held onto the last X files hatched per file area that could be called that would be good also. Again that report
would ideally offer the sysop some granularity over which bases to
include in such a report, how many days back to report on, and the
On 02-08-20 08:26, Avon wrote to Vk3jed <=-
I think what we will end up with inside the Mystic ecosystem will be
just fine :)
The hatch information would contain:
File name,
File size,
File description,
Echo Tag
Announced flag (yes/no)
Date/time hatched
This will allow us to report as many times as we want, and various
reports could be generated. You could do the traditional one and done report (the database will use the announced flag for that) or you could generate a report of all files hatched in the last X days.
Yes, I agree we need reporting on this! I want to keep building on the statistic stuff that was added into A44 and I am very open to hearing ideas at a high level (for now) about what those things are that you'd like to see.
So far we have:
- TIC hatch announcements (MUTIL)
- Auto deactivated echomail nodes based on days (MUTIL)
Have you given some thought as to how the reports may group hatched
files (or not)? So if we had a bunch of Mystic builds sent out in
FSX_MYS would it group them all as one chunk in the report and say use
the Base Name of the Echo Tag as a more descriptive header for that cluster?
It would be interesting to record either the specific nodes that a file was hatched to or at the very least the total number of nodes a file was hatched to Both would be nice to see as options that could be included
in reports.
Just to clarify? Are you after ideas of features/functions that can be
run on the basis of the stats now being tracked? Or are you after the types of stats and reports I would like to be able to track / pull / display in some fashion/form?
For the echomail side, I think it'd be nice to hear what reports would
be nice to have regardless of if the data is there or not. At the very least it may help me sort out how to design the template engine for
report generation.
On CRBBS, I'm running Husky. The stats that the perl script compiles is a pretty good indication of what I was looking for in stats. If you'd
like, I, or Avon, can send the perl script to you.
Yes, thats how it would work. Files would be grouped and sorted by echotag.
I've noted all of your comments and I agree with all of them! Thank you!
Just to clarify? Are you after ideas of features/functions that can b run on the basis of the stats now being tracked? Or are you after the types of stats and reports I would like to be able to track / pull / display in some fashion/form?
I think both are beneficial to hear.
For the echomail side, I think it'd be nice to hear what reports would
be nice to have regardless of if the data is there or not. At the very least it may help me sort out how to design the template engine for
report generation.
For the hatch stuff your feedback has been perfect and I have a pretty clear vision on the enhancements I want to make for both reporting and
to hatching.
For the echomail side, I think it'd be nice to hear what reports would
be nice to have regardless of if the data is there or not. At the very least it may help me sort out how to design the template engine for
report generation.
Sorry I've been snowed at work and home the last few days. Just posting this at the start of my Wed at work before the demands of the day arrive. I've forwarded some past stats reports to this echo. All but the last one were generated from one package. I'll try to email you tonight with details and any code I can share that may help you.
were generated from one package. I'll try to email you tonight with details and any code I can share that may help you.
Sorry I've been snowed at work and home the last few days. Just posting this at the start of my Wed at work before the demands of the day arrive. I've forwarded some past stats reports to this echo. All but the last one were generated from one package. I'll try to email you tonight with details and any code I can share that may help you.
were generated from one package. I'll try to email you tonight with details and any code I can share that may help you.
Thank you I appreciate it too. I actually have a pretty ridiculous schedule this week and next myself, so there is no rush to this stuff.
For now I am sitting on the start of digging into new features while I wait to see if I can address any bugs that pop up. Once I am through these next 10 days I will probably release the "bugfixes" as A45 and
then start A46 with a whole bunch of new things that could be broken ;)
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 95 |
Nodes: | 16 (0 / 16) |
Uptime: | 07:28:02 |
Calls: | 4,626 |
Calls today: | 2 |
Files: | 8,491 |
Messages: | 348,895 |