metridoc / metridoc-grails Goto Github PK

I am not sure what is going on here. In general this seems to happen when I was fixing something in metridoc settings

The name tabs makes no sense under commonTemplates since it is pegged to managing metridoc. Call it something else like manageMetridocTabs.

We use a lot of primed data from spreadsheets that is specific to our university. Maybe we should externalize this.

If we can get this to work then the whole project can be self contained, and any change in the core can be used in the other plugins immediately. That said, I am worried what the pom will look like. With the deployed plugin be able to resolve out the inline one?

Currently it is not showing the saved extra departments.

asset-pipeline plugin is far more intuitive (to me at least). I think we should consider using it instead of grails's resource plugin. Hopefully by 0.9 the very new plugin will be sufficiently mature enough to use.

tbarker- "We should split this up into different issues. Apparently this plugin can live along side the reource plugin so we can iteratively upgrade our app. Right now the bootstrap, font awesome and jquery plugins support the asset pipeline plugin."

ShiroUser is kind of a mess. We really don't need the logic for forgetting passwords anymore.

Some of the transaction service methods have not been updated to work with the new instructional transaction domain objects.

not so sure about this one.... everything changes so frequently, hard to come up with a convention that makes sense

no html5 and bad 500 errors

Only permit delete if there are no associated assets. Also tell the user why they can't delete the role

Should probably handle other issues first before doing this

Referenced here, but issue not closed: metridoc-archives/metridoc-grails-core#111

It is a transient field in both Cons and Ins transactions, but it is never actually used anywhere. Can it be removed?

find a reasonable way to unit test whoami

Make sure you reference the plugin as an inline plugin

this can be the central place for all metridoc authentication

I know some is there, I don't think it is as robust as consultational though

This takes high priority over everything

At some point, the case of some items in the spreadsheet became different from the domain. For instance, the spreadsheet's Admin/Policy questions is Admin/policy questions in the DB. This can be fixed in the spreadsheet, or perhaps it might be useful to have the spreadsheet fields generated at bootup based on the saved domain objects. Alternatively, I can simply convert the field name and the domain name to lowercase during validation.

Add admin window that allows the user to set system wide messages

They should be a flash message that always pops up at the top of every
single page. The message should have an expiration as well, either by date
or on server restart. So you will have to implement something in the
BootStrap destroy closure to delete all messages that should refresh on
server restart.

tbarker- "At the end of the day, I only need two messages. I am in development, and I am shutting down. The development one can just detect the environment while the shutting down one can be set in the manage screen and loaded into memory. A server restart will of course reset these."

Right now we are depending on 'memberOf' attribute. This is not guaranteed and should instead be a search accross all groups

Using google visualization

Doesn't look like the fix had gotten merged before the migration; should be a quick fix using the copyright updating script